On 9/6/13 12:08 PM, H. S. Teoh wrote:
> 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.

Oh, I'd be glad to still argue :o).

Andrei

On 9/7/13, Andrei Alexandrescu <SeeWebsiteForEmail@erdani.org> wrote:
> No, it doesn't.

You're outgunned! The council has spoken. :o)

On Fri, Sep 06, 2013 at 05:34:15PM -0700, Andrei Alexandrescu wrote:
> On 9/6/13 12:08 PM, H. S. Teoh wrote:
> >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.
> 
> Oh, I'd be glad to still argue :o).
[...]

Well, you may go right ahead, the audience is empty. :-P


T

-- 
Why ask rhetorical questions? -- JC

On 2013-09-06 20:52, H. S. Teoh wrote:

> If you consider requiring a nuclear power plant to power a handheld
> flashlight "awesome", then yes. ;-)

That would actually be pretty awesome. But not so useful :)

-- 
/Jacob Carlborg

On 2013-09-06 22:47, Dmitry Olshansky wrote:

> +1
> That pretty much nails it.

+1

-- 
/Jacob Carlborg

On Friday, 6 September 2013 at 19:10:20 UTC, H. S. Teoh wrote:
> hyphenate*.js still causes annoying page flickering.
>
The relayout had a different reason, but hyphenating caused a long pause before the relayout.
https://github.com/D-Programming-Language/dlang.org/pull/365

On Friday, 6 September 2013 at 17:29:34 UTC, Brad Anderson wrote:
> Even better, I think, would be to have the website just update automatically from git (nightly, perhaps).  Have a script that generates the website from a git tag (or even better, a branch called "public" so hotfixes can be made) and uploads it to dlang.org.
We should have version branches, so that the docs fit to the source code.
Tags are somewhat annoying for bugfixes and github is bad for maling pull requests to two branches, e.g. merge this into 2.063 and master.
Then there is the issue that websites are hard to test automatically.

On 2013-09-06 19:52:20 +0000, "Brad Anderson" <eco@gnuk.net> said:

> hyphenate.js uses a big language lookup table to insert thousands of &shy; into all of the words on the entire page so that the browser can hyphenate the words.  It seems the author has spent a lot of time trying to make it run fast but it's going to be slow just by the nature of what it has to do.  A proper hyphenation algorithm is faster because it takes place during the layout stage so it doesn't need to consider every word for hyphenation (and also would be written in native code) but that option isn't available to javascript as far as I know.

Not Javascript, but try CSS.
https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens

-- 
Michel Fortin
michel.fortin@michelf.ca
http://michelf.ca

On Saturday, 7 September 2013 at 15:31:31 UTC, Michel Fortin wrote:
> On 2013-09-06 19:52:20 +0000, "Brad Anderson" <eco@gnuk.net> said:
>
>> hyphenate.js uses a big language lookup table to insert thousands of &shy; into all of the words on the entire page so that the browser can hyphenate the words.  It seems the author has spent a lot of time trying to make it run fast but it's going to be slow just by the nature of what it has to do.  A proper hyphenation algorithm is faster because it takes place during the layout stage so it doesn't need to consider every word for hyphenation (and also would be written in native code) but that option isn't available to javascript as far as I know.
>
> Not Javascript, but try CSS.
> https://developer.mozilla.org/en-US/docs/Web/CSS/hyphens

That's what the website uses now.  Works on basically everything but Chrome and Opera.  hyphenate.js was supposed to use CSS3 hyphens if the browser supported it but that feature didn't seem to be working properly.  When I applied CSS3 hyphens to dlang.org the display time went from tens of seconds to instantaneous.  After I made that change we kept hyphenate.js around because Andrei didn't want to lose the hyphenation on Chrome but I tried to make it only run on Chrome (I think something was wrong with that though).