3 ms·
IMHO the idea that the history and future of programming languages follows a pre-determined ladder, or 'generations' is misguided. More abstactions isn't necess
by flohofwoe 5y ago
IMHO the idea that the history and future of programming languages follows a pre-determined ladder, or 'generations' is misguided. More abstactions isn't necessarily better then more explicitness. Functional style isn't necessarily better than OOP, and OOP isn't necessarily better than 'imperative style'. All the different languages will not converge into a "perfect" language some time in the future, if anything, it looks like the opposite is true.
I sometimes wonder if Marxism has a bigger influence in some "language designer circles" than (for instance) Darwinism ;)
- q-big 5y ago> I sometimes wonder if Marxism has a bigger influence in some "language designer circles" than (for instance) Darwinism ;) Or some (programming) language designers are creationists deep inside their hearts (without willing to admit it). ;-)
- xiphias2 5y agoRust needed 25 years to bring us a significally improved abstraction over C++ without sacrificing resource usage. It just shows that it's much easier to say that we need a higher level language than to know what would work in practice well enough to be useful as a systems level programming language. At the same time Linux was released 20 years after C, so of course Rust has to mature more to really take over C++.
- DubiousPusher 5y agoIs Rust an abstraction over ideas in C++ or is it in fact just a better set of abstractions over the same underlying operations? I would say the latter, mostly due to jettisoning OO nonsense.
- xiphias2 5y agoSure, I agree with you, I meant that Rust's type system is a better abstraction over manual memory management than C++'s type system, I didn't mean that Rust is an abstraction over C++, I'm just not that great in expressing myself clearly in this case.
- eru 5y agoIt's not just OO. It's also making things safe by default, and getting rid of a lot of accumulated jank.
- eru 5y agoNah. We had stuff that was better than C++ for a long time. (C++ has improved over time, but so have the alternatives.) A large part of C++'s staying power is due to status quo bias. So in that sense you are right, if you take 'significantly improved' to mean improved enough to overcome status quo bias.
- DubiousPusher 5y agoI think most people have given up on the concept of "more abstract"=better. However, there are other was to "advance" the state of programming. One is to find better metaphors to express the same concept. For example, C is a wonderful language. But if you spend much time at all in an advance C codebase, you will find lots of code that is attempting to do things that it's hard to tell it's attempting to do. Because C has this really half-baked type system and it's only generalization of data is the void pointer and so on. There are two solutions to this. Take every feature of C and explode it to its logical conclusion and beyond. And there you get C++, which has it's uses but is really one of the few languages I would ever call straight up bad. (I know, it's beloved to many and I came up on it but it is bad, I'm sorry.) But if instead, you back up and look at what is good about C and start modernizg its metaphors and instead of leaving them incomplete like in C you fill them out, you get something like zig. Which really is a beautiful language. No more abstract than C but much easier to understand.
- eru 5y ago> Take every feature of C and explode it to its logical conclusion and beyond. And there you get C++, which has its uses but is really one of the few languages I would ever call straight up bad. I think you could take the approach you described, and get something better than C++. Especially with the benefit of hindsight.
- dragonwriter 5y ago> IMHO the idea that the history and future of programming languages follows a pre-determined ladder, or 'generations' is misguided. Generations of programming languages aren't a predetermined ladder or order of quality or teleological progression, it is a description of a broad, backward-looking groupings of the order particular combinations of features appeared. > OOP isn't necessarily better than 'imperative style'. OOP is imperative (you might mean procedural, like C/Pascal or unstructured, like BASIC.)
- goatlover 5y agoIs Smalltalk's OOP imperative? What about CLOS?
- dragonwriter 5y agoYes, both Smalltalk and CLOS are imperative.
- eru 5y agoYou can do something like OOP in Haskell or Scheme, without being imperative. But yes, most OOP incarnations are imperative.
- eru 5y ago> IMHO the idea that the history and future of programming languages follows a pre-determined ladder, or 'generations' is misguided. > I sometimes wonder if Marxism has a bigger influence in some "language designer circles" than (for instance) Darwinism ;) That would be Hegelianism. (Marxism is sort-of a specific application of Hegel. Not that either makes more sense.)