3 ms·
I wonder about that, too. Not that anyone's beating my door down to port my own projects to zOS or anything, but I consider modern Linux/BSD to be my baseline t
by kstrauser 2y ago
I wonder about that, too. Not that anyone's beating my door down to port my own projects to zOS or anything, but I consider modern Linux/BSD to be my baseline target for all new code I write. If it runs well on amd64/aarch64 Linux, Mac, and {Free,Open}BSD, that's enough. Well, and Windows, if someone makes it run there and it's not onerous to support. I wouldn't accept patches that make it harder to build or maintain on those primary systems.
It's not that I actively hate anything that isn't a recent 64-bit Unix, but that the people on other systems are either 1) hobbyists who are competent to port stuff to their own systems, or 2) companies who aren't paying me for extraordinary support.
Bummer if something I wrote last week doesn't run on HP-UX, but it's not going to cost me sleep.
- jnwatson 2y agoI had to think long and hard about whether to accept a PR that fixed ppcle64 support on the library I maintain. Since it wasn't too much of a diff, I accepted it, but in many other situations I wouldn't.
- kstrauser 2y agoIf it’s trivial with zero adverse affects on common hardware, fine. If it adds the equivalent of a bunch of ifdefs or requires adding autoconf, nah.
- joseda-hg 2y agoAt this point, between WSL2 and how good wine has gotten, there's a lot of crossover for building/maintaining, outside the target OS