I think 80-ish days to recompile and old binary is a much better alternative to the total death of human arts and innovation, and the unending list of crimes against humanity that Marx's theory has led to every time it has been applied.

But to keep it a bit more videogame related, Marx always reminds me of this speech by senator Armstrong of Metal Gear Rising: https://www.youtube.com/watch?v=IMpuUUV2HeE . "We will use an absolute totalitarian state to abolish the state" - a lofty goal turned into complete lunacy.

[0] https://lwn.net/Articles/673724/

Also, past the weird bits, there isn't anything there. I have no reason to care for these characters. It feels like a vertical slice of a longer game, or a proof of concept.

DDLC has a really cool idea that should be tried again, in a way that remains consistent within its game world, with more character depth and a longer story.

I am now thinking if you can pull off an adventure game where some puzzles require editing the save file. It would be pretty tricky to make it understandable to most people. Now that I think about it, I wouldn't put it past Deltarune to eventually have an easter egg that can only be reached from a save state, which is impossible to achieve through normal gameplay. I know it doesn't have one right now, because all the scripts have been examined in depth and nothing like that was found.

So I see it as unavoidable evil. The patent system makes it lawful evil as opposed to chaotic evil, which is strictly speaking an improvement.

As a sidenote, if implemented as a macro, e.g.

    fn fast_sum_f64(values: &[f64]) -> f64 {
        let mut total = 0;
        fp_opt!(associative, {
            for value in values {
                total += value;
            }
        });
        return total;
    }

As an aside, unsigned does not save you from undefined behaviour. When sizeof(short)==2 and sizeof(int)==4 (e.g. x86, x64, arm32, arm64), then multiplying two unsigned short values happens by upcasting them to ints (see integer promotion rules), which can overflow the int.

My personal opinion is that along with making signed overflow defined, unsigned integers should be entirely removed as a type and there should instead be separate signed vs unsigned operators, because at the processor level there is no difference between the two, and there hasn't been a good case to separate them at the hardware level for the last ~half century. Basically, do what Java does with some syntax like unsigned{expr} which forces all integers inside expression to be treated as unsigned. Unsigned literals can stay, but they will be bitcast to signed equivalents if used outside unsigned context.

Then there is the fact that when something is patented, that has a chilling effect on competition, making the market less efficient.

There are also a lot of really silly patents that end up benefitting no-one, not even their inventor, but only result in needless litigation. The recent lawsuit between Nintendo and PocketPair comes to mind.

While there are cases in which patent law can help individual people profit from their invention, once all consequences are tallied, the overall effect of patent law on society appears to be negative.

In all seriousness, it is another stark reminder why you never rewrite from the ground up. Especially when you're replacing a foundational technology like the display server. In the same time Microsoft reworked their display driver model twice without requiring a single change from application developers. The Linux world doesn't have that many application developers, we should not be asking them to continually chase newer and newer APIs. A rolling stone gathers no moss.

I wonder if just letting the water gradually dissolve the uranium might not be fine, actually. If it is done far from wells and rivers used for drinking water, then the small amount of radioactive minerals that slowly seep out might not pose a danger. I can't find any studies to back it up, but I imagine there are places on Earth at which enriched uranium buried 1.6km underground poses no threat. I am no expert, so I would love to hear what others think.

The rest of the article can basically be summed up with "work takes too much time and pays too little", which is absolutely true.

I am not sure what the jab at stay at home moms or grandparents who help with childcare is supposed to be. Probably some other communist drivel. Grandma absolutely did not do unpaid childcare, she was insistent she had to teach us right and also got tons of labour and money from my parents. If the exchanges of money and labour between parents and grandparents in the context of childcare were measured, it would probably double the nation's GDP.