Hacker Neue

Preferences
reconnecting parent
Then we should probably mention

http://macpaint.org

(From page HTML source) <!-- ******** HELLO OLD COMPUTER USERS ******** --> <!-- This site is designed to be viewable at 640x480 resolution or higher in any color mode in Netscape/IE 3 or any better browser, so if you're using an LC III or something, you're welcome. In fact, I really hope you are using such a machine, because limiting the site to this level of simplicity wouldn't be worth it unless someone is. Please let me know if you are using an old computer to visit the site so I know it is worth it to someone to maintain this compatibility. I do apologize for the one javascript error that you may get on each page load, but I don't expect it to cause any crashes. The major exception to all of this is Netscape 4. That thing sucks. -->

Does anyone even remember why Netscape 4 was bad?

kragen
Well, like the comment said, it crashed a lot when you tried to run JS on it. It was pretty annoying to binary-search for a bug in your JS when the symptom was a browser crash. Also, it used a lot more RAM than Netscape 3 and was slower, but I don't recall it being better in significant ways.

DHTML in Netscape 4 was also completely incompatible with DHTML in IE 4. In IE you had the DOM, which is an inconvenient and inherently very inefficient interface that you could coerce into doing anything you wanted. In Netscape 4 you had layers. Our team (KnowNow) was working on an AJAX and Comet toolkit at the time (02000). In order to not write separate versions of our Comet applications for the two browsers, we stuck to the least common denominator, which was basically framesets and document.write.

reconnecting OP
Indeed, browsers learned how to hurt people from their earliest days.
spydum
Browsers were changing quickly back then, but if anybody remembers, it became Netscape Communicator and tried to expand to do everything..

https://en.wikipedia.org/wiki/Netscape_Navigator#:~:text=Thi...

reconnecting OP
If I'm not mistaken Netscape Communicator was just a pack of different applications, including NN. The real issue seems to be was specific CSS and some style rendering.
numtel
I think it was a total rewrite, similar to why Winamp 2 was great, fast, not bloated but Winamp 3 was slow, adding extraneous features nobody wanted.
reconnecting OP
True, Winamp 2 was much solid. Unless I'm mistaken Winamp 3 introduce skins and after absolute madness starts.
giantrobot
> Does anyone even remember why Netscape 4 was bad?

Netscape 4 is a broad set of releases over several years. It also wasn't necessarily "bad". It was just largely not mindblowingly better than Netscape 3 (for normal users) while using more CPU and RAM.

I also imagine in this context it's incomplete CSS support is problematic. Netscape 3 will ignore properly commented out CSS (mostly) while 4 will try to interpret what it can and choke on the rest. It's box model doesn't conform to where the CSS spec landed so even if you can give it CSS it can handle, your page is broken in every other browser.

reconnecting OP
I'm jealous of your memory capabilities, and I certainly remember that at some point it was nearly impossible to make website looks in similar way in Netscape and IE.

At the end, there was something like acceptable variation in page view for different browsers.

mr_toad
The rendering differences were at least as much IE’s fault as Netscapes. It took several versions before IE was (mostly) standards compliant.
giantrobot
You're not wrong. IE seemed very much designed around the Embrace, Extend, Extinguish concept. It made it incredibly difficult to write cross-browser CSS.
giantrobot
> I'm jealous of your memory capabilities,

Thanks. Learning web development back then left some deep scars and lasting lessons. I can no longer imagine all the other stuff I haven't retained because I remember stupid browser quirks from nearly three decades ago.

Getting many designs working consistently between IE and Netscape was impossible. The 640px wide left-aligned table layout was popular for years because it was the easiest common denominator that looked acceptable in both browsers.

reconnecting OP
When back to this time the web was mostly a pain, especially for developers, there was also some magic.

Take for example VRML, particularly VRML 2.0. I don't remember the software name, but there was a chat system within a virtual world, perhaps running in a browser (1).

1. https://csdl-images.ieeecomputer.org/mags/cg/1999/02/figures...

jfim
NN4 tended to crash more than NN3, it may have been due to the rushed development during the browser wars.
reconnecting OP
There was problem with styles and tables.

https://sbpoley.home.xs4all.nl/webmatters/netscape4.html

cmrdporcupine
From vague memories I remember NN4 on classic MacOS was, I recall, a total memory leaking / crashing shitshow. I worked in a shop that had a bunch of Macs and the rule was you couldn't run FileMaker (which they used a lot) and Netscape at the same time because the two would just run over each other memories. The glory days of lack of memory protection on MacOS 7.6.

But I also don't think 3 was much better.

This item has no comments currently.