2 ms·
The language is of course part of the problem. Because having to write de facto one file per class does not really allow you to write very elegant software. It
by valenterry 6y ago
The language is of course part of the problem.
Because having to write de facto one file per class does not really allow you to write very elegant software. It forces you to write files over files and no one wants that, so they fall back to primitive types.
For the abstraction bloat it is actually similar. Here the reason is that for the longest time (and even nowadays) Java makes it painful to work with functions. So now instead of just a plain function, you have to create a class with an interface that has one method... and instantiate it. Great... not.