IssueRaiser

I tend to think that the sophistication of the tools reflect the extent that the language is broken.

I tend to think that the sophistication of the tools reflect the extent that the language is broken. Valgrind doesn't need to exist for the Java user. You don't need class boilerplate getter/setter generators for Scala. Nobody needs NPE static analyzers for Rust. The need for rename refactoring tools is drastically diminished by the existence of type inference, almost to the point where `:%s/Foo/Bar/g` is entirely adequate. The non-existence of tools that you find in other languages might signal an immature ecosystem, but it might also signal a diminished need for them.

Posted by saosebastiao on Jul 8, 2015, 4:59 PM

Tags

Related issues

Raise real-world problems, find people facing the same issue, and discuss solutions.5,500 issues0 comments

reliability (Other)

I tend to think that the sophistication of the tools reflect the extent that the language is broken.

saosebastiaoJul 8, 2015, 4:59 PM

I tend to think that the sophistication of the tools reflect the extent that the language is broken. Valgrind doesn't need to exist for the Java user. You don't need class boilerplate getter/setter generators for Scala. Nobody needs NPE static analyzers for Rust. The need for rename refactoring tools is drastically diminished by the existence of type inference, almost to the point where `:%s/Foo/Bar/g` is entirely adequate. The non-existence of tools that you find in other languages might signal an immature ecosystem, but it might also signal a diminished need for them.

Comments (0)

No comments yet. Start the discussion.

Comment on this issue