81–90 of 226 posts
Earlier quoted context omitted.
Probably was "Windows 3.11, For Workgroups" as iirc Windows 3.1 didn't ship with a TCP/IP stack
There was a sockets API though ( https://en.wikipedia.org/wiki/Winsock ) and IIRC we all used Trumpet Winsock on Windows 3.1 with our dialup connections. But could have been 3.11 - my memory is a bit hazy.
Earlier quoted context omitted.
Transputers. Lots and lots and lots of transputers. (-:
And https://en.wikipedia.org/wiki/Connection_Machine
BTW, IBM has been doing a fine design job with their quantum computers - they aren’t quite the revolution we were promised, but they do look the part.
I sometimes wonder what the alternate reality where semiconductor advances ended in the eighties would look like. We might have had to manage with just a few MB of RAM and efficient ARM cores running at maybe 30 MHz or so. Would we still get web browsers? How about the rest of the digital transformation? One thing I do know for sure. LLMs would have been impossible.
We had web browsers, kinda, in that we'd call up BBSes, and use ansi for menus and such. My Vic20 could do this, and a C64 easily, really it was just graphics that were wanting. I was sending electronic messages around the world via FidoNet and PunterNet, downloaded software, was on forums, and that all on BBSes. When I think of the web of old, it's the actual information I love. And a terminal connected to a bbs cou…
Prodigy established a (limited) graphical online service in 1988.
Earlier quoted context omitted.
And imagine if telecom had topped out around ISDN somewhere, with perhaps OC-3 (155Mbps) for the bleeding-fastest network core links. We'd probably get MP3 but not video to any great or compelling degree. Mostly-text web, perhaps more gopher-like. Client-side stuff would have to be very compact, I wonder if NAPLPS would've taken off. Screen reader software would probably love that timeline.
you are wrong. Windows 3.11 era used CPUs with like 33mhz cpu, and yet we had TONS of graphical applications. Including web browsers, Photoshop, CAD, Excel and instant messangers Only thing that killed web for old computers is JAVASCRIPT.
JavaScript is innocent. The people writing humongous apps with it are the ones to blame. And memory footprint. A 16 MB machine wouldn’t be able to hold the icons an average web app uses today.
Earlier quoted context omitted.
And imagine if telecom had topped out around ISDN somewhere, with perhaps OC-3 (155Mbps) for the bleeding-fastest network core links. We'd probably get MP3 but not video to any great or compelling degree. Mostly-text web, perhaps more gopher-like. Client-side stuff would have to be very compact, I wonder if NAPLPS would've taken off. Screen reader software would probably love that timeline.
I have a Hayes 9600kbps modem for web surfing.
I sometimes wonder what the alternate reality where semiconductor advances ended in the eighties would look like. We might have had to manage with just a few MB of RAM and efficient ARM cores running at maybe 30 MHz or so. Would we still get web browsers? How about the rest of the digital transformation? One thing I do know for sure. LLMs would have been impossible.
For me the interesting alternate reality is where CPUs got stuck in the 200-400mhz range for speed, but somehow continued to become more efficient. It’s kind of the ideal combination in some ways. It’s fast enough to competently run a nice desktop GUI, but not so fast that you can get overly fancy with it. Eventually you’d end up OSes that look like highly refined versions of System 7.6/Mac OS 8 or Windows 2000, whic…
What killed that balance wasn't raw speed, it was cheap RAM. Once you could throw gigabytes at a problem, the incentive to write tight code disappeared. Electron exists because memory is effectively free. An alternate timeline where CPUs got efficient but RAM stayed expensive would be fascinating — you'd probably see something like Plan 9's philosophy win out, with tiny focused processes communicating over clean interfaces instead of monolithic apps loading entire browser engines to show a chat window.
The irony is that embedded and mobile development partially lives in that world. The best iOS and Android apps feel exactly like your description — refined, responsive, deliberate. The constraint forces good design.
I sometimes wonder what the alternate reality where semiconductor advances ended in the eighties would look like. We might have had to manage with just a few MB of RAM and efficient ARM cores running at maybe 30 MHz or so. Would we still get web browsers? How about the rest of the digital transformation? One thing I do know for sure. LLMs would have been impossible.
BBSes existed at the same time and if you were into BBSes you were obsessive about it.
I sometimes wonder what the alternate reality where semiconductor advances ended in the eighties would look like. We might have had to manage with just a few MB of RAM and efficient ARM cores running at maybe 30 MHz or so. Would we still get web browsers? How about the rest of the digital transformation? One thing I do know for sure. LLMs would have been impossible.
For me the interesting alternate reality is where CPUs got stuck in the 200-400mhz range for speed, but somehow continued to become more efficient. It’s kind of the ideal combination in some ways. It’s fast enough to competently run a nice desktop GUI, but not so fast that you can get overly fancy with it. Eventually you’d end up OSes that look like highly refined versions of System 7.6/Mac OS 8 or Windows 2000, whic…
Hypercard was absolutely dope as an entry-level programming environment.