3 ms·
Developers naturally has the freedom to choose where and on what they want to focus development time on, through I would not discount 32-bit machines as compute
by belorn 5y ago
Developers naturally has the freedom to choose where and on what they want to focus development time on, through I would not discount 32-bit machines as computers that should by now have died and be discared, especially in the server space which is what RMS is talking about during that 8-9m mark. A old 1U rack server is perfectly fine to operate as a router, a firewall, a logging server, a message bus, secondary backup (ie the server that simply get copies from the primary backup server) or some other low intensity work that is preferable done on a separate physical machine. If you work at a company that owned many of those you also have plenty of spares in case some essential old parts breaks down. You don't need a 256 core epic server with a 1TB of ram.
I suspect most kernel developers mostly operate with virtual machines in mind, but as a sysadmin I would argue that physical machines also has their use cases. I also suspect that if the linux kernel stop supporting 32-bit machines, others will continue. Are the BSD people thinking about dropping 32-bit support?
- 2b3a51 5y agoOpenBSD... "Due to the increased usage of OpenBSD/amd64, as well as the age and practicality of most i386 hardware, only easy and critical security fixes are backported to i386. The project has more important things to focus on." [1] OpenBSD includes their Xorg port in a base install, and you can run a reasonable graphical desktop on a 32bit machine. Firefox is not packaged for i386 I think. I just use Seamonkey when I test the 32 bit image now and again. There may be other package limitations relevant to server only use. Seems a rational approach to me. [1] https://www.openbsd.org/i386.html https://www.openbsd.org/i386.html