Sass, Pug, Haml, Slim, Stylus, and their friends all aim to make writing various bits of your frontend easier. And they mostly deliver on this primary promise. But they are all victims to the vagaries of open software development, and seem to have mostly fallen by the wayside. I loved using these through my career, so its with a bit of sadness that I realized I don't want to use them for new projects.
  • Haui@discuss.tchncs.deEnglish
    4·
    1 year ago

    18% reduction (max) for learning a different language than html? Hard pass.

    Especially with css you can give most of those small web design studios (and most wordpress plugins) a run for their money.

    I think it’s unnecessary to learn some obscure „alt-sub-language“ if the improvement is so little.

    • spencer@beehaw.orgEnglish
      2·
      1 year ago

      I’m personally a big fan of SCSS over both CSS and regular Sass. Keeps the same syntax so it’s not hard to pick up, but fixes some of the CSS jank.

      That said, I think they’re rolling out a new CSS version that covers some of those tweaks? I recall hearing abt that

      • Paradox@lemdro.idOPEnglish
        2·
        1 year ago

        CSS has been growing a lot of “super powers” lately, that used to require a pre-processor. Custom properties (variables), nesting, calc, and color-mix used to be things we’d reach for a preprocessor for, but can now be done 100% in pure CSS. And generally, the CSS based versions are better than their old preprocessor counterparts. calc can mix units, so you can easily do things like calc(100% - 1rem) to subtract a rem from 100% of the parent container. Can’t do that in Sass. Custom properties can be set by Javascript, or by media queries, and follow CSS scoping rules. Thats how I handle light/dark mode on my site.

      • Paradox@lemdro.idOPEnglish
        1·
        1 year ago

        Nim does a lot of things very well, I love writing JSON and parsing JSON in Nim, probably the best experience I’ve had with JSON, followed shortly by just implementing it as a protocol in Elixir.

        Karax’s pattern of just using language constructs to assemble HTML isn’t really novel, as nice as it is; Ruby has had one for ages in Builder (and several offshoots), Elixir has Temple, and there are probably some in other languages. They’re sort of one level of abstraction less than slim/haml, but its quite pleasant writing them. But they suffer some of the same issues Slim/Haml suffer, but also can suffer when trying to use them with component frameworks, or anything that exposes custom tags. This can, of course, be solved via metaprogramming or language-level templates, but it is a concern

        • brie@beehaw.org
          2·
          1 year ago

          The Temple examples look very nice; the Builder ones to my eye look quite cluttered in comparison, which I’m guessing is due to differences in syntax between their respective languages.

          I tink the main downside of templating in general is that it ends up making interfacing with JavaScript and plain HTML harder, compared to CustomElementRegistry based components.

          • Paradox@lemdro.idOPEnglish
            2·
            1 year ago

            Builder is mostly targeted at building XML files, and so compared to XML its fairly terse. HTML is just a nice also-have. There are template langs in ruby that are a lot closer to the Elixir temple variant, but I can’t remember any of them off the top of my head haha.

    • Paradox@lemdro.idOPEnglish
      1·
      1 year ago

      Well it’s pretty much just HTML without brackets and closing tags. There are a few oddities to enable this, and it falls down on inline styles (in the same way json fails vs XML for inline formatting), but it is still pretty fun to write

      But with the issues these languages are starting to manifest, that 18% isn’t worth it anymore