Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I Don't Use Netscape (1999)

complang.tuwien.ac.at

Post reply on HN
Print view View original

41–50 of 285 posts

Re: Why I Don't Use Netscape (1999)

#41

Post by weberer »

rrwo wrote: post #8
NotYourLawyer wrote: post #3

My modern version of this is browsing with JavaScript disabled. Most of the sites that don’t work weren’t worth my time anyway.

I disagree. Using AJAX to hit internal APIs to load or update content improves performance of the site, and can make it easier to maintain.

Is there any evidence of this? All the sites I've seen that use extra requests to load text always seem to take multiple seconds to load. Whereas most pages that use server side rendering generally load under 100ms.

Re: Why I Don't Use Netscape (1999)

#42

Post by tannhaeuser »

rrwo wrote: post #8
NotYourLawyer wrote: post #3

My modern version of this is browsing with JavaScript disabled. Most of the sites that don’t work weren’t worth my time anyway.

I disagree. Using AJAX to hit internal APIs to load or update content improves performance of the site, and can make it easier to maintain.

The argument is that JS-heavy site design indicates worthless content on average. Not that it's easier to maintain for the site owner (which might or might not be the case), or more realistically, creates job opportunities for "web developers".

Re: Why I Don't Use Netscape (1999)

#43

Post by Kiro »

b112 wrote: post #17
rrwo wrote: post #8

Earlier quoted context omitted.

I disagree. Using AJAX to hit internal APIs to load or update content improves performance of the site, and can make it easier to maintain.

I disagree. Using AJAX to hit internal APIs to load or update content improves performance of the site, and can make it easier to maintain. The reality is, with node junk, the average site uses 10mb of js, taking 5s to render, to show 1kb of text. Get rid of that 10mb of js, all those fonts, and you don't need to update only part of a page. It will load and render in 10ms.

That has nothing to do with Node.

Re: Why I Don't Use Netscape (1999)

#45

Post by johnchristopher »

tannhaeuser wrote: post #19
badsectoracula wrote: post #13

Considering all the discussions about JavaScript and sites with primarily text requiring it, this looks like the more things change, the more they remain the same :-P. Also see Wirth's Plea for Lean Software[0] from 1995 for another "timeless" issue. I did find this bit interesting too... > Apart from this practical reason, there's a principal one: The first time I invoked Netscape, it said that it is obsolete and re…

Firefox on Ubuntu (which I'm not using anymore for these and other reasons) and presumably on other OSs does exactly that: refuse to open new tabs/sites once every two weeks or so, telling me "one more thing we need to do" ie self-update. So you're loosing all your browsing context, though FF does a better job restoring it after restart than it used to, but still that's user-hostile and self-important as fuck. And th…

On Ubuntu/Debian, a work-around is to put Firefox on hold: sudo apt-mark hold

Will not work with snap though.

Re: Why I Don't Use Netscape (1999)

#47

Post by tannhaeuser »

DonHopkins wrote: post #31
NotYourLawyer wrote: post #3

My modern version of this is browsing with JavaScript disabled. Most of the sites that don’t work weren’t worth my time anyway.

Yeah, who needs google maps anyway? Just use the Xerox PARC Map Viewer. https://en.wikipedia.org/wiki/Xerox_PARC_Map_Viewer

https://wiki.openstreetmap.org/wiki/Mapscii
Post reply on HN