This is truly disturbing. Your work as a frontend engineer must center the user, not your preferences and comfort zone.https://twitter.com/MrChrisseuh/status/1236723266380869634 …
-
Show this thread
-
Legitimate justifications for tool choice flow from user benefit: using X allows us to deliver faster sites, or iterate on feedback from users, or work better with designers (etc. etc.) The common theme among these legit arguments? They can be falsified.
2 replies 0 retweets 8 likesShow this thread -
Replying to @slightlylate
Sometimes it's fully situational ethics, though. If your developer experience and tooling allow you to move 2x faster by punting on, say, ALL MOBILE USERS, this can in fact be the correct choice for your business that desperately needs more features.
1 reply 0 retweets 1 like -
Replying to @gavindoughtie
Absolutely! And good managers can make that choice explicit for/to the business. I observe most folks post-hoc rationalising lower reach, tho.
1 reply 0 retweets 0 likes -
Replying to @slightlylate
It takes a lot of effort to have less code, though, and the rules about what's efficient change over time. For example, underpowered Android devices AND 5G totally flip the original desktop wins for SPAs. It's cruel that 300K of JS is more expensive than 3MB of HTML.
1 reply 0 retweets 0 likes -
Replying to @gavindoughtie
I keep chuckling at "underpowered" re: Androids. They have 4+ cores! And a full GB+ of RAM! And GPUs!!! The reason 3MB of HTML is survivable on them is because the system is well optimised to yeild, do work in chunks, progressively render, and stay interactive...
2 replies 0 retweets 3 likes
...and when you move anything to JS, you fully take the reins. It is now up to you to handle all of those concerns. And most frontend teams, I'm sorry to say, either don't understand that or aren't good enough to handle multiplied responsibilities.
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.