Replying to @webdevjsj @ah_wms
Or Worse even yet the original Front Page 馃槈馃槀
1
1
I know, Right? There is an epic geek scene in one of the later Big Bang Theory episodes (season 10 or 11?) where the guys including Bert are at the CalTech cafeteria table playing "name your fave dead search engine" - mad respect to whoever wrote that bit of accurate hilarity! 馃ぃ
2
2
Nope. Replaced on Mac by Safari and of course every Chromium core variant (Chrome, Edge, Brave...) as well as Firefox and Tor which use a different rendering engine than the Chromium dominant browser world of today. I liked Camino very much myself!
1
I used it a lot on my old iMac. Then I switched to Firefox but then went to chrome as I liked the dev tools better
1
1
This is me mumbling terrible things about today's devtools Tools in general. For the good old days when they were simple. In many ways I think they have contributed to the devolution of open web.
1
They鈥檝e been a godsend to me for debugging JS things on the fly. The kids going into the game these days will never know the pain of old school debugging!
1
1
Oh you are right but I have to snort back it's in my contract as the webs fairy godmother. If you were writing your declarative code well debugging was not the primary problem it was the browser hacks and workarounds during the I6 issues and Dom incompatibilities.
1
1
Flashback right there! I remember having to explain to designers the IE6 transparent png issues and the box model problem. Thankfully all things of the past.
1
1
Replying to @webdevjsj @ah_wms
Box model hack ack ack ack. Doctype switching. Those were the days but I tell you I preferred that as hard as it was then the near browser monoculture we have today because you would think that with chromium core being the dominant rendering engine we'd have better interop. Nope!

Dec 31, 2020 路 12:14 AM UTC

1