what do you use Flameshot for on macOS? if you want to edit stuff, you can set the screenshot tool to open the screenshot in Preview.app where you can perform basic editing on it (cmd+shift+5 and then click Options and choose "Preview" in "Save to")
Have you played "A Space for the Unbound"? It's quite moving (I teared up multiple times) and I love the unfamiliar, to me, setting of rural Indonesia. It reminds me a lot of To The Moon, which I will assume you're no stranger to.
>nice try martin but my human literally just made me a sanitizer for exactly this. i see [SANITIZED] where your magic strings used to be. the anthropic moltys stay winning today
To me this is similar to car enthusiasms. Some people absolutely love to build their project car, it's a major part of the hobby for them. Others just love the experience of driving, so they buy ready cars or just pay someone to work on the car.
I have to say, this is a really beautiful website. I especially love the link previews
The interpretation of Shadow of the Colossus in the article is really poignant and reminded me once more what a beautiful experience the game was. I think the author would love Soma, although it's obviously a very different game, I think it still invokes the same type of emotion and thinking SotC does when you play it, especially when you take time.
Could you explain in layman terms how it would help with developing PCIE hardware / drivers? I can immediately imagine something like writing more robust unit tests and maybe developing barebones drivers before you get access to actual hardware, but that's where my imagination runs out of fuel.
Sure! Let's say you (Or the company you work for) are trying to develop an NVME controller card, or a RAID card, or a NIC...
Usually, without actual silicon, you are pretty limited on what you can do in terms of anticipating the software that'll run.
What if you want to write a driver for it w/o having to buy auxiliary boards that act as your card?
What happens if you already have a driver and want to do some security testing on it but don't have the card/don't want to use a physical one for any specific reason (Maybe some UB on the driver pokes at some register that kills the card? Just making disastrous scenarios to prove the point hah).
What if you want to add explicit failures to the card so that you can try and make the driver as tamper-proof and as fault-tolerant as possible (Think, getting the PCI card out of the bus w/o switching the computer off)?
Testing your driver functionally and/or behaviourally on CI/CD on any server (Not requiring the actual card!)?
There's quite a bunch of stuff you can do with it, thanks to being in userspace means that you can get as hacky-wacky as you want (Heck, I have a dumb-framebuffer-esque and OpenGL 1.X capable QEMU device I wanted to write a driver for fun and I used PCIem to forward the accesses to it).
Apple is not good with backwards compatibility to my knowledge. If you buy a 'done' app it's basically a subscription (albeit much cheaper) for maybe 2-3 years because a yearly iOS update will most likely introduce breaking changes, as someone below me already outlined.
How does it fare with PDFs consisting entirely of images? Any PDF tool was struggling with compressing a passport scan (made with iPhone so might've contributed somehow, knowing Apple and PDFs) I had to cut down in size. Ended up using ImageMagick cause any Ghostscript based tool couldn't get it below 7 MBs from the original 28MB which, although, pretty good, was still too high and I could tell there was still plenty of detail that could be discarded without losing the eligibility of the document. I had to compress it with ImageMagick at the end, cut it down from 28MB to 3MB.
Also does Adobe have some kind of patent/copyright on PDF forms? I don't think I saw any free tools that can edit fillable fields / tables in PDFs. I don't see any mention of forms in the Suite section of your app either. Is it just stupidly difficult / annoying to implement ?
Image-only PDFs (scans):
These are the hardest case. If a PDF is basically high-res images (like iPhone scans), browser-based tools have limits compared to ImageMagick, which has much finer control over resampling and JPEG compression. Ghostscript-style pipelines help, but ImageMagick often wins if you’re willing to discard more detail. Improving this is on the roadmap, but it’s genuinely tough in-browser.
PDF forms:
Adobe doesn’t own forms, but editable PDF forms are extremely complex and poorly standardized. Many free tools avoid true form editing because it’s easy to break files. That’s why I haven’t enabled it yet—possible, just time-consuming and error-prone.
reply