Strange to see this show up on the front page now when I wrote this back in 2022. For context, this is a light critique of Guile's CLOS-like OOP system which overall I think is a pretty great approximation of CLOS. I just wanted to write down the things I felt were lacking so I didn't forget them, didn't have to repeat myself whenever one of these issues came up on irc or the mailing list, and could maybe motivate someone to fix them eventually.
lispm 18 hours ago [-]
Could you motivate someone to do those fixes?
davexunit 17 hours ago [-]
Maybe, but I haven't pushed very hard for it as I don't use OOP very often. I did buy Art of the Metaobject Protocol in case I wanted to try to make some of the improvements myself, but haven't gotten around to it.
ephaeton 21 hours ago [-]
Wow, I never knew these deficiencies from gooops. This seems to me like a 'scheme with classes' mindset implementation of CLOS. Given the success of C++ and the like, surely there'll be enough people to productively use this. I'd rather have more "proper" CLOS systems in the world though.
The FP-world worked successfully in dusting mainstream to have rust be a thing, now if we could replace C++ (and simula and whatnot) class-based "object" systems with object-based object system with more advanced capabilities such as sketched in CLOS, that'd be nice IMO.
faruk74summy 18 hours ago [-]
[dead]
faruk74summy 18 hours ago [-]
[dead]
lincpa 18 hours ago [-]
[dead]
Rendered at 06:02:21 GMT+0000 (Coordinated Universal Time) with Vercel.
The FP-world worked successfully in dusting mainstream to have rust be a thing, now if we could replace C++ (and simula and whatnot) class-based "object" systems with object-based object system with more advanced capabilities such as sketched in CLOS, that'd be nice IMO.