Editors of computer magazines were the "influencers" in the '80s.
If your intent is ship-once working software, you write towards that goal. You use fewer dependencies, and they are all effectively version locked. It's like putting books in a box. You put them in the way you expect them to ship, rearrange as needed, and when they're all securely in, you ship.
The current update fast and furiously free for all is like trying to bundle a few dozen kittens in a bed sheet by comparison. Often with a bunch of random chaos monkeys you've never met "helping."
Good times; not having to worry about library versions/updates was nice actually. Besides turbo Pascal (later delphi), we had no 3rdparty dependencies up until we sold the company.
Never had to ship software on 9-track tape, but remember receiving the source distro for C++ v1.0 from AT&T on one (cfront, no MI, etc)
Did ship plenty of software on QIC tape though, and man what a PITA. After much experience, we ended up retensioning every tape before writing. Sending releases to 100+ customers generated a Borg-cube of tapes that had to go into individual boxes for shipping, along with the rainbow of other tape flavors like TK50s and the various 4mm and 8mm tapes.
Documentation was a big deal, because once it was printed, you had a Borg-cube of shrink-wrapped paper and binders that were not going to change until the next release. I still miss proper documentation. Endless web pages are a lot more difficult to sit down and read start to finish.
This article helped me realize that I was shaped by this in the same way that many peoples grandparents were shaped by growing up in the great depression.
> I really envy people doing software with the web. One could do much better these days. But we didn’t have it, and so we were forced to do many things that wouldn’t be sensible today.
It's true there's a lot less cost and overhead to build and ship software today, but this is a double-edged sword: the perceived value of the software is also lower, and so people are less willing to pay and even expect the product to be free. I would argue it's much more difficult to build a software business these days because of this. If you can't sell your product, it's impossible to build a sustainable business.
I struggle with some of my ideas because of this. How do I compete in spaces where people can get applications for free due to ads, with a paid service with no ads.
wlindley•8mo ago
We made the transition from Heathkit HDOS to CP/M and MS-DOS but never shipped a product for MS Windows. We almost had a product ready in 1996 but then MS "upgraded" VB 3 to VB 4 and we started a rewrite, almost completed just in time for the "upgrade" to VB 5 - by which time our market had moved on.
It was a fun time to build custom and specialized hardware and software.
TMWNN•8mo ago
A very unusual case of a company explicitly deprecating its own proprietary OS, and shifting to an external standard, on the same hardware. Tandy giving existing Model 16 customers Xenix and shipping it with new units is the only other case I can think of offhand.
What do you think of this 1983 ACM paper comparing HDOS and CP/M? <http://delivery.acm.org/10.1145/360000/358070/p188-pechura.p...>
badc0ffee•8mo ago
TMWNN•8mo ago
A slightly different way of answering your question is that sometime after the PS/2's launch, IBM began explicitly noting that its software and peripherals were compatible with non-IBM computers. PC DOS 5.0 might have been the first. <https://np.reddit.com/r/vintagecomputing/comments/1jleun5/ni...>