uberclass and uberproto
mavrick opened this issue · 5 comments
Hey,
I'm currently using uberclass and want to make the switch to uberproto. What recommendations do you have for me and others in my position? Is this something I can just replace uberclass with seamlessly?
Cheers
Sorry for the late reply. It turns out that the switch is in fact not trivial and it probably wasn't a good idea to deprecate the old library. Even though I personally prefer using Uberproto because it is a lot more lightweight and flexible I will make a new non-deprecated Uberclass release.
Any news on that? I just wanted to start a new project and switched to uberproto, now realizing that it doesn't seem to support static properties anymore. May I kindly ask you to clarify what the main differences are and why you even chose to deprecate uberclass in the first place? I'm sure that there are some advantages over uberclass that just aren't so easy to grasp at first and I would love to get a comparison before deciding whether to switch over to uberproto. Thanks and kind Regards
You don't need static properties if you do inheritance ES5-style. I deprecated Uberclass because I am not going to maintain it anymore since I am using Uberproto (if any) inheritance library.
If you are interested in picking it up, I'm more than happy to give you access to the repository. The advantages of Uberproto imho however are
- Smaller size (0.6Kb minified + gzipped)
- ECMAScript 5 compatible
- Real object based inheritance instead of trying to emulate old class structures
- Also works on plain objects (which is great for mixins and super methods)
- Smaller API footprint (4 methods)
Great, thanks for your explanation. You got some legit points here, I'm definitely going to make the switch. Thanks for sharing!
Cool. And deprecated just means that I'm going to actively maintain it anymore. If it still works, go for it.