pull down to refresh

50 sats \ 1 reply \ @pabnull 12h \ parent \ on: What do you use for your frontend stack? Design AskSN devs

personally, i think it’s great, but i called it a ‘bridge’ because from what i read in your post, you seem a bit hesitant to fully switch. it could be an easy way to try things out while keeping control.

  • components are fully editable, so you can change what you want without breaking thinks
  • built on radix/base ui, so accessibility and basic behavior are handled
  • you don’t have to stick to presets; you can use css, css-in-js, or tailwind
  • everything lives in your project, so you own the code and structure
write
preview
0 sats \ 0 replies \ @k00b OP 11h

maybe i've been unclear, but i'm trying to validate my decision to switch to base/stylex - not deciding if i should switch. i'm trying to think through what systems properties i want, attempting to avoid use this thing generally everyone uses by default without understanding the tradeoffs (and let's be honest, vibing and dgaf for the most part)

i know i don't want to use shad already. it's perfect for people that want presets and want these decisions to be made for them, and i get you can customize it too. that's what boostrap was for a long time, so i don't have anything against that.

having some experience being an end user of enshittified 3rd party libs now, I'm trying to pick things i'd be happy to troubleshoot/review/maintain myself. i want to provide the abstraction layers - which i will probably vibe too tbh, but at least i'll understand them.

by chemistry analogy, i'm looking to make my own molecules so i'm looking for the right atoms/elements. i'm not looking for a premade molecule.

maybe i should be looking for a premade molecule though. i just don't see much reason to start there when i can vibe my own molecules.

reply