Echo JS 0.11.0

<~>
andrei.gabreanu 2855 days ago. link parent 1 point ▲ ▼
Well typescript is first and foremost important for the types system which es6 / babel do not provide. And since you can have the best from both worlds (es6 + types + babel) - why not :)

Replies

tracker1 2854 days ago. link 1 point ▲ ▼
Because at runtime, typescript doesn't provide type checking... ie: when interacting with a foreign API... Beyond this, with small, well-organized modules, TypeScript tends to only add boilerplate, and doesn't tend to prevent as many errors as the time to write boilerplate prevents.

I can see why some would like it, I just don't find much value in it.
sylvainpv 2853 days ago. link 1 point ▲ ▼
I agree that type checking at runtime is really important for JS applications. That's why I made this: http://objectmodel.js.org ; it works really well with Babel, and it has non-nullable types by default from the beginning