• 1 Post
  • 1.61K Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle





  • I hope you can see that they are being paid by the federal government to disappear people and are on school property pissing instead of doing what any other professional on their shift would do and find another place.

    You are right it’s very different. A high school person playing around with people his same age should certainly have to defend his case. Every ice agent should also have to explain why they were unable to use all their tactical gear and vehicles and planning to travel elsewhere to pee somewhere instead of literally exposing themselves on visible camera footage on school grounds. Every time you give them an inch it will become a mile









  • Working on hobby or shorter lived projects makes all your points acceptable. My work is generally on enterprise SaaS software with vast lifecycle and my thinking is

    separate css files

    module.css with imported classes: my go to outside of tailwind

    These are the same thing, unless it’s not configured correctly.

    inline styles

    Only makes sense for something computed. Like a color computed based on a user selection. Otherwise it should be a class

    scss

    On a well-maintained project SCSS should be second nature. Something like a Vue single-file component project with scss will certainly not add to the bloat. You’d just have extra lines of vanilla css to scope classes and children selection/scoping that scss does with better syntax, in addition to scss functions and the like. Note that CSS is improving to do the work that SCSS has previously done, just as JS is improving to do the work natively that frameworks, libraries, and toolkits have previously done.

    bootstrap

    Yeah bootstrap, like jQuery, had it’s time. It’s largely been replaced by native tooling that shouldn’t require external libraries. There’s plenty of CSS libraries that are purely for theming, which is mostly what people used bootstrap for. (Smart defaults, basic component and typography themes, etc).

    To me tailwind makes sense for setting up projects quickly, but gets out of hand when it comes to customization on a larger scale. You eventually end up with overrides to tailwind’s default styles that become hard to manage, outside of the scope of their theming implementation, and then ironically you’re usually just using CSS variables which is back to the core toolkit.