D Web Services Application Potential?

[Brandon Ragland via Digitalmars-d]

On Thursday, 30 July 2015 at 05:50:56 UTC, Ola Fosheim Gr wrote:
> On Thursday, 30 July 2015 at 03:56:25 UTC, Brandon Ragland 
> wrote:
>> Regarding JavaScript being slower, this benchmark[1] seems to 
>> indicate that on average, JavaScript on V8 is at-least 4X 
>> slower than a g++ compiled native package. It also appears to 
>> use anywhere from 2-4X as much memory.
>
> I think speed optimized javascript is at 50% of regular 
> non-SIMD C. Javascript suffers when you use high level 
> constructs and convenience frameworks, but so does C++ (which 
> is why people don't use them). It will probably take a long 
> time for javascript to get proper cross browser SIMD support 
> though...
>
> When you get rid of IE9 the real bottleneck to combat is the 
> C++ browser runtime, reflow and "random delays" etc.
>
> Memory usage/performance are issues you can limit by using 
> typed arrays/free lists. But the browser impose limitations on 
> memory usage...

This might be true, but then you're boiling down the whole reason 
JavaScript took off: Frameworks. JavaScript is a horrendous 
language to use, unless you throw some common framework at it 
that attempts to unify all the browser quirks into easy APIs, 
such as jQuery or Mootools.

JavaScript was never designed to be a language to run games or 
high-performance software with. The only reason we see that today 
is because of the trend towards "Web 2.0" and "google my 
software" where everyone wants everything to be easily accessible 
in the browser. We an overflow os knuckle-head JavaScript 
developers, and there bosses, we now have what we see today: 
Frameworks on-top of frameworks to complete the simplest things, 
because JS as a language cannot do it effectively.

Any language can be optimized more heavily if we throw the 
framework(s) out. However, your development time sky-rockets. In 
today's moving world, companies simply don't have time for that. 
Thus the end result: bloated web pages that stall and lag due to 
un-optimized framework heavy JavaScript.

In all the years I've been working, there was never one language 
I avoided more: JavaScript. My team and I have nick-named it 
"booty-script" because of it's lack of modern day anything, and 
it's terrible semantics.

Most people don't write JavaScript. They right jQuery, or 
Mootools, or some other framework API that abstracts away the 
JavaScript ridiculousness.