2 ms·
> But you need really good tooling to use it, like a powerful IDE with good autocompletion and refactor support. It is way too verbose to type everything out yo
by dehrmann 4y ago
> But you need really good tooling to use it, like a powerful IDE with good autocompletion and refactor support. It is way too verbose to type everything out yourself, and the verbosity means manually refactoring takes lots of changes around the program to manifest.
One of the ironies of Java has been that its strictness and verbosity can make it hard to develop, but that strictness also enabled the development of powerful IDEs. What feels like a hassle for a 100 line file becomes an asset for a million-line project because of the safety, discoverability, and refactoring it enables.
- pdntspa 4y agoIndeed; I haven't seen a ton of bad code in it (not saying that it's not out there, just that I haven't been exposed to much of it), but when I needed to dig into how something works, so far it has been very easy to scan and mentally parse what's going on.
- gorjusborg 4y ago> What feels like a hassle for a 100 line file becomes an asset for a million-line project This is true and hard to communicate to people that haven't lived it.
- kuboble 4y agoYes. I worked many years in both Java and C#. In Java every project and codebase I saw was pretty much the same. In c# when I look at other people's projects I often feel like it's a foreign language. You can make it look like C++ with unsafe blocks. You can nake it look like ruby with dynamic variables. You can write sql-like statements. As much as I love writing in C#, I prefer reading other people's Java.