I think one of the mistakes I made with choo is "state is immutable" - views derived from state are already immutable; state should mutate
-
-
Replying to @yoshuawuyts
Another mistake I made with choo: too many computer words that have no inherent meaning and you need to learn what they mean. We can improve
2 replies 0 retweets 13 likes -
Replying to @yoshuawuyts
Choo not feeling quite right in terms of API is why I haven't gone and done more tutorials & guides - wanna get it (mostly) quirk-free first
2 replies 0 retweets 4 likes -
Replying to @yoshuawuyts
I just released nanobus - a tiny message bus (~0.4kb)https://github.com/yoshuawuyts/nanobus …
1 reply 0 retweets 7 likes -
Replying to @yoshuawuyts
Ok, alright, think I've got an idea of what the API of http://choo.next will look like - check it https://github.com/yoshuawuyts/playground-nanoframework …pic.twitter.com/bOPcvdbkH2
5 replies 2 retweets 18 likes -
Replying to @yoshuawuyts
Not so sure about replacing function calls with events. I’ve done this before and it makes debugging hard.
1 reply 0 retweets 1 like -
Replying to @mantoni
haha, very fair - I think it's fine tho, as long as people show restraint it'll be easy to reason about. Also .on('*') helps :D
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @mantoni
what did you find hard about it by the way?
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
You emit an event with a type = nothing happens vs „undefined is not a function“
1 reply 0 retweets 1 like
yeah that's very fair - feel like we could write a few debugger modules for this tho - don't think it should be too hard :D
-
New conversation
-
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.