tibastral2
But your approach is from the past man, really... .btn is not reusable among pages / projects / etc. => it's always different, and when you understand that specificity wars is the main problem of css, you will not want to use your idea again.
It LOOKS cool to have a <button class="btn"> inside your html. because it's more readable. But it's NOT explicit. You fragment truth into different pieces. and it makes it IMPOSSIBLE to test things in isolation.
One last thing. Using all the "last features" of css is just putting you in a place where you depend on the browser carriers to handle things for you when I prefer personnaly to rely on myself and my craft. But that's a personal one ;)
But this belief is only true if the language to describe the structure is html or js which creates not reusable pieces of style/structure.
But when you go for a different approach where everything is functions and strong types (ADT), like when you use haskell for exemple, this debate is over, because you handle EVERYTHING in your code, and stop fragmenting the truth into opaque and dissociated worlds (html, js, css, database, glue, docker, ...).
- the icon showing how many claude instances are running
- sleep preventer does not only sleep prevent, it also allows being able to dictate to claude code from a ... local llm => amazingClaude Code sleep preventer (and dictate to Claude Code)
My Journey to Pure No-Code Addition (Spoiler: Plot Twist Ending)
TL;DR: Spent 6 months trying to build addition in "no-code". Ended up writing pure functions. I am now enlightened.Month 1: The Dream"Code is gatekeeping! I'll revolutionize math with pure visual programming!"Buys 7 no-code courses, $2,400 in SaaS subscriptionsMonth 2: The Workarounds- Tried pre-built text elements (2,500 combinations, Bubble crashed)- Attempted human-in-the-loop via Zapier +...
It's called retention my friend, and it's the key metric for apps.