Why we must burn the entire web development stack to the ground, and never speak of it again.

[petrillic@hachyderm.io]

Why we must burn the entire web development stack to the ground, and never speak of it again.

https://paulmakeswebsites.com/writing/shadcn-radio-button/

[azonenberg@ioc.exchange]

@petrillic please do. It's awful and needs to go.

[geoffwozniak@masto.hackers.town]

@petrillic I'm not gonna object.

[hakfoo@mstdn.party]

@petrillic The mistake was letting designer into the room too early.
If users had obtained stylesheet control and aggressive personalization/customization first, wrapped around beige semantic content, the default atmosphere would be "websites that don't honour MY personal ergonomic preferences suck".

Instead, we got "hijack accessibility and download times, because Barry Turtleneck needs exactly THIS size and shape button for *branding*"

[trenchworms@eldritch.cafe]

@petrillic

https://eldritch.cafe/@trenchworms/115723350623291756

My ongoing theory about the persistent and now overwhelming jsification of the Web, in the face if being able to do all these things far more easily and directly.

tldr the egos of devs who have been told css isn't "reaaal'" coding are being exploited to ensure a Web that is utterly reliant on JS and can never have it turned off so that ad companies can continue to data harvest as much as possible.

[simx72@defcon.social]

@petrillic hi

do you have an rss feed to your writings? (i'd like to read your blog with my rss reader and get notified when you write something new)

[saraislet@infosec.exchange]

@petrillic well that's six nauseating forms of horrifying in a hand basket

[xchaos@f.cz]

@petrillic Take a simple thing and make it hard?

[alter_unicorn@masto.bike]

@petrillic and cars and rich people

[jeroen94704@fosstodon.org]

@petrillic Getting strong left-pad (https://en.wikipedia.org/wiki/Npm_left-pad_incident) vibes from this 😀 .

[daz@floss.social]

@petrillic Unfortunately, many developers argue against this saying the built-in ones look terrible and we need branded websites and native app-looking UIs, but fail to appreciate the full trade-off they're making when trapped in that front-end world. Not appreciating the over-complexity. Probably some gatekeeping too.

It's great with the new styleable select and recent developments means we're getting to where a front end build system is optional.

[slotos@toot.community]

@petrillic The developer experience is so good though!*

* for the developer that wrote it with no intent to ever deal with future modifications

[mnf@mastodon.social]

@petrillic Just felt like I should dig up this from 2023 🤪

https://mastodon.social/@mnf/109630717698727061

[raymaccarthy@mastodon.ie]

@petrillic
So many websites are designed by the clueless throwing javascript at it and often at client load time from 3rd parties.

THIS IS WRONG.

Also by default Browsers should use OS look/feel/theme and not a bad copy of something Google or MS thought up last week (so-called Material design or Modern). I'm looking at you Mozilla, who have broken the desktop GUI of Thunderbird and Firefox.

CSS if you must.

[raymaccarthy@mastodon.ie]

@hakfoo @petrillic
I don't want UI / GUI "branding" or developer customisation on any website or application. Makes it like a bad WinAmp skin. You do the "branding" with CONTENT, not by your own (usually stupid) idea of customising the appearance of standard GUI elements.

Over 15 years ago when I wasdoing Java, you could pick native or various custom GUI and the if Native then the program would look like a native program on whatever XP theme was installed, or Mac or random Linux desktop.

[http_error_418@hachyderm.io]

@petrillic charitably, I would say that the libraries like react were created because this kind of option wasn't available natively in CSS

But now it is, and they should be burned to the ground.