5 ms·

Way too many C#/Java developers who used JS in the early 2000s and hated it still think it's the same language.

EvanPlaice 11y ago
I probably fall into the opposite category. Moved away from statically typed languages back when .NET 3.5 was released and have settled on JS primarily JS for the past few years. I'm wiling to bet C# is 10x better than the last time I used it. Except, I don't have a good excuse to use it again to see.
douche 11y ago
Way too many C#/Java/Haskell/Python/Ruby/Scala developers still use it today and still think it's a heaping pile of garbage.
voltagex_ 11y ago
The MS AJAX control toolkit and UpdatePanel probably didn't help, either. I think I can probably say that Javascript engines are an order of magnitude faster than they were 16 (!) years ago. If I may make a generalisation, C#/Java devs are more likely to be "enterprise" developers and said enterprises were more likely to be the ones on IE <11. I know I fought damn hard to upgrade from IE8 just a couple of years ago. My webdev skills suffered as a consequence, too. Microsoft moved pretty fast once they realised that IE needed to compete again - and Visual Studio evolved alongside it (mostly). VS2015 is now a pretty good development environment for Javascript/Typescript and even includes some Grunt build support (although I haven't had a play with it yet).
- bzbarsky 11y ago
  > I think I can probably say that Javascript engines are an order of magnitude faster than they were 16 (!) years ago. Two orders of magnitude. I just checked, and on my laptop http://web.mit.edu/bzbarsky/www/mandelbrot-clean.html http://web.mit.edu/bzbarsky/www/mandelbrot-clean.html (the first JS thing I wrote where performance of the language itself seriously mattered) runs in about 30-60ms in modern browsers. On the same hardware, it runs in about 2200ms in Firefox 3, which is the last pre-JIT version of Firefox. Other benchmarks I've tried show similar improvements results. And that's only going back to 2008; the interpreter was a good bit slower another 8 years before that.

I probably fall into the opposite category. Moved away from statically typed languages back when .NET 3.5 was released and have settled on JS primarily JS for the past few years. I'm wiling to bet C# is 10x better than the last time I used it. Except, I don't have a good excuse to use it again to see.

douche 11y ago

Way too many C#/Java/Haskell/Python/Ruby/Scala developers still use it today and still think it's a heaping pile of garbage.

voltagex_ 11y ago

The MS AJAX control toolkit and UpdatePanel probably didn't help, either. I think I can probably say that Javascript engines are an order of magnitude faster than they were 16 (!) years ago. If I may make a generalisation, C#/Java devs are more likely to be "enterprise" developers and said enterprises were more likely to be the ones on IE <11. I know I fought damn hard to upgrade from IE8 just a couple of years ago. My webdev skills suffered as a consequence, too. Microsoft moved pretty fast once they realised that IE needed to compete again - and Visual Studio evolved alongside it (mostly). VS2015 is now a pretty good development environment for Javascript/Typescript and even includes some Grunt build support (although I haven't had a play with it yet).

bzbarsky 11y ago
> I think I can probably say that Javascript engines are an order of magnitude faster than they were 16 (!) years ago. Two orders of magnitude. I just checked, and on my laptop http://web.mit.edu/bzbarsky/www/mandelbrot-clean.html http://web.mit.edu/bzbarsky/www/mandelbrot-clean.html (the first JS thing I wrote where performance of the language itself seriously mattered) runs in about 30-60ms in modern browsers. On the same hardware, it runs in about 2200ms in Firefox 3, which is the last pre-JIT version of Firefox. Other benchmarks I've tried show similar improvements results. And that's only going back to 2008; the interpreter was a good bit slower another 8 years before that.