4 ms·
Isn't that forecasting a trend with too few data points? The field is still young and changing.
by alserio 5y ago
Isn't that forecasting a trend with too few data points? The field is still young and changing.
- nlitened 5y agoOh, I don’t think it is a trend. I rather see it as a curious phenomenon that makes one reflect on the trade offs we usually make when using polymorphism, and whether it’s worth all the time, not only in terms of performance, but also in terms of program architecture.
- alserio 5y agoInteresting. What are the program architecture tradeoffs you are suggesting?
- nlitened 5y agoTo be honest, I have zero experience programming with Zig. But I imagine programming with Zig would lead to more literal style and fewer, simpler abstractions (no IoC, no frameworks). That might be beneficial for certain kinds of focused-scope projects.
- alserio 5y agoI see. They say you can solve every problem with an other indirection, and ad hoc polymorphism is an instance of that. But there are other ways to enable composition that are seldom reached for when your language makes that easy
- ncmncm 5y agoEvery problem, except those caused by too many indirections. Each solution uses only a few language features. Different problems call for different subsets. Not using a feature on your favorite sort of problem says nothing about its value. "Ways to enable composition" poorly supported are reached for less. Poorly supporting one of them that has proven frequently useful does not improve a language.
- ncmncm 5y ago> too few data points? There have been rather a lot of languages. The field is approaching 70 years old, and still changing, but clear evolutionary processes are seen repeated in hundreds of languages living and dead. The ones that don't grow are the most reliably dead.