4 ms·
Java is trying to force a code architecture on the devs. It's useful in enterprise situations where devs cycle in and out but the code base has to stay. You nev
by teawrecks 6y ago
Java is trying to force a code architecture on the devs. It's useful in enterprise situations where devs cycle in and out but the code base has to stay. You never have to guess where or how something is defined. C/C++ on the other hand gives you 1000 ways to shoot the person who replaces you in the foot.
- p2detar 6y agoExactly. This is what people bashing Java just don’t seem to understand. Training a new Java employee on an existing code base is far cheaper than on a C/C++ codebase. Speaking from personal experience.
- giancarlostoro 6y agoI've found it just as simple to teach someone a Python codebase, and I do have OOP in most of my python projects, but sometimes I don't and that's okay, because not everything needs to be an instance of a class. D is not as prevalent but I'm certain showing someone around a D code base wouldn't be too complicated.
- giancarlostoro 6y ago> You never have to guess where or how something is defined. I mean sure, this is mostly true of Go more than most other languages though. I didn't mean to pick on Java alone, C# which is a language I love has this similar problem, though they seem to be heading slowly towards a multi-paradigm language, though the emphasis on OOP is still there, it doesn't feel as restrictive as Java. Heck, even Kotlin seems to be getting rid of a lot of what I call the ceremony of Java whilst still producing equivalent bytecode (I can only imagine most of it is just syntatic sugar).