3 ms·
This brings up a good meta point: people who like to complain about the quality of software in the modern world almost certainly didn't live through the early[1
by ajross 7y ago
This brings up a good meta point: people who like to complain about the quality of software in the modern world almost certainly didn't live through the early[1] days of the industry.
This sounds crazy to modern ears, but at the time the idea of a desktop system actually staying booted for a whole month was weird and alien. They just didn't do that. Commercial unixes were better. It was routine to find servers that had been running for three digit (!!) uptimes, and people would brag about stuff like this. Linux, when it arrived, was in this category too and we'd all puff to our friends about how we "never turn off" the machine under our desk, because it would always be able to run for a month or so before it crashed.
It was just a different world, and things, despite some of the community emotion, have gotten vastly better. We're much better at writing software than we used to be, which tends to make some of old folks a little confused when people hold up "new" ideas as being paradigm shifts in software quality.
We already had the shift! We're just picking the higher hanging fruit now.
[1] Do the mid-90's even count as early?
- rapind 7y agoI have a Hackintosh running High Sierra, and at most I reboot once a month.
- blackoil 7y ago<rant> The problem is not people writing buggy software or them crashing. At least for me problem is we keep on reinventing the wheel, without corresponding increase in productivity. I don't see people cranking s/w better or faster then they did with Delphi in 1998. Instead of standing on shoulders of the giants we disrespect them, our whole industry is built on abusing all the hardware and technology gains for frivolous wars and gains. </rant>
- jaclaz 7y agoWell, there are huge differences (in the MS world) between 9x and NT. DOS (before) was very, very stable (but of course was not multitasking) and widely used in industrial setups. Windows NT (before Win9x) and Windows 2000 (right after) were both, very, very stable, I had machines running 24/7/365 that were rebooted once a year or so and for other reasons (maintenance/update, hardware replacement, black outs longer than UPS capability, etc.).
- barrkel 7y agoDOS wasn't functional enough to be described as stable; it did almost nothing but look after the files on your file system and provide a few APIs, via interrupts, for programs to read and write files and perform console I/O. Stability was almost entirely the responsibility of the program you ran on top.
- badsectoracula 7y agoI do often complain about the quality of software but that is because i complain about the quality of most of the software. The foundation we work on is usually much more robust than what it was in the 90s, it is the stuff that we build on top that is shaky. And a big issue (at least on the desktop) is that in many cases we keep throwing away old stuff and reinvent new stuff with their new bugs and issues, instead of fixing that old stuff (and i do not think that it is a coincidence that most of the stable foundation is actually old stuff that had a lot of people trying to fix its issues instead of throwing everything away).
- barrkel 7y agoCoding in DOS, saving before executing your program became a reflex because any hard freeze in your program would force you to reset the machine. It wasn't rare, and practically unavoidable if you're trying to do something clever like a TSR. Or doing something interesting with graphics - if you got left in a weird mode, you might have to type blind to recover, or give up and reset.
- dylan604 7y agoIn the early days of web-hosting providers, it was common to see a version of Linux and a version of Windows as options. Only the Linux servers came with an uptime guarantee.