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/)TE
Posts
31
Comments
173
Joined
2 yr. ago

  • In a world where your IDE and maybe also compiler should warn you about using unicode literals in source code, that's not much of a concern.

    VSCode (and I'm sure other modern IDEs, but haven't tested) will call out if you're using a Unicode char that could be confused with a source code symbol (e.g. i and ℹ️, which renders in some fonts as a styled lowercase i without color). I'm sure it does the same on the long equals sign.

    Any compiler will complain (usually these days with a decent error message) if someone somehow accidentally inserts an invalid Unicode character instead of typing ==.

  • Yeah, also a bunch of other details, and the whole plot is way more focused on the war in the movie. In the book it's more of a backdrop. You should give it a read, it's worth it :) I also like her other books!

  • I don't know the answer, but happy to see someone talking about this book. I feel like so many people know the movie and have no clue that it's based on the book, nor how much they changed it. I personally love the book and am happy to see it.

  • But a unique identifier in game doesn't actually enforce bans, because what's stopping someone from creating a new one? VS if you create a PSN account, you need some sort of verification (e.g. email address).

    They could've done something similar with a non PSN login, though people would've probably still complained. And for them, it's not 3rd party because it's published by Sony IIRC, so it's actually an in house system.

    I also don't own the game, but I just wanted to point out the reason in their argument isn't entirely invalid.

  • Note that OP made a distinction between "need" and "ought to" and I agree. You don't "need" to know any of these, but you "ought to" because knowing them TO SOME DEGREE helps you use the machine more effectively and safely. Networking course is definitely going overboard, but I still think they're important to know. I'm pretty sure doctors already do understand the basics of how MRI machines work.

    Learning the basics of how WiFi works avoids people getting confused when WiFi doesn't "just exist" everywhere, or why it drops out suddenly when a lot of people are using it even if you have full bars. Learning about HTTPS and SSL lets you understand what it keeps secure and how that can keep you secure when you're e.g. banking.

    That being said computers and software now are specifically designed to hide their inner workings as much as possible to simplify things for their users so it's a bit of a special case.

  • Do you mean admonitions? E.g. info, warning, etc? There's precedent for that in commonly-used open source implementations, e.g. obsidian.md (which uses the same syntax, and started before). What semantics does it break? It's designed to read well in plaintext and render nicely even if used in a renderer that doesn't support admonitions, e.g.

    [!NOTE] Information the user should notice even if skimming.

    As opposed to other common markdownish implementations that use nonsensical plaintext which renders poorly in alternative renderers. Here's a discussion on the topic in the CommonMark forums.

  • My "scrum leader" (who we handled agile just fine without before) is constantly complaining about points or priorities shifting, to the point that he'll tell us to not put what we're actually working on on the board because it'll mess up the burndown chart.

    One of the 4 values of agile is "responding to change over following a plan". He's parroted this to us before, and yet still doesn't seem to see the irony.