For government websites I’m certainly in agreement that static HTML is the way to go. Less sold on the “only serious projects are static” logic.
-
-
Replying to @tahini
I'm saying something different: it's not about static, it's about reach. Do whatever you can to improve the experience, but *start with reach as the primary consideration*. You can probably afford some JS! But not as much as the JS-industrial-complex wants to sell you.
1 reply 0 retweets 3 likes -
Replying to @slightlylate
Yeah I think I disagree with this, though. Most businesses start off with very few resources. The aim, nearly 100% of the time, is to prove an idea in a extremely limited market. That is largely how it is in the early stage world.
1 reply 0 retweets 2 likes -
Replying to @tahini @slightlylate
In the FAANG world, you are totally right. A new intuitive at Google should start with reach as the primary consideration.
2 replies 0 retweets 1 like -
Replying to @tahini @slightlylate
But isn’t that the bubble? Not the startups using React to get a product out?
1 reply 0 retweets 0 likes -
Replying to @tahini
FANG teams know limits *much* more than the folks buyimg JS-of-the-week. Search has N versions (where N is large) to maximize reach. GMail still maintains a static HTML version, because reach! Startups that buy this shit are dumb. Critical services that adopt it are *dangerous*
1 reply 0 retweets 0 likes -
Replying to @slightlylate
That’s my point. You should have this perspective. It’s important that you do, given what you do.
1 reply 0 retweets 1 like -
Replying to @tahini @slightlylate
A startup testing some idea using React in a single market isn’t dangerous though.
1 reply 0 retweets 0 likes -
Replying to @tahini
As an investor, I cannot express how deeply distressed it makes me to hear of founders who imagine their market is their set of friends/families/colleagues. It's OPP, and those people are ~not drilled into what opens doors, *but your effing job is to see what they don't*
3 replies 0 retweets 0 likes -
Replying to @slightlylate
Most startups don’t fail because of overloaded JS bundles. They fail because they market doesn’t want it. It’s far more bubble-y to tie failure of a startup to its _bundle size_ than to actually choose some overload framework. That’s the irony you don’t see. doubly as an investor
1 reply 0 retweets 0 likes
Most startups are unable to attribute failure to any specific cause. Bundle sizes are only a measure of "how much do you punch potential customers before they can access your [world changing] service". Some are worth a long gauntlet!
-
-
Thanks. Twitter will use this to make your timeline better. UndoUndo
-
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.