News for hackers. Stuff that matters.
Re:Why does TypeScript have be the answer to anything? by seanmcdirmid on Tuesday October 02, 2012 @03:16PM (#4603688)
To be more specific you have to use some crazy static analysis technology (global interprocedural analysis) that is intractable unless you sacrifice accuracy. Human have similar problems as compilers/tooling, though they are a bit better at understanding nuanced conventions to make better judgements about what dynamic code is doing.
Re:Why does TypeScript have be the answer to anything? by jmmcd on Tuesday October 02, 2012 @03:26PM (#4603745)
Yes, of course, we sacrifice accuracy. I said so at the very start. But imagine a "go to definition" tool that works correctly for 99% of cases and barfs or goes to the wrong place on the others. If the alternative is no tool at all, that still sounds pretty useful!

I admit there are cases (refactoring is an example) where if you don't trust the tool 100% you won't use it. But many tools are not like that.

Re:Why does TypeScript have be the answer to anything? by seanmcdirmid on Tuesday October 02, 2012 @07:42PM (#4604997)
Well, you'd be without feedback alot, state of the art in type recovery is nowhere near 99%. Your libraries can exploit the flexibiliy of a dynamic language (meta programming, crazy unions) and make the job much harder. Typescript seems very interesting in the way they handle type retrofits on libraries, but I haven't really absorbed it yet.