Hacker News new | past | comments | ask | show | jobs | submit | Mayzie's comments login

> 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 :')


I had a go, but there were a few I wasn't really sure by. To the creator, can you add a "Not sure" option?


I think they recognize the "not sure" by various users giving different answers.


> 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.


It's been a decade at this point since the last big distro (and surrounding drama), Debian and Ubuntu following shortly after, moved to systemd.


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.


And where will the money come from for this second study? What about a third? Fourth?

We live in a money-dependent world. We cannot go without it.


Haircare as well :)


> 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].

[1] https://www.kernel.org/doc/html/latest/admin-guide/bcache.ht...

[2] https://bcachefs.org/


lvm-cache works as well, if you're already using LVM.

https://github.com/45Drives/autotier is exactly what they were asking for as well


I've done some testing with using ZFS on top of LVM with dm-writecache.

Worked well enough on the small scale, but sadly haven't had the time or hardware to test it in a more production-like environment.

Also, it was starting to feel a bit like a Jenga tower, increasing the chances of bugs and other weird issues to strike.


I wouldn't recommend combining those two. It's only begging for problems.


Yeah that's my worry. Still, got 6x old 3TB disks that still work and a few spare NVMEs, so would be fun to try it for teh lulz.


Rather build a L2ARC or metadata special device hybrid setup using ZFS or skip ZFS and go for lvmcache/ mdadm style RAID with XFS or something.


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.

[1]: https://openzfs.org/wiki/Writeback_Cache


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.

[1]: https://news.ycombinator.com/item?id=41670945


My assumption with bcache is that it operates on blocks rather than entire files. Am I wrong?


Yeah, bcache is exactly that


Relevant /r/todayilearned thread from a few hours ago about this: https://www.reddit.com/r/todayilearned/comments/1eanz3p/til_...


There have been and are attempts at addressing the usability gap of tech by the more tech illiterate over the years. Particularly, Linux projects such as Ordissimo[1], Eldy[2], and Endless OS[3]. I am sure there are plenty of other projects, as well (including Apple's new iPhone Assistive Access mode[4]. As sad as it may be, the market would probably be non-existent in a decade or two as newer generations enter aged care having already been somewhat familiar with computers and phone technology.

[1] https://www.ordissimo.com/en/why-ordissimo

[2] http://www.eldy.eu/

[3] https://www.endlessos.org/

[4] https://support.apple.com/en-au/guide/assistive-access-iphon...


> The main problem with canaries is that it's dead easy for a government to remove them from existence, simply issue subpoenas to every website that has one.

Why can't social media platforms implement warrant canaries per user profile?


Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: