Re: Redesign of dlang.org
Nick Sabalausky via Digitalmars-d <digitalmars-d <at> puremagic.com>
2014-04-24 08:17:07 GMT
(Argh! Accidentally emailed this to digitalmars-d <at> puremagic.com twice!
Actually posting to NG now...)
On 4/23/2014 6:48 PM, H. S. Teoh via Digitalmars-d wrote:
> until sometime in the last few
> years I got so sick of JS eating up CPU, memory, causing needless
> browser slowdowns, popping up unwanted ads and nag dialogs, that now I'm
> back to JS being off by default, and only (grudgingly) enabled for a
> handful of specific sites that actually *need* it. It's amazing how much
> faster the web suddenly became, overnight.
That's why I do it! That plus the lack of modal CSS pop-in windows.
(Seriously, no sooner do the browsers finally kill off popups, but then
overzealous designers go replacing them with *modal* versions! And these
new ones break basic browser functionality even *more*.)
The *truly* amazing thing is that many of those slow-with-JS sites are
using JS/AJAX specifically *because* they actually believe it makes
their site faster (I bet many of them are probably running on Node.js or
PHP, too). Always, of course, based on the same half-baked,
never-tested, but oft-repeated theory that reducing a few fractions of a
kilobyte by doing partial page-reloads actually makes the web noticeably
faster (yea right).
Shit, even in the days before 14.4 modems, let alone 56k or broadband,
transferring the actual HTML was practically nothing, it was the
occasional use of an image or two that slowed things down - *because
those take a heck of a lot more bytes than HTML*. Even today, one
gravitar image, one "share on site x" logo, or one stock photo of a