If you ask most professional developers (as compared to a Hobbyist, see "What's the Difference between a Hobbyist and a Professional") about JavaScript and you'll likely get non-positive responses. Most professional developers – that is those that get paid – don't like JavaScript because it's hard to make a craft of developing when you're limited by your language. Most professional developers have come to expect a set of tools to help them develop more reliable code and to create the code faster in the first place. JavaScript isn't bad for tying a few loose things together, however, developing enterprise scale applications is not what it was designed for.
Created
November 5, 2012 15:18
-
-
Save robashton/4017704 to your computer and use it in GitHub Desktop.
If you ask most professional .NET developers (as compared to those beardy weardies that get paid less money but have more fun doing development in languages such as Ruby, Python or Javascript) about JavaScript you'll likely get non positive responses because they've never really tried to work with it in earnest. Most professional developers (those that work in the enterprise world at least) don't like JavaScript because it's hard to move to a world where you're not limited by your language and can do pretty much whatever the hell you want. Most professional developers have come to expect to have crutches available (in the form of tooling) to get around the fact that they're pretty much just generating code all over the place and not giving much thought to design. JavaScript is great at tying lots of small things together and writing small things with, however developing huge monolithic enterprise applications is not what it was designed for.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment