See also: web performance and React
-
-
Replying to @slightlylate
I mean, there’s an example in every project of a certain size. Node.js blocked LTTNG tracing for Linux because... we already had DTrace and Joyent had a way to use that to trace their Linux VMs. One of the first features io.js shipped with was LTTNG support :)
1 reply 0 retweets 13 likes -
Replying to @mikeal @slightlylate
The solution wasn’t to convince Joyent that LTTNG support was worth their time to review, it was to move to a participatory governance structure where people were empowered to resolve the issues they care about.
1 reply 1 retweet 23 likes -
Replying to @mikeal @slightlylate
as far a React goes, I’m just out of patience for everyone in these arguments. if you aren’t Facebook, don’t use React if you have non-Facebook problems — they’ve made it clear how that project runs and what the priorities are.
5 replies 34 retweets 112 likes -
Replying to @mikeal
I wish this were visible to more people. Nearly nobody looks long or hard enough to grok these dynamics.
1 reply 2 retweets 13 likes -
Replying to @slightlylate
Modern startups have a very odd relationship with open source. Their businesses depend on it more than software they purchase and they expect a service guarantee (which doesn’t exist) that matches their need rather than their investment (which is $0)
3 replies 5 retweets 50 likes -
Replying to @mikeal @slightlylate
Even worse. Startups are allowing themselves to be constrained by the open source dependencies they are beholden too. It is costing us a lot, but we've collectively decided to chalk it up and expend energy elsewhere.
1 reply 0 retweets 3 likes -
I was talking to some friends about this recently. Instead of fixing problems with current projects, engineers are incentivized to find a whole other solution and just take the pain of swapping it out. Essentially it's searching for an acceptable set of externalities.
2 replies 0 retweets 5 likes -
Rewrite is the path to blog-post/promo/RSUs, and doing it in a way that aligns you with "industry practice" sure helps your terrified and afraid managers/recruiters "compete for the best talent" The echo chamber runs on sovereign wealth fund cash.
2 replies 0 retweets 4 likes -
(which is not to take anything away from the value of standards, but choices about compiled-down interfaces w/ one impl aren't standards)
1 reply 0 retweets 1 like
I'd love it if this pathway also had a factor for user benefit weighting...some sort of peer review to do more than tribally self-congratulate.
-
-
Replying to @slightlylate @polotek
User benefit is harder to measure than developer preference so it’s always going to be second class :( The only silver lining is that developers really do like to obsess about performance, it’s just usually the wrong performance they obsess about.
1 reply 0 retweets 4 likes -
They don't obsess, they cargo-cult. If they obsessed,
@tkadlec,@tameverts,@HenrikJoreteg, and@triblondon would have private islands and I'd be able to focus on giving them features (safely) instead of planning mitigation strategies and jawboning VPs to fix their disasters.2 replies 1 retweet 14 likes - 5 more replies
New conversation -
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.