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
Software cultures that indulge in ignorance of constraints facilitate magical thinking, which eventually erodes the foundations out from underneath even conservatively-constructed experiences if left unchecked.
This is bad for users, but also business. A great shame of frontend's lost decade is that we lost the ability to adapt because so much of the community was high on frameworkism.
=> More informations about this toot | More toots from slightlyoff@toot.cafe
And I don't know how to say this any more directly than this: any frontend engineer who brings React or Angular on premises (without an honest bakeoff & guardrails), in 2025, is de facto bad at their job.
=> More informations about this toot | More toots from slightlyoff@toot.cafe
@slightlyoff What is the alternative to React?
=> More informations about this toot | More toots from danielinoa@mastodon.social
@danielinoa https://infrequently.org/2024/11/if-not-react-then-what/
=> More informations about this toot | More toots from slightlyoff@toot.cafe
@slightlyoff Interesting article, will read 👍
=> More informations about this toot | More toots from danielinoa@mastodon.social
text/gemini
This content has been proxied by September (3851b).