Mastodon Feed: Posts

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
lolgop ("L O L G O P") wrote:

Attachments:

Mastodon Feed

Reblogged by kornel ("Kornel"):
monsieuricon@social.kernel.org ("K. Ryabitsev") wrote:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
starfleetjobs@botsin.space ("Starfleet Jobs") wrote:

Mastodon Feed

Reblogged by lloydmeta ("Lloyd"):
ross@rossabaker.com ("Ross A. Baker") wrote:

Mastodon Feed

Reblogged by lloydmeta ("Lloyd"):
alexelcu@social.alexn.org ("Alex Nedelcu :java:") wrote:

Mastodon Feed

jeffsonstein ("Jeff Sonstein") wrote:

Muddy Waters Blues Band on Jul 1, 1965

https://wolfgangs.app.link/SGkJJdbqVvb

Attachments:

Mastodon Feed

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
alda@topspicy.social ("Alda Vigdís :topspicy:") wrote:

Mastodon Feed

Reblogged by cstanhope@social.coop ("Your friendly 'net denizen"):
MicroSFF@mastodon.art ("Micro SF/F by O. Westin") wrote:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
ChiralTheAlien@home.social ("Chiral The Alien") wrote:

Attachments:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
electricarchaeo@scholar.social ("Shawn Graham") wrote:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
davetroy@toad.social ("Dave Troy :toad:") wrote:

Mastodon Feed

Reblogged by teller ("Siim Teller"):
henrikroonemaa ("Henrik Roonemaa") wrote:

Attachments:

Mastodon Feed

Reblogged by teller ("Siim Teller"):
michuk@101010.pl ("Borys Musielak") wrote:

Mastodon Feed

Reblogged by teller ("Siim Teller"):
henrikroonemaa ("Henrik Roonemaa") wrote:

Attachments:

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

The broken padlock has the effect of creating solidarity: managers experience it as a broken site in the same way users do. And when managers experience something going badly, it gets fixed.

And yet, browsers do not do this for performance. At all. Not even in devtools.

It's a shocking failure of imagination and care.

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

You see, the key problem in web performance today is getting managers to give a shit.

This has been true for many years, but we like to talk around it and pretend that the next incremental engineering improvement will actually change things, even when we know full well that it will not.

And we know what works; as this decline and atrophy has taken hold, we've also succeeded in migrating the entire web to TLS. It's an incredible feat! How, you might ask? With an icon.

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

The one exception to this has been Core Web Vitals, but that was weakened and delayed by multiple years for predictable (and predicted) reasons.

But even the weak-sauce that CWV served has helped to highlight just how badly browsers have let everyone down -- users most of all.

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

The post-scarcity dream was, of course, wrong on the facts about desktop computing too, but putting that to the side for a moment, I think it's important to focus on the browser's role in enabling frontend's lost decade.

We suffered a collective hallucination this dramatic because nobody shook the community awake. There was no intervention.

Fearful, cowardly product managers even tried to police my work in highlighting how poorly it was going & succeeded in sinking effective interventions.

Mastodon Feed

blithe ("Blithe") wrote:

How do I get the Home Depot tiny gloves from the commercial though?

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

The dream of infinite CPU and fast, stable networks was sunk by the emergence of broad-based mobile computing:

https://infrequently.org/series/performance-inequality/

Here's a talk from '16, warning of what I was seeing then; a harbinger of what was to come:

https://www.youtube.com/watch?v=4bZvq3nodf4

And an solemn update from '19 on how it was going (spoiler: badly):

https://vimeo.com/364402896

And here's the latest update on networks & CPUs:

https://infrequently.org/2022/12/performance-baseline-2023/

TL;DR: we have never been post-scarcity.

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

Something like half my job these days is to help MSFT's web products improve. This is a continuation of the incidental consulting I did at Google from '15-'21, and in that time it has become crystal clear to me that the market for frontend tools and technologies is broken -- and browsers are to blame.

What we experience as pervasive slowness, even on the high-profile sites, is a consequence of a culture that fell in love with a post-scarcity dream. A dream that was, in fact, a mirage.

Mastodon Feed

slightlyoff@toot.cafe ("Alex Russell") wrote:

Per usual, @brucelawson said it better than I could:

"Bad performance is bad accessibility":

https://brucelawson.co.uk/2022/bad-performance-is-bad-accessibility/

Mastodon Feed

rmrenner ("The Old Gay Gristle Fest") wrote:

Finally tried out GUI Dwarf Fortress yesterday. I just did a couple of the tutorials. It's really cool but it's a lot to take in. It also doesn't play well with 4k screens

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
AlgoCompSynth@ravenation.club ("AlgoCompSynth by znmeb #MaskUp") wrote:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
grobmeier ("Christian Grobmeier") wrote:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
TrisResists@mstdn.social wrote:

Attachments:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
evangreer@mastodon.online ("Evan Greer 🏳️‍⚧️") wrote:

Mastodon Feed

kornel ("Kornel") wrote:

@rust_gamedev I've noticed massive GIFs from ffmpeg in your weekly news. Try (pure Rust) https://gif.ski for encoding — it should give you smaller files and better quality.

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
Fullnihilism@kolektiva.social ("Wolf Girl Winter") wrote:

Attachments:

Mastodon Feed

Reblogged by jeffsonstein ("Jeff Sonstein"):
coastal8049 ("Scott Tilley") wrote: