Relevant video from Ann Reardon's How To Cook That about exploding Pyrex (and the difference between all capitals and all lowercase): https://www.youtube.com/watch?v=YVbkDAw4aJs
Turned out that distinction isn't too reliable when it comes to determining whether a product used soda lime glass or borosilicate glass instead.
It’s a bit amusing to me that this sounds like another, different anti-trust issue. Apple’s browser having this feature, which other browser vendors (presumably) can’t add, to open another app would also look bad to an EU judge.
> I think it was Microsoft FrontPage that had the most undigestible output at the time.
Nah, I would argue that was Microsoft Word's (Office?) Save as Web Page feature. Which is what I built my first few websites in as a kid haha before learning about FrontPage and pirating that (back in 2003). FrontPage was a dream in comparison. Then I learned that FrontPage was also not as good, and learnt Dreamweaver is the better option so pirated and tried to use that shortly after, but the WYSIWYG of FrontPage was leagues better to my little child brain. Ah, nostalgia :')
> The reason this causes so much suspicion is because we westerners are terrified of what that would mean for the rest of the world.
It would mean having to eschew the neoliberal ideals that impede research and development in favour of the old that made America and to some extent the rest of the West the dominant superpower in R&D for many decades. We should be familiar with it, even if we have lived all or most of ours lives in the former.
Or it would be hard to convert back and we'd have a war first.
Many distros still provide the `service` command, and don't print any warnings when you use it. At best, you might get an informational message that the equivalent systemd command is being called. There is no recommendation to call the systemd command directly, or any sign of the `service` command being deprecated any time soon. As a result, a lot of people are probably still relying on their muscle memory for the `service` command.
> I don't know if this exists or not, but I'd like to try something like a fuse filesystem which can transparently copy a file to a fast scratch SSD when it is first accessed.
You may be interested in checking out bcache[1] or bcachefs[2].
But L2ARC only helps read speed. The idea with dm-writecache is to improve write speed.
I started thinking about this when considering using a SAN for the disks, so that write speed was limited by the 10GbE network I had. A local NVMe could then absorb write bursts, maintaining performance.
That said, it's not something I'd want to use in production that's for sure.
There was some work being done on writeback caching for ZFS[1], sadly it seems to have remained closed-source.
That's what SLOG is for if the writes are synchronous or if you have many small files/ want to optimize the metadata speed look at the metadata special device, which can also store small files of configurable size.
ZFS of course has its limits too. But in my experience I feel much more confident (re)configuring it. You can tune the real world performance well enough especially if you can utilize some of the advanced features of ZFS like snapshots/ bookmarks + zfs-send/recv for backups. Because with LVM/ XFS you can certainly hack something together which will work pretty reliably too but with ZFS it's all integrated and well tested (because it is a common use case).
As I mentioned in my other[1] post, the SLOG isn't really a write-back cache. My workloads are mostly async, so SLOG wouldn't help unless I force sync=always which isn't great either.
I love ZFS overall, it's been rock solid for me in the almost 15 years I've used it. This is just that one area where I feel could do with some improvements.
Turned out that distinction isn't too reliable when it comes to determining whether a product used soda lime glass or borosilicate glass instead.