Follow

seeing a project advertise as "no javascript" is a huge red flag for usability (and accessibility) tbqh, especially the fact that they won't even consider it even when it might be the best tool to make a ui element work.
yes use only what you have to
yes do progressive enhancement
no don't take a techbro all-or-nothing stance, it gets you nowhere

hot take I guess, and probably not one that's gonna be popular

@linear i dont really have hard examples on hand and it's probably a bad idea to get hot takes out right before much needed bedtime, but;

colorschemes, fonts, font sizes, come to mind. While *technically* possible through horrible css hacks or page reloading, it makes the ux for switching much much worse, especially as you need to switch a couple of times to see what works best.

Really tbh, any interaction on a page (and this project has plenty) sucks when it has to navigate and load a new page whenever you want to favorite some thing, etc

@f0x @linear firefox has a feature that still exists for theme switching based on alternative stylesheet <link> tags declared on the page

nobody uses this because google didn't implement the same feature

this makes me kinda upset tbh

@f0x @linear like the feature you want actually exists but the megacorp wasn't interested so you basically can't use it

@f0x @linear as a bit
i will write some nginx config that checks your UA string, and if it's chrome it delivers javascript that emulates alt css, and if it's firefox it just does the thing without js

@linear you also don't gain *anything* by saying you won't use any js, just shooting yourself in the foot, now or later

Sign in to participate in the conversation
Pixietown

Small server part of the pixie.town infrastructure. Registration is closed.