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.
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.
I don't see how this contradicts any of what they said, unless they've edited their comment.
You're right we had graphical apps, but we did also have very little video. CuSeeMe existed - video conferencing would've still been a thing, but with limited resolution due to bandwidth constraints. Video in general was an awful low res mess and would have remained so if most people were limited to ISDN speeds.
While there were still images on the web, the amount of graphical flourishes were still heavily bandwidth limited.
The bandwidth limit they proposed would be a big deal even if CPU speeds continued to increase (it could only mitigate so much with better compression).
> 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.
Netscape was talking about making the Web an app platform to replace Microsoft Windows even way back then. The world we're living in today is exactly what they envisioned.
Electron wouldn’t be possible back then.
Not JavaScript. Facebook.
Netscape 2 support javascript on 16-bit Windows 3.1