• 0 Posts
  • 18 Comments
Joined 1 year ago
cake
Cake day: June 8th, 2023

help-circle



  • I feel the same way. Designing good, opinionated APIs is HARD, but it also provides the best experience for both the author and the consumer.

    • Prettier is the undisputed king of JS formatters because it has no options by design. You set and forget.
    • One of the reasons iOS is so successful is because they lock down their APIs and put strict standards on apps, making it hard to write something that doesn’t at least look good and slot into the OS well.

    Among other examples.




  • Tekhne@sh.itjust.workstoProgrammer Humor@lemmy.mlgot him
    link
    fedilink
    arrow-up
    9
    arrow-down
    1
    ·
    2 months 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 ==.



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






  • What do you hate about macOS? From my perspective, it beats out Windows in ease of use, performance, likelihood not to break, and being *NIX; and it beats out Linux by having things working out of the box without needing to spend a decade tinkering just to get things almost working right.

    I use Windows for gaming (and work, unfortunately), Mac for general computing and programming, and Linux for servers and vms.





  • No, practically speaking the domain name should have no effect on access time. DNS has so many layers of caching that as long as SOMEONE has accessed the website nearby (including you), the domain lookup will be local and therefore fast.

    Anyway, DNS lookup times, even slow ones, are still not going to be noticable to the end use originally.