D could catch this wave: web assembly

[Kagamin via Digitalmars-d]

On Friday, 19 June 2015 at 15:13:11 UTC, Joakim wrote:
>> Hmm... Web: write once with html, css, js. Native: write three 
>> times in obj-c, java, c#. Not sure why the former should sink 
>> and not the latter.
>
> Because writing it once in HTML/CSS/JS takes you much longer 
> than writing it in Java, while being less responsive, then you 
> get to enjoy all the myriad ways your UI will be screwed up by 
> the different browsers.

High DPI settings screw up native UI too if it's not 
pixel-precise, and ignoring user preferences is infraction, I'm 
afraid. And this is where web actually shines: it's designed to 
adapt gracefully to any user settings. Well, of course when site 
design strays from how web was designed to work, it runs into 
problems, that should be obvious.

I didn't really try to write java, but my impression is that java 
usually requires huge amounts of boilerplate code, while web is 
usually succinct.

>>> But what do they do instead of starting anew?
>>
>> Web and native are not really related, one doesn't preclude 
>> existence of the other and doesn't depend on it.
>
> That doesn't answer the rhetorical question you're responding 
> to. In any case, they _are_ competing technologies, and one is 
> so bad that it is manifestly losing out.

Dunno, I don't see there losses, maybe because they only happen 
on mobile. Yeah, you said nothing about how this is related to 
desktop as if it doesn't exist.

On Friday, 19 June 2015 at 15:45:20 UTC, Nick Sabalausky wrote:
> We need some sort of SVG-BSON, or something along those lines.

There's EXI.