0 Followers
0 Following
7 Posts

This account is a replica from Hacker News. Its author can't see your replies. If you find this service useful, please consider supporting us via our Patreon.
Officialhttps://
Support this servicehttps://www.patreon.com/birddotmakeup

What keeps me in the Appleverse is the hardware, and the software that Just Works with the hardware (I find that "Just Works" has been rapidly eroding in general, but naturally it still handles the hardware well). The alternatives are Linux on much worse hardware, or the non-starter that is Windows on anything whatsoever.

I'm told ThinkPads are getting to parity and have primo Linux support, but barring accident, my M3 MBP will probably last me a decade. Another reason I prefer Apple hardware.

This might be a good thing for homebrew to adopt for the download/install process, but if it doesn't include a ruby interpreter, I have a hard time seeing how it's going to be compatible with anything but searching and installing bottles. I install most of my packages from a Brewfile, which itself is Ruby code.
Amateurs. Russia has fined Google more than the GDP of the entire planet. Odds of collecting are about the same.
These days one would just most likely create a fork on github. Vim was also maintained through separate patches for a long time, but Bram was a lot more accepting about integrating and distributing those patches himself.
I doubt the lack of license was the reason DJB's projects didn't take over the world. Most of them required heavy forking to break away from hardwired assumptions about the filesystem and play nice with the OS distribution, and DJB is himself notoriously difficult to work with. Still, qmail managed to establish maildir as the standard format and kill off mbox, and for that alone I'm eternally grateful.
What a strange convention. I'm partial to minisign, which works on plain old files.

> Cancelling XSLT is going in the wrong direction (IMHO).

XSLT isn't going anywhere: hardwiring into the browser an implementation that's known to be insecure and is basically unmaintained is what's going away. The people doing the wailing/rending/gnashing about the removal of libxslt needed to step up to fix and maintain it.

It seems like something an extension ought to be capable of, and if not, fix the extension API so it can. In firefox I think it would be a full-blown plugin, which is a lower-level thing than an extension, but I don't know whether Chromium even has a concept of such a thing.