3 ms·
Sounds reasonable :). Although I dread imagining a JavaScript equivalent of a "100+ project .NET solutions" built in spirit of "rapid development".
by _random_ 13y ago
Sounds reasonable :). Although I dread imagining a JavaScript equivalent of a "100+ project .NET solutions" built in spirit of "rapid development".
- pjmlp 13y agoI do like dynamic languages for quick prototypes, but my experience on the scale of enterprise projects and their code quality, just increased my preference for static typing for production code.
- int_19h 13y agoTypeScript FTW. https://nodejstools.codeplex.com/workitem/291 https://nodejstools.codeplex.com/workitem/291
- pjmlp 13y agoThanks for the info. Now if only we had customers asking for TypeScript. I really like its design as a JavaScript superset.
- DrJokepu 13y agoBasically the important bit to remember when using dynamic languages in production is that you have to be extremely serious about writing (good) tests. It’s easy to get lazy when using a statically typed language as the compiler will do much of the work for you (especially if you take full advantage of the type system’s features). You can’t get away with that when writing e.g. JavaScript.
- pjmlp 13y agoThat is exactly the main problem. Enterprise developers don't write tests if their managers don't force them to, gets specially hairy when you have multiple consulting companies across multiple sites. So you get JavaScript/Ruby/Python code with zero tests. No sane people tries to refactor such code.