• 0 Posts
  • 45 Comments
Joined 2 years ago
cake
Cake day: June 18th, 2023

help-circle




  • Working on hobby or shorter lived projects makes all your points agreeable. 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.










  • Sure but it’s dumb to search “Were you able to resolve your issue?” That exact comment exists across hundreds, perhaps thousands of github issues, it’s a generic question. The unique comment is the follow through. And if they tried searching the first comment, it would take a few more seconds to try searching the second comment. So there is not “no marker.”







  • kautau@lemmy.worldtoProgrammer Humor@programming.devShots fired
    link
    fedilink
    arrow-up
    6
    arrow-down
    1
    ·
    1 month ago

    You mean subscribe to them right? You can’t buy Jetbrains products to use in perpetuity. I pay for their all products pack. They have a 40% continuity discount after two years, which is nice. I would agree they aren’t terribly expensive for commercial software, but they are competing in a space full of free and/or open source alternatives, unlike many production-level commercial softwares.

    That being said, their AI integration features are awful across the board, whether it’s their own AI or copilot.

    And while I much prefer jetbrains stuff to something like vscode, it’s way more about UI uniformity for me. VS Code extensions outside the top 20 tend to slap themselves wherever they want, with html/css dialogues that don’t fit the UI, and there’s often like 6 versions of an extension that’s like “this one is deprecated, but also the other one is deprecated, but the new one is made by microsoft but it’s actually 3 extensions now.” Whereas generally jetbrains extensions fit within my action panel, toolbar items, and can move widgets to different sides of the UI so that version control stuff, code analysis/structure stuff, external integration/database stuff, and project trees all get their own dedicated part of the workspace