Just finished merging and testing all patches for choo v3; docs and contributor testing is pretty much all that's left now
- very excite
-
-
Replying to @yoshuawuyts
Laying the last hand on the choo v3 documentation; the view isn't too bad heypic.twitter.com/bnCCisB68J
2 replies 1 retweet 11 likes -
Replying to @yoshuawuyts
I've never felt so confident merging a 1k+ line patch -https://github.com/yoshuawuyts/choo/pull/127 …
1 reply 0 retweets 9 likes -
Replying to @yoshuawuyts
Choo v3 is out
- now 5kb and heaps of shiny features 


- Release notes: https://github.com/yoshuawuyts/choo/blob/master/CHANGELOG.md#300 … | HN Discussion: https://news.ycombinator.com/item?id=12040387 …1 reply 38 retweets 74 likes -
Replying to @yoshuawuyts
Oops, choo is now the king of useless benchmarks - and we've barely started optimizing even haha - ah wellpic.twitter.com/TiTo4B56K7
5 replies 5 retweets 16 likes -
Replying to @yoshuawuyts
Stretch goals for choo: 1) be fast enough for game dev / minimize GC pauses, 2) provide tooling to visualize *any* part of an app real time
4 replies 0 retweets 12 likes -
Replying to @yoshuawuyts
I really, _really_ hope this takes off in a really big way. Too many frameworks out there throw payload size to the wind. Thx!
1 reply 0 retweets 1 like -
Replying to @doot0
gehe - same (though I'll need to do work for money again soon hah) - want to get choo to be even smaller actually
- 3kb is the goal1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
Super ambitious! Why don't you go whole-hog and fit the entire payload in a single TCP window?
2 replies 0 retweets 0 likes -
Replying to @doot0 @yoshuawuyts
Oh wait! It already does! Again, amazing work.
1 reply 0 retweets 1 like
hahaha, lol - so everything < 65kb should be sweet; learned something today hah https://en.wikipedia.org/wiki/TCP_window_scale_option …
-
-
Replying to @yoshuawuyts
The next step to optimisation is looking into low-level stuff I think. 3kb is very ambitious but more than likely possible.
1 reply 0 retweets 0 likes -
Replying to @doot0
at this point the diffing algorithm is 40% of the payload; router 30% ish - think the algorithm is probs the most optimizable rn
1 reply 0 retweets 0 likes - 4 more replies
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.