40 ms·
>The 2nd dream for software was object orientation. It’s hard to describe how strong and confident this idea was. by using classes, codebases become collaborati
by whatshisface 6y ago
>The 2nd dream for software was object orientation.
It’s hard to describe how strong and confident this idea was. by using classes, codebases become collaborative and useful to one another - The perverse, dark-magic idioms of unix disappear in OOP best-practice. The decline of java may be the saddest story in computer science.
It was just before my time.
Java is far from the only object-oriented language. Does the author suggest that C# and Python are of only historical significance? It's unsubstantiated to associate the decline (?) of Java with the decline (?) of object oriented programming, and even moreso to associate either of them with the implied decline (?) of composability, which can be achieved in many ways other than object orientation. For example, Go and Rust do not implement OOP in the same way as Java, but many people think their modifications improve composability, far from contributing to its decline. What we have in the quote are three dubious facts (it's not clear how much of a decline any of those have undergone), associated through nonexistent connections (they are not related).
- StillBored 6y agoConsidering mainstream languages, I find java unique in forcing OOP into places it doesn't really belong. You can see this in your first "hello world" application where the entry point ends up getting wrapped in a class definition. Something that makes zero sense, and does little but obfuscate. I tend to like a bit of OOP here and there, but the little java programming i've done, it always feels like I was forced into pounding the square peg into a round hole. https://www.programiz.com/java-programming/hello-world https://www.programiz.com/java-programming/hello-world Compared with say, C++ where you can write entire programs that never declare a single class. Its the same thing with purely functional languages, in any significantly large program you reach the point where your solving problems using the wrong paradigm because the language is too dogmatic.
- Nursie 6y agoHaving an entry point in a class lets you have per-class entry points, so you can choose what to run, if that appeals to you. Java likes its objects, but in modern java there's enough in the way of lambdas etc that most of the weird "this must be a class" stuff is removed, or at least hidden. And the java community are far less dogmatic about it these days.
- WalterSear 6y agoHowever, the author is specifically longing for the old Java, and the halcyon days of trying to object orient everything. It's not a blog piece: it's a cry for help.
- nradov 6y agoThere are multi-paradigm languages like Scala which address that concern, at the cost of higher complexity.