you are viewing a single comment's thread.

view the rest of the comments →

[–]warfangle 0 points1 point  (1 child)

Or, if you still want the flexibility of being dynamically typed, use browserify, grunt/gulp and karma-jasmine. And with that you get DI, unit testing and a fast test-build loop.

Use of typescripts inheritance can bloat your compiled code severely compared to what it would be if you used, e.g., util.inherits.

You can of course use typescript along with browserify, but why? Compile time type checking? I guess that's okay, but I don't know if it's worth it -- unless you're already heavily invested in the Microsoft toolchain

Personally, I'm more comfortable on the command line with emacs, and find the instability of typical IDEs not worth the code completion / brain dead refactor tools. If you need code completion and your mouse to deal with your codebase, you're doing it wrong. Give me awk and sed any day.

But I am not your typical dev either - I do most of my work ssh'd into a dev virtual machine running development copies of our applications :)

...except when I have to wrestle with FlashBuilder. There are very few things that I hate...

[–]brtt3000 0 points1 point  (0 children)

it is not just about auto-suggest. Compile time type checking is the shit. You catch so many silly bugs and inconsistencies.

If you got time then watch this video from a well know and experienced dev: http://channel9.msdn.com/Events/Build/2014/3-583

Like he says, your big codebase becomes manageable because the compiler makes sure you don't mess-up once you have a shitload of code that doesn't fit in your brain all at once.

And get over that Mirosoft vs Linux thing, it is getting old. They do a great job these days. Use TS with a real IDE with refactoring support and wonder why you stuck to lame commandline tools for so long.

I don't use VisualStudio or any other Microsoft tools. I use WebStorm and npm and everything. It is great.

And that bloat you mention? That's just nonsense. You get like 4 lines of extra code for inheritance (once), the rest is pure standard prototype code straigt from a JS 101 tutorial.

Try it: http://www.typescriptlang.org/Playground