4 ms·
My doubts were meant as specifically against your points. CLOS is often lauded as one of the best object systems. To see it as one of the complaints feels odd
by taeric 7y ago
My doubts were meant as specifically against your points.
CLOS is often lauded as one of the best object systems. To see it as one of the complaints feels odd.
Cruft in the standard library? Examples would be good here. But, this is hard to get behind. Nobody would be really sad to see Java date leave. That said, many of us are happy we don't have to touch some code that is working fine with it.
And this is next to a demand for a bigger standard library. Which will only lead to more cruft.
Not sure what you mean about the compatibility layer. Care to expand?
My point was if CL had the press of any of the alternatives to gave, that would put weigh the negatives you gave. Instead of chasing removal of stuff, marketing would make more of a difference.
- rauhl 7y ago> CLOS is often lauded as one of the best object systems. To see it as one of the complaints feels odd. CLOS is awesome, better than the rest. But there are some weird seems between types and classes. And in places CLOS doesn’t go far enough — e.g. it’d be nice to specialise methods based on element types.
- taeric 7y agoBut this criticism wants a new system. Not just fixing some areas. That sounds off. I'd be interested in seeing some of the extensions you have in mind. I've only dabbled in clos. And I have to confess structures fit my case way better.