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/)FC
ferric_carcinization @ ferric_carcinization @lemmy.ml
Posts
0
Comments
154
Joined
4 mo. ago
  • I'm not that familiar with tax law in the USA, why is it impossible? Is it because making money by having money is not taxed, so if it makes up a large enough percentage of your income, the percentage of your total income you pai in taxes can never reach 40%? If so, at which point does it become impossible? (Unless there is a 100% tax bracket, which would be Un-American™)

  • Does the number of security vulnerbilities scale linearly or exponentially with the number of threads?

    But seriously, why would you make something like this in assembly? I can understand not wanting to use libraries, but even using C would make it portable.

    I would personally prefer to not to use assembly & C for handling untrusted input, which is something that a web server does constantly.

    This still seems interesting, but I can't understand why assembly was chosen for such a complex project. Compilers are pretty good at optimizing & computers are very fast, so I don't see there to be anything to gain by doing this.

    They say that their cryptography implementations are fast, but that's not the only thing that's important.

  • I've read that Xlibre is a fork of Xorg that would still get new features, so I did not know much about it. I use Wayland, as it works better for me, but after reading the readme, I somehow want to use it even less.

    This fork was necessary since toxic elements within Xorg projects, moles from BigTech, are boycotting any substantial work on Xorg, in order to destroy the project, to eliminate competition of their own products. Classic "embrace, extend, extinguish" tactics.

    How is it EEE? A point about embracing could be made, but wouldn't there have to be extension with non-FOSS code or difficult to implement additions to standards? Even then, as it's hosted on GitHub of all places, it doesn't seem to be that extinguished.

    Right after journalists first began covering the planned fork Xlibre, on June 6th 2025, Redhat employees started a purge on the Xlibre founder's GitLab account on freedesktop.org: deleted the git repo, tickets, merge requests, etc, and so fired the shot that the whole world heard.

    I haven't heard about this, but I would guess that it's from a CoC violation, based on the rest of the readme.

    This is an independent project, not at all affiliated with BigTech or any of their subsidiaries or tax evasion tools, nor any political activists groups, state actors, etc. It's explicitly free of any "DEI" or similar discriminatory policies. Anybody who's treating others nicely is welcomed.

    Calling DEI discriminatory is never a good sign.

    Together we'll make X great again!

    This seems pretty close to a certain right-wing slogan from the USA. I don't know if it's accidental or a joke, but I don't think that it's appropriate, and like the author, I don't have much good faith left for this.

    A lot of commits by the Xlibre developer were reverted upstream and the readme does not look professional.

  • What's disgusting about it? The only thing I can think of is the implicit return, which felt a bit icky at first.

    Also, as the if expression is an expression, you can call methods on it like so:

     rust
        
    if 1 > 2 {
        3
    } else {
        4
    }.min(5)
    
    
      

    (the above is still an expression, so it could be used, for example, as part of a condition for another if)

    Of course, you can write horrible code in any language, but the ability to use blocks where expressions are expected can be great sometimes.

  • Rust would allow you to

     rust
        
    let ret = if some_condition {
        <a lot of expensive calculations>
        result_of_operations
    } else {
        <a lot of other different expensive calculations>
        result_of_other_operations
    };
    
      

    Now you don't have to declare it inside the blocks.

  • It's way more common than you may realize. Intel & AMD (and other x86 CPU manufacturers of the time) did it before the first Crusoe CPU launched. (2000 according to Wikipedia)

    CISC architectures are now seen as inefficient, so all the new ones are RISC and new CISC CPUs just translate the instructions to their intenal RISCier microarchitecture. The CPU's microcode specifies what an instruction translates to.