Ancestors

Written by Alex Russell on 2025-01-21 at 20:27

The correct response to realizing computers are fast is not to make your software slow, because:

a.) you won't benefit as much as you hope

b.) if you break pro-user norms, so will every other site/app/library, and your thing will feel slow even if it's "fine" in isolation

c.) HW bounty is not evenly distributed, so your product becomes less usable non-linearly below some resource floor

Pretending constraints don't exist is not engineering, it's bullshitting.

=> More informations about this toot | More toots from slightlyoff@toot.cafe

Written by {Insert Pasta Pun} on 2025-01-21 at 21:40

@slightlyoff I don't think this is how that happens.

A (web*) developer starts off with a fast computer and fast internet due to the nature of their job (rapidly making and editing a web app)

so they tend to have better monitors, processors, RAM, and internet.

thus they don't notice how slow and bulky their code is.

• other developers do not receive good enough equipment bonuses, and should unionize to get better equipment ;3

=> More informations about this toot | More toots from risottobias@tech.lgbt

Toot

Written by Alex Russell on 2025-01-21 at 21:47

@risottobias That is exactly what I have been blogging about as the frontend privilege bubble[1]. But it's all facilitated by a software culture that sets no expectations of grounding, and apportions no responsibility for outcomes.

=> More informations about this toot | More toots from slightlyoff@toot.cafe

Descendants

Written by {Insert Pasta Pun} on 2025-01-21 at 21:49

@slightlyoff see that seems more accurate. it's an un-examined systemic bias of developers.

it's not as your first toot says "the correct response to realizing computers are fast is not to make your software slow",

it's that web developers own F1 engines while everybody else owns ride-on lawn mowers.

=> More informations about this toot | More toots from risottobias@tech.lgbt

Written by Alex Russell on 2025-01-21 at 21:53

@risottobias This is literally what React's developers did. It's what they continue to make excuses for, and never apologize or clarify about. They had global knowledge that React was unworkable for the low end and mobile without extreme care, but only sold upside and (always false) dreams of cheap client compute. That's worthy of ridicule and comment.

=> More informations about this toot | More toots from slightlyoff@toot.cafe