> You can make classes, but you can only ever make one instance of them. This shouldn't affect how most object-oriented programmers work.
This describes my experience with most OOP code very well.
> You can make classes, but you can only ever make one instance of them. This shouldn't affect how most object-oriented programmers work.
This describes my experience with most OOP code very well.
As for OOP, a bit more realistic would have been to restrict interfaces to at most one implementation.
https://gwern.net/doc/cs/2005-09-30-smith-whyihateframeworks...
Note that one of the comments is from me :-)
It's no surprise that when you make virtually all mainstream programming languages OOP, then there will be a vast amount of bad OOP code out there (as by definition mainstream code then becomes "OOP code").
DreamBerd probably allows this.
If not, maybe you can hoist the ability to hoist % symbols, before which you can hoist % symbols.
I'm more inclined to follow the bell curve. 10% crap, 40% mediocre but rather bad, 40% mediocre but rather good and 10% great.
That sounds interesting. Who has researched/written about that?