still surprised that the people that prefer not to write CSS want to put it in HTML instead of JavaScript
19 replies
@zachleat that’s because their HTML is created with JavaScript. They don’t really write HTML anyway
@zachleat real 10x developers put both HTML & JavaScript in CSS
@benschwarz :before and :after are the only real `content` creators
@zachleat @benschwarz it's about time we get multiple ::before and ::after so we can finally create websites without anything but the html element!
html::before {}
html::before::before {}
html::before::before::before {}This will be our day of revenge!
@zachleat day ain’t over yet
@beep there is at least 3 more <div> of <span> left!
@zachleat please don’t
@peruvianidol same, but also surprised
@zachleat I don’t mean to defend tailwind, but not having to switch context and coding just editing one file feels nice. That feeling came from using Bootstrap helper classes (at least for me).
@MoritzGiessmann @zachleat Having some utility classes can be great. Having only utility classes is… not my favorite.
@Chris @MoritzGiessmann well said!
@MoritzGiessmann @zachleat utilities for highly repetitive compound classes makes sense. But polluting markup with atomic utilities (that could also be achieved with variables) is not my favorite thing.
Also writing CSS without having to change file can also be achieved with <style> right?@MoritzGiessmann for me, single file components are a much better abstraction that stays closer to the platform
@zachleat am i allowed to offset my love of utility classes with my simultaneous love of static sites and minimal client js?
@d3v1an7 we can all have a few utility classes, as a treat!
@zachleat the HTML is rendered with JS, so tomato/tomato