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/)B
Posts
4
Comments
109
Joined
2 yr. ago

  • What about the M-expression version (f[x])?

  • Me and my 9 disembodied heads judging people that don't learn an adhoc functional programming language solely so they can run Linux

  • aaaaaaaaaaaaaAAAAAAAAAAAAAH

  • NixOS is a dangerous drug, but at least it's a drug without side effects, since Nix is purely functional.

  • I'm partial to Terra's theme, but yeah, that whole OST is amazing.

  • I don't think having well-defined precision is a rare requirement, it's more that most devs don't understand (and/or care) about the pitfalls of inaccuracy, because they usually aren't obvious. Also, languages like JavaScript/PHP make it hard to do things the right way. When I was working on an old PHP codebase, I ran into a popular currency library (Zend_Currency) that used floats for handling money, which I'm sure works fine up until the point the accountants call you up asking why they can't balance the books. The "right way" was to use the bcmath extension, which was a huge pain.

  • Cuelang: https://cuelang.org/docs/reference/spec/#numeric-values

    Implementation restriction: although numeric values have arbitrary precision in the language, implementations may implement them using an internal representation with limited precision. That said, every implementation must:

    • Represent integer values with at least 256 bits.
    • Represent floating-point values with a mantissa of at least 256 bits and a signed binary exponent of at least 16 bits.
    • Give an error if unable to represent an integer value precisely.
    • Give an error if unable to represent a floating-point value due to overflow.
    • Round to the nearest representable value if unable to represent a floating-point value due to limits on precision. These requirements apply to the result of any expression except for builtin functions, for which an unusual loss of precision must be explicitly documented.
  • That works until you realize your calculations are all wrong due to floating point inaccuracies. YAML doesn't require any level of precision for floats, so different parsers on a document may give you different results.

  • YAML doesn't require any level of accuracy for floating point numbers, and that doc appears to have numbers large enough to run into problems for single-precision floats (maybe double too). That means different parsers could give you different results.

  • Depends on the monkey

  • Image is accurate, since without bugs, the food chain collapses and takes society with it, and the survivors will have to migrate to rural areas that can support a hunter-gatherer lifrstyle.

  • I don't not use Arch, by the way

  • Based and nixpilled

  • rule

    Jump
  • I have ghosted my jar of ghost peppers.

  • gr8 m8, I r8 8/8

  • It's cute enough that it's worth posting twice

  • He's trying to help you figure out a gorilla joke for this post

  • My jimmies remain unrustled

  • 196 @lemmy.blahaj.zone

    Literuley 1984

  • 196 @lemmy.blahaj.zone

    Rabies rule

  • Programmer Humor @programming.dev

    Happy 30th birthday to RFC 1631 ("NAT"), the "short term solution" we all rely on

    datatracker.ietf.org /doc/html/rfc1631
  • 196 @lemmy.blahaj.zone

    Kilrule was here