You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I read your blog post and browsed this repo and it is amazing stuff you have here!
I got really inspired by your work so I ran with it and created this library, loosely based on mixwith:
It looks a lot like yours with some (big) differences:
I merged mix and mixin into one
with is optional syntax sugar
mix can return a mixin instead of a class
mixins can be used to instantiate an object directly
mix can combine multiple mixins into a new one
I found that creating an actual class is often not desirable because it limits the potential uses for the code. Instead, mics promotes the use of mixins everywhere:
import{mix,is}from'mics'varLooker=mix(superclass=>classLookerextendssuperclass{look(){console.info('Looking good!')}})// directly instantiate a looker:varlooker=newLooker()looker.look()
Thanks again for inspiring me and I'd love to get some feedback from the master!
The text was updated successfully, but these errors were encountered:
I read your blog post and browsed this repo and it is amazing stuff you have here!
I got really inspired by your work so I ran with it and created this library, loosely based on mixwith:
mics
It looks a lot like yours with some (big) differences:
mix
andmixin
into onewith
is optional syntax sugarmix
can return a mixin instead of a classmix
can combine multiple mixins into a new oneI found that creating an actual class is often not desirable because it limits the potential uses for the code. Instead, mics promotes the use of mixins everywhere:
Thanks again for inspiring me and I'd love to get some feedback from the master!
The text was updated successfully, but these errors were encountered: