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/)AG
AggressivelyPassive @ agressivelyPassive @feddit.de
Posts
16
Comments
1,465
Joined
2 yr. ago

  • Again, because enshittification refers to the exploitative monopoly.

    Vegas as a whole never had a monopoly, no individual casino in Vegas had a monopoly, and today's online gambling has certainly some larger players, but none of them have the market power to squeeze both sides as much as Amazon does.

    What you're seeing is simply a shift within the market. Nothing else. Yes, people are being exploited, but not because of some monopoly that forces them to do so. There's plenty of competition in the online gambling sector.

  • He received bribes in 200€ bills and then complained that it's really hard to actually pay stuff with it because hardly anyone ever uses anything larger than 100€ bills and it will draw attention (and suspicion).

  • Compared to Java, it makes me write the same data structures three or four times.

    Just an example: if I want to be able to insert a struct via Diesel, I need to write the actual entity, an entity without the id for inserts and maybe some other structures for queries. Also, I need to write a schema file defining the DB plus an SQL statement for actually creating the needed tables.

    Another example: explorative testing. Sometimes you need to disable chunks of code for testing purposes. Maybe that long running computation or a DB query, etc. Rust often forces you to write a bunch of "corrections" to make the code seem correct again.

    I get that this is useful, but for my line of work, it's just a pain in the ass.

  • Rust needs some layer on top to make it more usable for the typical business apps.

    I tried to build simple CRUD apps, but it's still a huge pain, because there's just so much stuff I need to do myself and so much low level overhead that I need to keep in mind.

    Java is worse in many ways, but for cobbling together a mess that barely manages to do its thing, it's really great.

  • If cloning a repo is an issue, you're using CI wrong. --shallow has it's purpose.

    Anyway, in my project a complete CI run including local integration tests takes about an hour. We could cut that down by running things in parallel, but we never bothered to add more runners.

    I would say, if your tests hold you back, you might want to reconsider testing. Staged testing is an option, or just reevaluate whether you really need all those test cases. Many integration tests are not really testing that much, because 95% of them overlap.

  • Because Ryan wrote it like this 10 years ago and nobody bothered to rewrite it in C.

    Back then, I'd guess most developers were relatively fluent in assembly, so if there's only a small change to make, they'd just change the assembly and move on.

  • What I'm wondering is, how many deaths are attributable to slow evacuation? Usually, you only hear about the great catastrophies where the entire plan crashes into a mountain and evacuation was never an option.

    But how many accidents cause a situation where quick emergency evacuations are actually needed? I have absolutely no intuition about that.

  • Because the hurdles for being banned are intentionally very very high.

    Oh, and the authority in question (Verfassungsschutz) had a head who's a bona fide Nazi. So the agency to protect the constitution from (right wing) extremists was led by a right wing extremist.