171 karma · joined May 23, 2011
gives you a fun ball of yarn to untangle
Seriously try to Deflate a 50mb compressed json structure vs just piping it down the wire on a high bandwith connection and try to measure that. (In real life with a server and browser - browsers are super slow at this)
I never tried CBOR when looking for a sub 10ms solution for websocket comms, however my use case was not bound by datasize but entirely by speed (network not inet).
However it all came down to a suprising realisation: "compression on both ends is the primary performance culprit"
Optimizing the hell out of the protocol over websockets got me to a fairly ok response time, just using string json and 0 compression blew it out of the water.
So the result was that data load was faster and easier the debug going with strings of json vs any other optimization (messagesize where in the 10-50mb realm)
The amount of shotty ws sever implementations and gzip operations in the communications pipeline is mindblowing - would be interested in hearing how just pure json and zero compression/binary transforms performed :)
I find it more magic to change a single class at root and have the entire design reflow (on purpose) -
Its beautifull when combined with shadowdom and wc
--corporate-main-primary, secondary etc
Then map that to red-50 if you really want to.
but a design lives in cmyk/ral/rgb/hex not red-650
The go
--action-button-cta-hover etc that could map to corp primary or some other stuff
Highly reactive (goes booooom with water or oxygen)
Expands incredibly when heated
For those efficiencies i would recon you'd need temperature in excess of 1500k right?
That does not sound like anything that is easily "safe" or "reliable"
Object content as lazy
Embed lazy
Image lazy
Link rel=import (not support that widely though)
Heck if you wanted to get REALLY cute you go use multipart-mixed-replace headers.
Or SSE
No SoMe at all for kids under 13.
No messaging after 20:00.
1.5 h screentime (ios) maximum a day.
O.5 h enforced reading (actual books) from 17:30-18:00 (we make it a family thing - all reading together).
No screens at all at playdates until 4th grade.
No movies or media below age-level ratings without consent from parents.
No phones in bed or while sleeping.
Heavy utilization of screentime, unifi network blocks etc.
Works well for us
I've tried messagepack a few times, but to be honest the hassle of the debugging was never really worth it
Plantmilks are firstorder product.
This means that clinate impact of most plantmilks are higher than milks, excepting oat and ryemilk.
On a cost note - : making oat milk is literally just blending some oats and let them soak a day or 2, filter the water and done, perhaps do that if cost is an issue?
On a sidenote, if you drink soy, almond or worse ricemilk you're actually doing something worse for the climate/environment
Only that knows url for endpoints, protocols and connections - and proxies between them and your app / components