ryantriangles
I'd argue that that's not meaningfully different to OP's suggestion of a HTML file with all the content inlined, though. It's still a single file grouping everything required together and can be easily edited and read practically anywhere. It has a few advantages over the inlined-content HTML file, too:
- You can read the compressed file directly, an epub being typically half the size of the uncompressed files (going by a quick test of 30 randomly-selected files I had on hand).
- Storing the actual JPEG, PNG, OTF, etc files inside the zip is more efficient than inlining them as base64 and then making the browser decode them, in terms of both speed and filesize.
- While reading an epub, different sections can be a different HTML files, and only one needs to be loaded into memory at a time. This can be irrelevant for smaller things but it can make a big difference sometimes--with pages that include many charts and tables, documentation for graphics libraries that include images and animations for each documented function, etc.
- Epub files have native support for highlighting and bookmarking, to keep your place in long documents and share the file with your highlights attached.
I think these tradeoffs are why there hasn't been as much interest in replicating it, combined with the fact that mlocate/fd/find/fsearch are already a lot faster in most circumstances than the default Windows search and good enough for the most common use cases (although there are certainly usecases where they're not).
Microsoft publish a tool in the Windows Terminal GitHub repo, ColorTool.exe[1], which can turn iTerm2 color scheme files into Windows Terminal ones. That might be your best bet because there are huge repositories of good iTerm2 schemes[2] and really slick tools to quickly make your own with live previews.[3]
[1] https://github.com/Microsoft/Terminal/tree/main/src/tools/Co...
Hardware AV1 decoding is available on some Android devices right now, and will ship with a lot more over the course of the year. So it seems the perfect time to ship an AV1 option behind an opt-in setting, which is what they've done. If you don't have hardware support and it's not worth the battery drain then you don't have to select it and there's no way they're removing H.264 support anytime soon.
To me the big draw of the iPad is that it combines the simplicity of a phone OS with a screen that can render large fonts and still be usable. That's great for people with poor eyesight, like my grandparents, who can fit only a few words at a time onto a 5" phone display and who find the Windows interface frustrating (being full of small buttons, accidentally-pressed keyboard shortcuts, things minimizing to the tray, and multiple windows containing multiple tabs). As someone lucky enough to have escaped that problem so far the iPad exists in a strange halfway point between a laptop (large, powerful, keyboard-equipped, capable of running and doing anything) and a phone (comfortable, portable, long-lasting) that's never quite right for the job.
Admittedly I've never used the Pencil which I imagine can be quite nifty.
And I don't think reading a book and browsing the web are fundamentally different activities. They're near-identical. The web was created as a way to access documents consisting of text, images, and links to other points within the current document or to other documents. A book is a document consisting of text, images, and links to other points within the current document (endnotes, footnotes, "see page X") or to other documents (references/citations). The UX and features you'd want for a book reader are the same you'd want for a browser's Reader Mode, as implemented by Edge, Firefox, and Safari. I don't see any difference between reading an ePub file and reading a long article on a website.
http://news.bbc.co.uk/2/hi/health/6154600.stm
https://www.wsj.com/articles/SB106919100053167300
https://publications.parliament.uk/pa/cm200304/cmbills/110/0... (Section 3)
It's not really a fair comparison, though. The main issue with anti-vaccination content is dangerous misinformation, not simply promoting something harmful. The other issue is that the people who fall for this content aren't usually the ones who get hurt, their innocent children are. It would only be a fair comparison if there were a large movement of very influential, powerful, and famous people posting "vegetables cause autism, and Burger King cures it" videos out there to hundreds of millions of viewers and a boom in child obesity tied directly to parents viewing them.
S3 has nothing to do with the FTP protocol, but if someone completely new to AWS and similar platforms asked "What's this S3 thing?", you might say "Think of it as sort of like an unlimited FTP server." You can connect to it through programs like CrossFTP, browse a folder hierarchy, upload files, link those files from a website, and in general do all the things people commonly use (S)FTP for, with the same tools they use for (S)FTP stuff. It's similar enough that it makes a good starting analogy.
App Scripts is another description I think is reasonable. Personally, I don't think manual invocation or modification of a stateful resource is key to the term 'script.' I think of a script as a relatively simple program that is invoked, accomplishes one task, and then ends without interaction. "Erase duplicate files in folder X" and "send me an email listing all files added today" are examples of scripts you might run as a cron job or in response to an event (like free space dropping below some level). Lambda is close enough to this that I think "Lambda's where you store scripts and define when they get run" is a reasonable explanation.