Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)E
Posts
9
Comments
170
Joined
2 yr. ago

  • W is a double-v for us, so our alphabet goes uvw (u ve dobbel-ve), rather than uwv (ju dabbel-ju vi).

    Germanic languages vary a bit in their attitude towards w; we Norwegians use it pretty much just as a fancy old-timey v and could frankly drop w from our alphabet without missing anything (just like q is practically never used).

    Germans use w the way we use v, and then use v pretty much like f.

    The anglo w sound is something we have to learn in English class, and even then a lot of people start to hypercorrect and pronounce even the "v"s in English as their w. It can be wery funny to listen to, or wery frustrating.

  • Imagine if that money had been spent on building out renewables instead

  • Us nords have nine vowel letters:

    • a e i
    • o u y
    • æ ø å

    and they all are just themselves for a name. Like e isn't "c with a line" any more than q is "o with a leg".

    They're also all monophthongs, which is hard to communicate to anglophones who pronounce their vowel letters overwhelmingly as diphthongs. E.g. anglos probably read the vowel letters as

    • ey i ay
    • åo ju way
    • ??? ??? ???

    There's an æøå song which might help.

  • It's cow tools from a Gary Larson comic

  • Oh man, I used to have my irssi claim it was Comic Chat. Fun times.

    Like other MS tech of the era it was at least lightly into EEE territory, as the client would add stuff to messages that just looked like crap to users of normal IRC clients, similarly to how Outlook users would have seemingly random Js in their text, because Outlook rendered that as a smiley through the power of a Windings font.

    But it sure did spawn some memes.

  • OCaml should transfer pretty well to Rust. Rust can feel like an ML dressed up in C's braces.

    Similarly, if you can write in Haskell without having to reach for IO, then you can probably satisfy Rust's borrow checker with no more effort.

  • Isn't rather "meme" the refinement from "gene" (seeing as it was chosen to rhyme with gene)

  • Nice to see libxml2 dropped I guess, after that ordeal with it becoming unmaintained last year. But curious what the replacement is, and if others are finding replacements as well.

  • Not that big on ligatures in monospace, really. I think I just go with what seems to look kinda nice and has a big enough amount of symbols to not look weird once a few of them are needed.

    Also generally prefer dotted zero, or an inverse Ø. Fonts that make 0 and Ø look the same might as well just drop the slash altogether.

    In spite of that I've been using Fantasque Sans Mono for years. At least the slash in its 0 doesn't extend beyond the circle like in an Ø.

  • Especially given that a lot of us are interested in content filtering, just that we want to be in control of what we're subjected to, cf adblockers.

    I'd be super fine with it if I could tune, say, the YouTube app on our TV to not subject me to ads for illegal gambling sites, fossil fuels, vacations in authoritarian regimes, etc.

    But that's exactly what they don't want us to have control over, because that means lost income.

  • The article has some good points, but it read as pure LLM slop to me.

    Was reminded of the meme: Heartbreaking: The worst person you know just made a great point.

  • Yeah, the usual argument for not picking GPL with Rust is based on how it applies to static linking, which is how Rust works by default. But the coreutils are executables, not libraries.

    Even for the libraries I think it'd be nice with some stronger guarantees. Allegedly the EUPL is copyleft but allows static linking, so probably something to look into.

    Ah well. At least it's also possible for orgs like GNU to re-release forks of MIT stuff as GPL. The MIT licensing doesn't only work for the proprietary-preferring orgs.

  • Programming @programming.dev

    RFC 3339 vs ISO 8601

    ijmacd.github.io /rfc3339-iso8601/
  • Also doesn't help that the grammar reeks of LLM.

  • I'm also a fan of baud. I really should alias cat to baud -400 cat or thereabouts.

    Bonus: run baud -800 bat --color=always and you get that wonderful old dot matrix printer feeling of the cursor just stopping whenever the color codes are being processed.

  • Be kind, rewind.

  • Programming @programming.dev

    Brendan Gregg's special collection of freeware tools for system administration

    www.brendangregg.com /specials.html
  • re: mksh I have snippets in my editor for shebangs++. E.g. #!<tab><enter> nets me

     bash
        
    #!/bin/bash
    set -euo pipefail
    
      

    or

     python
        
    #!/usr/bin/env python3
    # pyright: strict
    
      

    etc

  • Programming @programming.dev

    The Jetbrains 2025 survey results are out

    devecosystem-2025.jetbrains.com
  • Got 'em

    Jump
  • .nl

    checks out

  • They are utility, as long as you don't have a theme that randomly picks a new colour every time the token type changes.

    It's a bit like having a bunch of different tools or utensils in separate colours. Even if the drawer is messy and the colour ultimately arbitrary, you can pick out utensils because you're habituated to looking for a given colour.

    Just stick to one theme and you'll get the same thing but for code. Theme hopping kills your habituation, and resets you to the "I can tell that these are different things because the colours are different" stage.

  • The stance coupled with the garish background colour reminds me of how Pike also had a very dismissive view of using colours for syntax highlighting, and then later opened up about having a kind of colourblindness.

    Both of them also seem to mean colour when they write syntax highlighting. That's just one typographic tool among many. We also use bold, italics, underline, and even whitespace to highlight programming syntax. We could write a lot of programming languages as if they were prose, but we don't. People hate that and call it "minified code".

    Humans also have a great capacity for colour vision, much better than most mammals. Some of us are even tetrachromats. Our colour vision is basically a free channel of information: It's always on; we don't have to concentrate to be able to discern most colours. When things in nature are more colourful than usual, like leaves in fall or a colourful sunset, we don't find it tiresome; we find it refreshing and seek it out. But when our built environment becomes all shades of grey, we tend to find it depressing.

    But humans are also different in many ways here. Better or worse colour vision is one thing, but some are also prone to getting overstimulated; others require more than average stimuli. We have great selective attention as a species, but again, individuals vary. There's no one syntax highlighting that works for everyone.

    Ultimately we should just find some syntax highlighting that we find generally pleasant, and then stick with it until we reflexively use the information carried in those colours. Use habit formation for our benefit.

    Tonsky may enjoy his garish background colour and have found a mushy colourscheme that works for him, but he's also way off base in his assessment of colourschemes in general.

  • Linux @programming.dev

    Canonical releases Ubuntu 25.10 Questing Quokka

    canonical.com /blog/canonical-releases-ubuntu-25-10-questing-quokka
  • Programming @programming.dev

    The challenge of maintaining curl

    lwn.net /Articles/1034966/
  • Programming @programming.dev

    Parse, Don’t Validate AKA Some C Safety Tips

    www.lelanthran.com /chap13/content.html
  • Rust @programming.dev

    Dyn you have idea for dyn?

    smallcultfollowing.com /babysteps/blog/2025/03/25/dyn-you-have-idea-for-dyn/
  • Programming @programming.dev

    It’s Not As Simple As “Use A Memory Safe Language"