On Fri, Sep 06, 2013 at 08:51:29PM +0200, Jacob Carlborg wrote: > On 2013-09-06 20:24, H. S. Teoh wrote: > > >If I had to guess, it's because we finally nuked hyphenate.js and > >hyphenate-selectively.js, both of which are big resource hogs that > >provide only barely-noticeable functionality. > > Why do these script take so long time in the first place to > download/run? [...]
Beats me. All I know is that they (or their ilk) made browsing dlang.org so painful that I decided to block javascript completely in dlang.org. It became surprisingly easier to use after that. Even on a fast machine with lots of RAM where you wouldn't notice the loading/running times, hyphenate*.js still causes annoying page flickering. I honestly am totally puzzled why people thought such a thing was a good idea in the first place, considering that (1) it requires a huge amount of CPU power and RAM, (2) it requires high-speed internet access which not everybody has, and (3) even after that it still flickers like it was a BASIC program running on a 6502 processor from the 70's. Like I said, the only way it can be considered "awesome" is if you consider powering a handheld flashlight with a nuclear power plant to be an "awesome" idea. But anyway. That's enough rubbing it in. It's gone now, good riddance and all that, and we don't have to argue over this anymore. T -- "Real programmers can write assembly code in any language. :-)" -- Larry Wall
