People who constantly complain about clientside-rendered sites should be forced to use Twitter through the Macaw Swift or m2 stackshttps://twitter.com/slightlylate/status/1234017844477624321 …
Is this an argument that public services should only be available through app stores and/or on fast, expensive devices? If not, I might require some education about what m2 is.
-
-
In this case it’s an argument that Twitter is/was worse to use when it was heavily server rendered with JS to stitch it together, due to accumulated years of cruft and tons of code that was hard to delete. JS-rendered sites have perf issues but any stack is slow if no one cares
-
There are certainly great arguments for why server rendered is better for a lot of cases, but it’s continuously vexing to see all of the clientside experiences lumped together when the really good ones are so much better than server rendered ones.
- 6 more replies
New conversation -
-
-
This Tweet is unavailable.
-
Is there a query param I can use?
- 1 more reply
-
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.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.