D => asm.js for the web?

[Nick Sabalausky]

On Sat, 23 Mar 2013 14:22:04 +0100
"bearophile" <bearophileHUGS at lycos.com> wrote:

> Dan:
> 
> > There is huge benefit and it is one of the big selling points 
> > of Dart. You write in a familiar OOP language with great 
> > toolset and out comes working javascript. I don't know 
> > javascript - I've started to learn a few times but was repelled 
> > by it. But most traditional OO programmers can grok Dart in a 
> > few days, plus it has great tools. If D could do the same it 
> > would be great.
> 
> I prefer TypeScript. It doesn't require a new JavaScript VM, and 
> it looks designed very well. I am waiting for a 
> TypeScript=>asm.js compiler :-)
> 

While some of this stuff is fairly interesting, if you're doing so much
DHTML that JS's downsides become a problem, then you're doing way
too much DHTML. Time to either:

1. Pre-bake stuff (There are sooo many pages out there that do DOM
manipulations or even AJAX requests during page load or "onload". This
is, of course, completely moronic because if it's done during/upon page
load, it *could* have all been just done ahead of time and baked into
the original page. The only thing "during/upon page load" JS ever has
any legitimate reason to do, is undo certain "JS-disabled" elements on
the page - and even that's only for cases where <noscript> is
unsuitable.)

2. Put some of the processing back on the server, where it belongs.

3. Rip the stupid thing out of the web browser, because it's clearly
not a goddamn document.