4 ms·

At want point to do you accept you’ll have to buy into _some_ vendor lock-in? Should you always program in a way that ensures your application will function a Z

At want point to do you accept you’ll have to buy into _some_ vendor lock-in? Should you always program in a way that ensures your application will function a Zaurus running OpenBSD?

yjftsjthsd-h 4y ago
> At want point to do you accept you’ll have to buy into _some_ vendor lock-in? If I wanted that, I'd go back to Windows. Well. Maybe Apple. Either way, I wouldn't be here. > Should you always program in a way that ensures your application will function a Zaurus running OpenBSD? Preferably? Like, your framing makes me think that you think that's somehow extreme, but... unironically yes, if your program wouldn't run on OpenBSD on a Zaurus you should seriously sit down and consider why and whether that's really how it should be. And there are valid reasons to decide "no" (ML needing really high performance can justify hardware lock-in, cutting-edge development on things like DPDK could justify needing a specific kernel, I guess needing very specific features and not having the developer-hours could justify using systemd features), but 90% of software should absolutely 100% work on any of FreeBSD/NetBSD/OpenBSD/Debian Linux/Alpine Linux/Gentoo/Fedora/whatever on any of x86/x86_64/aarch64/mipsel/riscv/whatever