Even the truth in the original demonstrates ignorance: front-end (and client-side generally) has layers to occupy you for multiple careers!

Codecs, databases & storage, graphics (2d & 3d), languages & runtimes, fonts & layout, networking, performance: all harder on the client.
It *is true* that working across layers is a key trait of highly effective engineers. Respecting those who do it on the client is good.

The idea that one must "graduate" to the back end carries the same stench as every overconfidently presented "full stack" failure I trace.
Front-end demands humility because it is *different* and, in key respects, *harder*.

There's an asymmetric hubris here: those of us who work the client don't tell back-enders that their work is trivial. Nor do we gate-keep the "full stack" crowd, no matter how poorly they do.
If only we could just not render webpages for the huge amount of the industry that can't be bothered to respect how hard it is to put pixels on screen at 60fps, sipped through a network straw, on computers you don't own and can't control the software of.
Not in a malign way, ofc. They could earn use of browsers back, layer by layer, explaining in high fidelity how they work, starting, idk, with a passable description of 3G's CDMA/TDMA tradeoffs? Or maybe a good description of TLS and PKI? Either would be fine. We're not monsters.

• • •

Missing some Tweet in this thread? You can try to force a refresh

Keep Current with Alex Russell

Alex Russell Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!


Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @slightlylate

13 Oct
The cognitive dissonance of anti-web and anti-choice rules made & justified because device resource scarcity [1] against the marketing of ALL POWERFUL CPUs [2] is dizzying.

[1] infrequently.org/2020/09/the-pu…
[2] macworld.com/article/357533…
For a sense of scale, when the anti-choice, anti-web rules were laid down, Apple's fastest device was the iPhone 3G; a single-core, 32bit, in-order, ~400MHz chip attached to 128MiB of system memory.

Today, the slowest device you can buy directly from Apple is based on the A12...
The A12 is a 64 bit, 6-core, 2-and-change-GHz part with ~~8MiB of L2 cache~~ attached to 3GiB of RAM in the most resource-impoverished device Apple markets today:

Read 7 tweets
14 Sep
Trying again: Apple's iOS store shenanigans include a subtle & unique catch-22 journalists should grok:

- when apps violate policy, Apple says "use the web"
- ...except every iOS browser is required to use Apple's engine...
- ...and it's Apple keeps it year behind
This is hidden from view because no iOS browser maker dares to submit a browser that shows a "this isn't _real_ Firefox" (e.g.) banner...because what is the user supposed to do? Buy a new phone? They also can't afford to be cut off from all the world's rich users.
But why is Apple's engine & browser years behind?

Because Apple doesn't fund the WebKit team with anything like the headcount they'd need to keep up. And let's keep in mind that this isn't down to some sort of cash crunch.

This is a choice.
Read 8 tweets
17 Aug
Now imagine a world where Apple hadn't cut off the web at the knees and the things we regularly do on Android were possible, e.g.: WebGL 2, WASM threads (soon), Audio Worklets, large media storage, prompted PWA install, push notifications -- not to mention the upcoming stuff...
...backpressure for sockets, web transport, web codecs, WebGPU when it's ready (not when Apple deigns), payment handlers, etc. etc.

🍎 has used control not just to curate the store but also prevent the web from being a viable alternative & it's a goddamned scandal.
"oh, but feature X is in a tech preview" is the new "believing FB when they say they have 'more work to do'".

At some point you have to look at the pace and trend and conclude that not allowing other engines is strategic.
Read 4 tweets
19 Apr
I don't usually do this, but it's about public health and this site is getting a lot of press and HOLY !*#$ WHAT IS WRONG WITH THE REACT COMMUNITY!?:

This feels like the right place to invoke @tomskitomski:

If I had to guess, this probably wasn't ever tested on anything w/o a "Designed in Cupertino" badge.
It's *more than 900K of JS* to see the headline data. A screen shot is significantly smaller.

Nothing about this is OK.
Read 5 tweets
28 Feb
Increasingly distracted by the Performance Inequality Gap: the difference between those in the high-performance bubble thinking they're increasing richness without decreasing reach, but who are actually tanking reach by making content inaccessibly slow.
Users with the fastest devices and networks -- which includes ~all developers and business decision makers -- are leaning into technologies (JS) that, by their very nature, are decreasing the reach and usability of their services for users outside the bubble.
These devs & managers benefit from the Performance Inequality Gap in many (often indirect) ways, but not nearly as much as their now-margninalized users (and their businesses) lose.
Read 9 tweets
3 Nov 19
There seems to be confusion about how, exactly, Apple keeps the web second-class on iOS. Understandable! It's the interplay of several interlocking effects. Let's examine them (thread).
First, no matter how app-like it is, Section 4.2 of the App Store Review Guidelines excludes web experiences from being discovered via the search box where users go to add things to their homescreen.

Structural prejudice against the web by policy: developer.apple.com/app-store/revi…
Next, Apple under-invests in Safari's engine (WebKit) in ways that cumulatively make it difficult to do anything new and ambitious. The cumulative effect of the under-investment is hard to overstate, but it can be graphed:

Read 9 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!