News for hackers. Stuff that matters.
Re:Announcing TypeScript 2.0 by LeanderK on Thursday September 22, 2016 @04:25PM (#12560064)
maybe its just what your used to. Most of my time I code in Java (and a bit of Scala) and i only look at the source code as a last resort. This is not really possible with JS. But i imagine with a lot of background in dynamic languages you instinctively look at the source-code and therefore not use the types that much.
Re:Announcing TypeScript 2.0 by jeremiep on Thursday September 22, 2016 @04:35PM (#12560145)
I looked at SO much Java sources because the method signatures weren't complete enough.

I would never have been able to integrate netty into our game servers that optimally with only the docs as reference for one. Yet its documentation is really, really good. I still wanted to know its internals in order to hit the fast paths.

Whether you're using static or dynamic types, the very same holds true to build robust software: understand what you're doing.

Managing complexity and reducing state will always be the biggest factors to quality, regardless or type systems.

Re:Announcing TypeScript 2.0 by mercurial on Friday September 23, 2016 @12:25AM (#12562302)
Well, considering the number of dependencies a typical web project has, I can tell that I'm far from understanding the internals of every library used in our codebase. I mean, of course you'll want to do that in some cases where performance is really important, but generally speaking type signatures and docs should be enough.
Re:Announcing TypeScript 2.0 by LeanderK on Saturday September 24, 2016 @06:46AM (#12570399)
i din't say that i don't look at source code, but not intuitively. I look at it when the method is very confusing, or i have to optimise one path, it is undocumented and important etc. What i wanted to say is that types give you a pretty good first intuition to what the method does and how (including exceptions). They help me navigate my way through the code, especially with DSL like the excellent jooq (http://www.jooq.org)
Re:Announcing TypeScript 2.0 by qwertyuiop924 on Thursday September 22, 2016 @05:26PM (#12560504)
...And I hate java (for perverting OO, and being annoyongly verbose), and come from a highly dynamic background.

It's ultimately a matter of preference, though.

Re:Announcing TypeScript 2.0 by LeanderK on Saturday September 24, 2016 @06:50AM (#12570406)
not that java is my favourite language, i would even say that i despise it. But its here to stay and the discussion was about shitty static type-systems where Java is the poster-boy ;)
Re:Announcing TypeScript 2.0 by qwertyuiop924 on Saturday September 24, 2016 @03:10PM (#12572123)
It's not even the shitty type system: C's is arguably even worse.

No, it's the fact that it's effectively the new COBOL.

Re:Announcing TypeScript 2.0 by Roboprog on Sunday September 25, 2016 @01:17PM (#12576216)
Java: the language so ugly it has to wear a (IDE plugin) bag over its face while you're doing it.

Yes, I'll go have that talk with H/R now...