4 ms·
I've been reading awful takes like this since I started writing software. "PHP is an awful language, superior developers write in Perl." "Rails is bloated and
by generalk 7y ago
I've been reading awful takes like this since I started writing software.
"PHP is an awful language, superior developers write in Perl."
"Rails is bloated and slow, making it unfit for any real work."
"True developers don't rely on frameworks, writing all your own code is the only way to be performant."
If you wanna handicap yourself, be my guest.
I've written three or so projects in TailwindCSS, and it lets me create responsive designs quickly. It gives me a very sane set of defaults to build off of. And most importantly, it helps me get a product to production faster than writing raw CSS.
- holler 7y agothat may be so, but I think it's a valid point to bring up the tradeoffs you're making, including using a non-standard dsl that other designers/developers/hires will likely be unfamiliar with. personally having written css since I was a teenager, my gut reaction is "eww", but if the team or stakeholders deem it to add value to a project and not affect productivity, sure why not?
- hombre_fatal 7y agoThe grandparent comment wasn't "bringing up tradeoffs". They literally just said real devs don't use frameworks.
- andrei_says_ 7y agoI think it’s not for people who know CSS. It’s specifically for SPAs where site-wide changes are related to component changes and so having to change the html is not that different from changing the css. I can not force myself to use something like this but I’ve been writing CSS for a long time. I use BEM and predefined sets of colors and space values to ensure consistency and that’s efficient enough for me.