Skip Navigation

Posts
8
Comments
324
Joined
2 yr. ago

  • The amount of code you save grows with your codebase. It was 18% for that one, small example. In a larger codebase it can be quite a bit higher.

    While I have, more or less, moved to just writing html-style templates, I do miss how easy it was to refactor something to have a different tag name. Vim and other editors do have shortcuts that make it easy to change both the opening and closing tag, but in indent based syntax, I didn't have to worry about this. There was only one tag to change.

  • 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.

  • 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.

    A good template would make interfacing "easy". JSX[^1] is a very good example of how you can interface quite easily, and the templates used in Surface work really well to bridge some of the complexities of a server-rendered but client-dependent syntax.

    [^1]: I know JSX isn't a template language, the differences don't matter for the purpose of this discussion

  • 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

  • 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

  • cult of personality

    [Ian Cutress]

    LMAO proving the point

  • Just like how OfficeScript is but isn't JavaScript?

  • Nesting is now in native CSS, so it's even easier

    My approach for variants is to use attribute selectors. You don't get massive class names and it becomes more obvious what things are doing. Discover ability gets hurt a bit, but that was never BEMs strength either

    https://pdx.su/blog/2023-07-27-use-css-attributes

  • It's the absolute best computer I've ever owned. Maxed out it's ram and everything just flies

  • Smidge over 1.1Gbps peak, average probably around 900Mbps.

  • 6E is great, but basically nothing supports it. I got a 6E capable AP from Ubiquiti, and looking at my devices table, basically nothing has ever used the 6GHz radio. My house has a wide variety of devices, many new. The only thing that's used it is my MacBook

  • That's how it's supposed to work but a lot of techs just forget to set the limits or update the QoS tables and so your limits are more in the physical realm

    Sort of like how in the 90s and 00s you could pop the filter off the line where it came into your house and get extra channels for free

  • I bought the Xoom and the Nexus 10, and got my wife a Nexus 7

    Google abandoned all within an extremely short timeframe. The Nexus 10 suffered the worst, getting an awful ui regression a few months after it came out

    I have seen no evidence Google will do any better this time

  • A lot of ISPs have silently upgraded their bandwidth peaks, without telling customers, and use rented modem speed as a way of upselling. I.e. "We'll double your speed for $15 a month"

    Buying a new modem can end-run that and get you the speeds without changing your bill. When I had comcast in the Bay Area, buying a new modem gave me an extra 100mbit up and 30 down, without any interaction with comcast.

  • Might wanna buy a new modem. 15 years ago was, what, DOCIS2? The new DOCIS4s could get you far faster internet

  • Makes certain levels of nesting painful

    You can say this is a design choice, and you shouldn't ever go too deep in config, and I'd agree, but it is a limiting factor to be aware of

  • I like how elixir approaches it: configs are just elixir script files that have a module for some common conventions. Gives you a lot of power, and no goofy new syntax

  • Not like clockwork orange. Like Brazil

  • In my experience it's pretty universal. My TV offers it (Android/Google TV), my Xbox has it, and Plex has it

  • This feels like a false history. Hulu had original content all the way back in 2008, with Dr horrible