The State and Future of JavaScript

J

Jorge


Yet some important but obvious things are not being said clearly
enough in this one, e.g., that after ten years of (badly focused)
committee work they were still non-delivering (*)... this is what led
to (someone with the guts and the how-to) "standing on the Khazad-dum
bridge facing down the ES4rog".

(*)Don't confuse their "non-delivering" with "it (ES/JS) was stalled
for a very long time because Netscape killed itself and Microsoft
stagnated the browser after winning monopoly status.", one thing has
nothing to do with the other, afaics.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,769
Messages
2,569,579
Members
45,053
Latest member
BrodieSola

Latest Threads

Top