4 ms·

250kLOC Python sounds scary. But that would easily be 1mLOC+ lines in Java ...

magicalhippo 6y ago
I'd much rather have a million lines of Java. And I'm not a huge fan of Java. It can be a bit tedious going down the AbstractWidgetInterfaceFactoryFactory rabbit holes, but at least I have a fighting chance.
- joelbluminator 6y ago
  To each his own...
  - rajacombinator 6y ago
    Honestly they both sound horrific. Any code base that large ...
    - joelbluminator 6y ago
      Yep, indeed. Most of my head scratch moments with big code bases aren't about anything as technical as types. It's not as if knowing the types would have made me realize what the code actually does, which is the main hurdle.
      - magicalhippo 6y ago
        In my experience, static types allows me to ignore a lot of code, which helps dealing with large codebases. Sure it won't do magic with 1MLOC of spaghetti code, but in a reasonably sane codebase it makes it much easier to know which parts to care about and which you can ignore for the time being. Again, that's my experience at least.
gher-shyu3i 6y ago
Not necessarily. It's possible to write quite terse code in Java, especially Java 10+ (var, streams, etc.). And now with records and pattern matching, even more so.
paddim8 6y ago
I don't understand why people say this about Java and C# vs. Python. You can easily write concise code. There will be more lines because of things like brackets and some other simple things, but c'mon, it's not 2005.
emergie 6y ago
lombok is the holy grail of java boilerplate removal. With proper usage of spring-data, spring-cloud-stream, spring-* lomboked java code can be very terse. If you follow conventions repositories, rest clients, mappers etc. are often defined only by interfaces and annotations - actual implementations are generated. The downside is that the entrance to the full blown spring-* world has a step learning curve - there is a lot to read at spring.io.

I'd much rather have a million lines of Java. And I'm not a huge fan of Java. It can be a bit tedious going down the AbstractWidgetInterfaceFactoryFactory rabbit holes, but at least I have a fighting chance.

joelbluminator 6y ago
To each his own...
- rajacombinator 6y ago
  Honestly they both sound horrific. Any code base that large ...
  - joelbluminator 6y ago
    Yep, indeed. Most of my head scratch moments with big code bases aren't about anything as technical as types. It's not as if knowing the types would have made me realize what the code actually does, which is the main hurdle.
    - magicalhippo 6y ago
      In my experience, static types allows me to ignore a lot of code, which helps dealing with large codebases. Sure it won't do magic with 1MLOC of spaghetti code, but in a reasonably sane codebase it makes it much easier to know which parts to care about and which you can ignore for the time being. Again, that's my experience at least.

gher-shyu3i 6y ago

Not necessarily. It's possible to write quite terse code in Java, especially Java 10+ (var, streams, etc.). And now with records and pattern matching, even more so.

paddim8 6y ago

I don't understand why people say this about Java and C# vs. Python. You can easily write concise code. There will be more lines because of things like brackets and some other simple things, but c'mon, it's not 2005.

emergie 6y ago

lombok is the holy grail of java boilerplate removal. With proper usage of spring-data, spring-cloud-stream, spring-* lomboked java code can be very terse. If you follow conventions repositories, rest clients, mappers etc. are often defined only by interfaces and annotations - actual implementations are generated. The downside is that the entrance to the full blown spring-* world has a step learning curve - there is a lot to read at spring.io.