4 ms·
Of course this is on point, you shouldn't write Rust like it's Java, however looking at Java, you shouldn't write anything like it's Java. Java has brought fort
by carlmr 2y ago
Of course this is on point, you shouldn't write Rust like it's Java, however looking at Java, you shouldn't write anything like it's Java. Java has brought forth the biggest madness of tacking on OOP to everything that is still making 3 billion software projects unreadable.
- ilrwbwrkhv 2y agoTotally. The amount of indirection and badly written code with hundreds and thousands of classes which take a simple data and combine it with magic methods which you have to open the class to understand is crazy.
- Log_out_ 2y agoA whole beach of sand,every grain a unique object,influenced by water,milled from a clifffactory.No other way to model a holiday..
- neonsunset 2y agoThis made my morning, thanks.
- hyperman1 2y agoEven in Java, the interfaces everywhere style was never great. Somehow Java got picked up by Architecture Astronauts that love writing enterprise pattern layer cake. Nothing in the language makes this style necessary, it's perfectly possible to write short and sweet code, and yet the Java culture got infected with this overcomplicate everything culture.
- orwin 2y agoI kinda prefer the interface everywhere to the inheritance everywhere crowd. But I've mostly used/debugged groovy code so maybe I'm partial.
- deleted 2y ago[deleted]
- deleted 2y ago[deleted]
- AnimalMuppet 2y agoJava got picked up by the enterprise software crowd. (Maybe blame Sun for that - the enterprise people were going to buy a lot of servers.) The enterprise software culture is where you had "software analysts", which was a different job description from "programmer". That culture took over Java and made it what we now think of as "Java culture", but it wasn't really Java. It was really the enterprise software culture. That's my opinion, anyway.
- ksp-atlas 2y agoEven other JVM languages aren't safe from this, since you still need to interface with Java
- kaba0 2y ago> Java has brought forth the biggest madness of tacking on OOP to everything It was C++, if we are being historically accurate. It’s actually a positive in Java’s case that it managed to make these systems even run.
- pjmlp 2y agoI love how everyone likes to blame Java for OOP, when most of the stuff that eventually ended up in enterprise OOP patterns, predate Java for 10 years. Including those stupid "coding Java in C++" remarks, when Java OOP model is based on a mix of C++ frameworks, and Objective-C features.
- immibis 2y agoAnd Objective-C is just Smalltalk with C syntax.
- fulafel 2y agoYep, "With enough thrust, pigs fly just fine" - Java's addition of GC was that brute force solution to the tangle of mutually mutating randomly interconnected objects that in C++ tended to collapse under its own weight without making it to production.
- pjmlp 2y agoNah, the architecture space astronauts just changed from Smalltalk, C++ into Java.