3 ms·
> Is there a case to be made for developing new software […] I think one decent case would be to keep yourself honest. Linux started out a 80386 only, but som
by throw0101a 6y ago
> Is there a case to be made for developing new software […]
I think one decent case would be to keep yourself honest.
Linux started out a 80386 only, but someone ported it to DEC Alpha. By deciding to run on both 32- and 64-bit platforms in the 1990s, it kept the kernel developers agnostic. Then when the x86 world went 64-bit with amd64, there was probably a lot less 'cleanly up' to do for it to be ported compared to if it had been focused on pure-x86 (see also SPARC and endianness). It's said that NetBSD has a very clean code base because of it's reputed high portability.
Similarly Solaris was very scalable. Partly because in 1996 Sun released the SPARCcenter 2000, which could handle 20 CPU sockets. That was a lot, and I'm guessing not many folks bought one, but they had to deal with it in an official capacity, as time when on more CPUs (and cores) became prevalent Solaris was good to go as that situation became more mainstream.
If you develop for the odd ball situations and corner cases, it may force you to be less lazy as a programmer.
- deleted 6y ago[deleted]
- huslage 6y agoI ran a fully populated SPARCcenter 2000. It was a beast. Not like the E10K, but still a beast.
- bcantrill 6y agoYou are absolutely correct; anyone who worked on Solaris scalability and performance back in the day will have plenty of Dragon war stories -- and Solaris did so well on Campfire (a.k.a. UltraSPARC Enterprise 4000, shipped 1996) exactly because so much time and energy had been spent on Dragon (a.k.a. SPARCcenter 2000, shipped 1992).
- throw0101a 6y ago> Campfire (a.k.a. UltraSPARC Enterprise 4000, shipped 1996) My main gripe with the various 'E-series' systems (IIRC, we had some E3x00s) was boot-up time, especially the RAM check on power up. I was in an academic environment, and so every so often we had to power down our lab for electrical/fire code inspection power outages by Facilities. The first time we rebooted one (with 4GB of RAM?) it kept booting and booting and booting and booting and booting and booting. 17 minutes later we got the login prompt on the console. We put the 17 minutes as a note in our run book so that we knew not to worry if took 'forever' and to move onto the next step. Otherwise we'd start freaking out about something being "broken" with the system(s). (This was in the 2001-2001 timeframe.)
- icedchai 6y agoYes! I worked at a startup with an E3500, around 1998-99, and those machines took forever to boot. Nice hardware though. I think ours had a whopping 512 meg.
- kjs3 6y agoThe 2000 was pretty popular AFAIK; I saw a lot of them anyway. Yeah...a lot of stuff got worked out in Solaris on the SC2000, and the journey was painful. But after a year or so of very frequent out-of-cycle patches, some hardware upgrades, and a lot of time with Sun support, they were pretty stable and scalable. Nice machines. I don't think we ever got the OC-12 ATM cards really stable...fortunately, networking went a different direction and they had a mercifully short lifespan.