3 ms·
This paragraph caught my eye - > I think Object-Oriented Programming was an important advance over procedural programming, which is what we had been doing, but
by thunderbong 4y ago
This paragraph caught my eye -
> I think Object-Oriented Programming was an important advance over procedural programming, which is what we had been doing, but we’re stuck. We’re supposed to change paradigms every generation, and we haven’t. So we’re way behind now. Object-Oriented Programming hit the mainstream in 1980. We’re in the 2020s and we’re still there. We should have moved on.
- kagakuninja 4y agoFunctional programming is the next big thing. Ideas from functional programming have gone mainstream, and are found in almost all major languages: lambdas, higher order functions, and immutability / purity. Monads have made some minor inroads (although they get bastardized by OO people, see Java and Javascript).
- silverwind 4y agoYes, but the remnants of OO still linger, both in people's minds and code.
- klysm 4y agoMost importantly in people’s minds. A lot of early educational content is rooted in flawed software philosophy that is carried out into the world
- usrusr 4y agoThere are still remnants of ideological OOP use around and they are terrible indeed, but remnants on the language level are perfectly fine as long as they are not used as originally intended. Paraphrasing Crockford, we have found OOP, the good parts. It's used for structuring code now, not for modelling the world. That's a huge difference.
- DonHopkins 4y agoWell if people wouldn't keep brutally deconstructing it [1] then serving it up as a delicious la carte menu [2] of tempting indulgences, maybe object programming will finally die! [1] https://www.info.ucl.ac.be/~pvr/decon.html https://www.info.ucl.ac.be/~pvr/decon.html [2] http://www.paulgraham.com/reesoo.html http://www.paulgraham.com/reesoo.html
- nmz 4y agoWell, we're heading for a future where no one programs and everyone just prompts chatgpt. So it seems the future of programming languages is no more programming languages.
- nforgerit 4y agoSo, "in the future" how do people create programs expressing their intent? They'd write or speak in some natural language, right? 1. In order to avoid ambiguities they'd need to use concrete vocabulary. 2. Any non-trivial program will need to consist of multiple input statements. Those input statements will have some kind of relationship to each other. This is roughly what a grammar is about. 3. Those future programmers will somehow need to check if the program does what it's supposed to do. They'd run it with test data. Combine 1-3 and see that we just described, what a programming language and its ecosystem (compiler, runtime, etc.) do. Thus, programming languages are nowhere near to die out, they will just shift things higher up the layer lasagne.
- nmz 4y agoWe already have that, considering gpt requires a lot of code to train itself, the transition to a new language might not be worth it, so we might be stuck with the ones we have now.
- Shorel 4y agoThat argument sounds like change for the sake of change. Programmed obsolescence for programming languages. We should move on when we find something that is objectively better, not because some years have passed. And honestly, the only new thing that seems to be better than the current paradigm is Rust borrow model, which is not against object orientation, it compliments it.
- btschaegg 4y agoWhile this is true, I'd like to point out that the switch to the currently prevailing flavor of OOP also didn't really fit that description all that much. Note that by now, other advancements like assembly vs. raw machine code would be pretty much a no-brainer. The 90s-flavor OOP we're stuck with in many places is objectively bad for performance (see e.g. Mike Acton's takes on what he calls "Data-Oriented Design") as well as readability/understandability (where I'd say languages with a culture around more FP concepts and immutability have a way better track record) and concurrency (see Erlang/Elixir). And, as always, you can simulate the useful properties of other paradigms, but that only goes so far. I think what the original quote laments is that the median software developer is leaning way more on "we've always done it this way" as a way of guidance instead of better ideas replacing the old ones. Edit: Also: I totally agree with you about Rust, but I can't help but notice that Rust mainly stops you from doing dumb things (no inheritance, borrow checker…), which effectively dials back many of the… more unfortunate concepts/idioms of 90s OOP.