Have you ever actually used e.g. JavaScript-compiled Nim? Go ahead and write "Hello, World!" in Nim, compile it to JavaScript, and post back with the results.
It literally doesn't work for any version of IE, and only partially words for Edge. Hell, it can't even deal with blob objects on all browsers. That's the quintessential file abstraction used in the browser, and it only works for 3/8 of the browsers listed! That's pathetic. Guess what? Works with jQuery!
No thanks. Being a full-stack developer means you have a lot of languages and frameworks competing for space in your mind. Learning the trendy framework of the day for the browser is a waste of mental real estate. Proper OOP in JavaScript, combined with jQuery is fast and efficient, and works across browsers.
Michael Gutierrez
nope. Nor Elm, nor ReasonML. I've looked at ATS compiled to JS though, and the runtime was a lot smaller than jQuery. What I've done in my projects is still #2, of the options I gave. >any version of IE so yeah, 0.0.0, and 0% of your customers. I'll grant that it's nice to be able to tell your boss that you definitely haven't excluded anyone. crossing the dom/javascript boundary as frequently as jQuery must do will always be more expensive than working with a vDOM and rendering it with it a diffing algorithm.
Owen Taylor
Of course, because it doesn't provide any of the benefits of jQuery.
Also,
Dylan Lewis
3+% of that is IE, and it's IE 11, not exactly IE 6.
Jace Collins
netmarketshare.com/browser-market-share.aspx I'm seeing estimates between 10-13% marketshare for IE+Edge. Even best case scenario, Edge, you're talking about a failure of the Fetch API to work with blob objects, which is unacceptable.
