I really, _really_ hope this takes off in a really big way. Too many frameworks out there throw payload size to the wind. Thx!
-
-
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 -
Replying to @doot0
hahaha, lol - so everything < 65kb should be sweet; learned something today hah https://en.wikipedia.org/wiki/TCP_window_scale_option …
1 reply 0 retweets 1 like -
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 -
Replying to @yoshuawuyts @doot0
started some work here to strip lifecycle events from morphdom - https://github.com/yoshuawuyts/nanodiff …, but I messed up something / no tests rn
2 replies 0 retweets 0 likes -
Replying to @yoshuawuyts @doot0
did manage to shave 0.5kb - 1kb off it; also probs a teeny bit faster - would simplify the yo-yo code a lot tho
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
This kind of optimisation is beyond my skillset.
1 reply 0 retweets 0 likes
Replying to @doot0
haha - why would it be? I've got no clue what I'm doing either hey 
- not to say you *should* tackle it, buttt think you probs could
6:43 AM - 7 Jul 2016
0 replies
0 retweets
0 likes
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.