The problem I have with all these frameworks is that they weigh a lot, but then don't help you do common stuff - SSE, forms, transforms?
-
-
-
Replying to @edefic @FrozenFire
Server Sent Events - they're probably what you want instead of WS :D https://github.com/yoshuawuyts/choo/blob/4ca7fe75a64a8c080e092f1010437de7523889b7/README.md#server-sent-events-sse …
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts @FrozenFire
though you're right - the better example would've been HTTP; most frameworks are like: "lol figure it out yourself" - why? :(
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
the only use I see for SSE is read-only realtime webapps tbh — most webapps should behave like state syncers
1 reply 0 retweets 1 like -
Replying to @edefic @FrozenFire
you mean like poll for state changes every n seconds? Notifications / status of things is pretty common I reckon
1 reply 0 retweets 0 likes -
Replying to @yoshuawuyts
no, receive a stream that acts upon a state machine, and transmit one, and model the app in terms of a real state model
1 reply 0 retweets 0 likes -
Replying to @edefic @yoshuawuyts
instead of just ad-hoc hoping requests go through and assuming things, build state replicators, viewers, editors
1 reply 0 retweets 0 likes -
Replying to @edefic @yoshuawuyts
your view layer becomes a viewer/editor for the local state machine
1 reply 0 retweets 1 like -
Replying to @edefic @yoshuawuyts
but realistically I am too sleep-deprived to give an explanation that does it justice
1 reply 0 retweets 1 like
haha, I think I see what you mean - I'm agreeing here!
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.