Having hyphenator.js on the site slows down the browsing experience immensely, especially on mobile. I know I personally avoid the dlang.orgsite on my Galaxy Nexus and on my Nexus 7 because of this reason.
Since the whole web is right-aligned and users would much rather have a site that loads fast and without content flashes than a site with hyphenation, I believe the library should be removed. I say this as someone who is a typography nut and loves hyphenation. A printed book without it is not worth buying. But the cost of implementing it in JS for web pages is too high. There's a reason why no major website uses this approach. On Tue, Jul 16, 2013 at 9:27 AM, H. S. Teoh <hst...@quickfur.ath.cx> wrote: > On Tue, Jul 16, 2013 at 10:16:28AM -0500, captaindet wrote: > > On 2013-07-15 20:48, Brad Anderson wrote: > > >unfortunately, do not support CSS3 hyphens so they still use the slow > > >hyphenator.js. > > > > pls remove hyphenator.js altogehter. i see everyone complaining about > > it and no one wanting it. the words in the english language are > > usually short enough so that hyphenation is not really necessary. > [...] > > +1. If people are using browsers that don't support hyphenation, then so > be it. They will just get slightly more line-wrapping, that's all. No > harm done. This is too tiny a detail to pay such a big price (slow > loading, flashing, scrolling disruption, etc.) for. > > (I'm one of those people whose browsers don't support hyphenation. That > doesn't make the site any less useful (I turned off JS on dlang.org > because hyphenator.js is so annoying -- the only difference I noticed > was that the site is significantly more usable that way). This is really > a nice-to-have feature that doesn't deserve the price we're paying for > it, not an indispensible feature.) > > > T > > -- > First Rule of History: History doesn't repeat itself -- historians merely > repeat each other. >