> Ever try to use different JavaScript tools with conflicting jQuery versions? Yeah, that sucks. So library conflicts are unique to JavaScript? also I never ha

> Ever try to use different JavaScript tools with conflicting jQuery versions? Yeah, that sucks. So library conflicts are unique to JavaScript? also I never had compatibility issues with jQuery because it does a good job at staying backward compatible. > How about trying to figure out how to make 20 javascript include files load quicker as one request? Yeah that sucks too. I can do it with one shell script, if you have a problem figuring that out, the issue is not with JavaScript... > Performance? Let me just point to the old Facebook mobile app made with JS & HTML5. It sucked. Enough said. So Facebook's mobile app is representative of ever web app ever created? This statement is ridiculous in so many ways. > How about unit testing JavaScript? I've never tried it, but it sure sounds like fun. If you can't explain why it's a bad experience, you shouldn't bother stating it, otherwise it's just BS. > My biggest problem with JavaScript is code security. If I make some awesome product, there is no way to protect my code. How can we expect game makers to write apps in 100% JavaScript and HTML5 if they can't protect their intellectual property? There are 99999 minifiers and obfuscators out there and don't act like you never heard of disassemblers. > There are compiling tools like Closure, unit test frameworks, minify, coffee script, TypeScript and a bunch of other tools. But to me, they all try to make up for the weaknesses and problems with JavaScript. JavaScript is a mess and we spend a lot of time trying to work around all of it's problems. It's like saying that Visual Studio and all tools used with .NET make up for the weaknesses of C#. > It is possible to program in Silverlight, Java or Flash and run that in the browser instead of JavaScript, but they all have their own problems and lack universal mobile support. I believe Microsoft's new TypeScript is a step forward for JavaScript, but I think we need to start planning to go a whole different direction. We need a new universal client side programming model, because JavaScript sucks. The title should be changed: One .NET guy doesn't like programming in JavaScript.