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

esa

@ syklemil @discuss.tchncs.de

Posts
9
Comments
175
Joined
2 yr. ago

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • To unjerk, as it were, it was a thing. So on old systems they'd do stuff like represent æøå with the same code points as {|}. Curly brace languages must have looked pretty weird back then:)

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • Jess. Ai'm still lukking får the ekvivalent åv /r/JuropijenSpelling her ån lemmi. Fæntæstikk søbreddit vitsj æbsolutli nids lemmi representeysjen.

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • No, I'm pretty sure the weird o with the leg is in basic ASCII. It's also missing Latin characters like Æ. It's a very weird standard.

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • Q. P is a common character across languages. But Q is mostly unused, at least outside the romance languages who appear to spell K that way. But that can be solved by letting the characters have the same code point, and rendering it as K in most regions, and Q in France. I can't imagine any problems arising from that. :)

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • I'm not entirely sure here, but you are aware you're in a humour community, yeah?

  • I'm an Emacs developer

    Jump

  • Neovim developer got sidetracked configuring their reply plugin

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • It's a joke because it includes useless letters nobody needs, like that weird o with the leg, and a rich set of field and record separating characters that are almost completely forgotten, etc, but not normal letters used in everyday language >:(

  • The devil said, “Take this glyph-laden grimoire and try to render it cross-platform.”

    Jump

  • With ASCII æs the åriginal sin. Can't even spell my name with that joke of an encoding >:(

  • Typst is hiring

    Jump

  • There's some interest in attracting non-awful people from the US. Get a bit of a brain drain going from there:)

  • Typst is hiring

    Jump

  • What, like an anglophone who can't tell the difference between the i and y sounds?

    (Or do the anglos actually pronounce it "tajpst"?)

  • Parse, Don’t Validate AKA Some C Safety Tips

    Jump

  • Isn't that sort of just the cost of doing business in C? It's a sparse language, so it falls to the programmer to cobble together more.

    I do also think the concrete example of emails should be taken as a stand-in. Errors like swapping a parameter for an email application is likely not very harmful and detected early given the volume of email that exists. But in other, less fault-tolerant applications it becomes a lot more valuable.

  • Parse, Don’t Validate AKA Some C Safety Tips

    Jump

  • It is pretty funny that C's type system can be described pretty differently based on the speaker's experience. The parable of the Blub language comes to mind.

  • Parse, Don’t Validate AKA Some C Safety Tips

    Jump

  • Parsing is a way of "validating early". You either get a successful parse and the program continues working on known-good data with that knowledge encoded in the type system, or you handle incorrect data as soon as it's encountered.

  • Parse, Don’t Validate AKA Some C Safety Tips

    Jump

  • I feel I gotta point out it's a pretty funny example—email comes up so frequently as a thing that you're recommended to neither parse nor validate, just try to send an email to the address and see if it works. If you need to know that it was received successfully, a link to click is the general method.

    But "parse, don't validate" is still a generally good idea, no matter the example used. :)

  • Deleted

    Permanently Deleted

    Jump

  • Yeah, you generally just want the same auto-stuff done as would be enforced in CI anyway.

    … all the other stuff you could fix but wind up just ignoring because your team ignores it will just glare at you until you sneak it in somehow

  • stop

    Jump

  • It's just a monoid object in a category of endofunctors, no biggie

  • Big Rust Update Merged For GCC 15 - Lands The Polonius Borrow Checker

    Jump

  • It’s Not As Simple As “Use A Memory Safe Language" [S4 events]

    Jump

  • Do also note that by saying that some % of crates use unsafe, it's not implied that 100% of the code in that crate is marked unsafe. It could be as little as one line; it could be a whole lot; it could be well-documented and tested; it might not be. (This is part of what the talk is about.)

    It's also rather to be expected that there's more unsafe in embedded. As Steve Klabnik gets into in How to Do Embedded Development with Rust (GOTO 2023), it's used when you e.g. want to set a certain memory address to a certain value, which in a lot of contexts is nonsense, but in some contexts makes a LED light up.

  • Working with systemd timers - Dmitry Kudryavtsev

    Jump

  • post from 2025

    systemd is a relatively new utility that provides an array of components for Linux systems.

    what

    Snideness aside, systemd timers can be pretty neat. They also have some features like being able to specify "Daily" and setting some looseness in when it triggers if you e.g. have a fleet of machines and don't want them all to do something at exactly the same time.