My favourite: The code does not work. You make a change, it breaks more. You undo that mistake: it now works.

One step closer to DRM filament spools. Just like the overpriced ink cartridges of 2d printers. The safety and security arguments are always bullshit. This is only about control over what you can do. No other printer has ever had an issue with safety or security with vastly more open designs.

It has to compete with:

• Climate change and the disasters it will cause.
• Nuclear war
• Some virus

Um no. Containers are not just chroot. Chroot is a way to isolate or namespace the filesystem giving the process run inside access only to those files. Containers do this. But they also isolate the process id, network, and various other system resources.

Additionally with runtimes like docker they bring in vastly better tooling around this. Making them much easier to work with. They are like chroot on steroids, not simply marketing fluff.

A water central heating system is a closed loop system that is under pressure. This means the water in it is circulated around and around the system and is cut off from other water supplies under normal operation. Naturally, slow leaks happen and gas can enter the system in various ways so occasionally this needs to be released from the system. Any gas in the system naturally collects at the highest points along the path - which tend to be the radiators.

When you bleed a radiator you are opening the system to the outside and hopefully where the gas has accumulated. Since the system is under pressure it forces the gas out of the system to equalize the pressure with the outside. This will cause the pressure of the system to drop and eventually it will stop.

However there should be a control valve somewhere, typically on/near the boiler that connects the central heating system up to the mains water supply. You can open this valve to cause water to flow into the central heating system and pressurize it and really this should be done every time you bleed the radiator a significant amount.

In apartments though you might find that you are on a building wide circuit, or you might have one isolated for your apartment. If you have a boiler in your apartment then you are likely on a closed system and should be able to equalize the pressure yourself. If it is building wide you need to talk with your building manager.

Note that you should not need to bleed your radiators that often. Once every several years should be more than enough. If you are doing it frequently then you likely have a large leak in your system and likely want to get someone to check that out.

Isn't, according to Catholics beliefs, the pope infallible? Is that not a core part of the religion that separates it from Protestants?

Are we about to witness a splitting of the Catholic church?

The only major roadblock is some anticheat software requiring highly invasive Windows rootkits to function, which Linux doesn’t really work with.

I consider that more of a feature then a bug

Ok then.

Ticket marked as closed: won't fix, cannot reproduce, not enough details

Yelp is a business engaging in shady tactics. So how can I ever trust anything they create.

With familiarity, can Rust’s intuitiveness match Python’s “from idea to deployment” speed?

Likely not at the start. Rust can take some time to learn to use it effectively it is not the fastest at throwing shit together quickly.

Or should I only learn Rust if I intend to create applications that need tight performance?

Also no. IMO rusts performance is only a nice by product of the language, yeah it encourages people to try it out, but they don't stay for the speed. They stay for the tooling and the feeling that once it compiles it will likely just work they way you intended. Rust forces you to think more about correctness and edge cases of your code - which does slow down initial idea to working prototype a bit. But IMO it quickly pays back dividends when you get something into production and it just works with no random crashing in the middle of the night.

It also makes refactoring a joy to do, where I hate refactoring in languages like python as you never know what you might have broken - likely something that you will find out only after you have deployed to production. Instead the compiler catches basically every thing that you missed before it will even let you run the code - so those edge cases are taken care of when you are developing, not after it fails in production.

I also find it is very nice with data processing/transformation as it lets you use functional coding styles which tend to lean towards clearer/easier to read series of data transforms.

If you want to learn it I would recomend starting out with the offical book, but you might also find zero to production or datawithrust interesting reads as well.

As with everything - it depends. Sometimes the FOSS versions are not very good, sometimes they are better than the official. Sometimes they are better for privacy, sometimes they make no real difference at all, sometimes the web version is better. Sometimes there is no FOSS version, sometimes the official one does not support Linux.

You are going to need to go on a case by case bases and decide each time.

They are hardly copying Twitter in this regard. Twitter is doing it for fuck knows why, trying to get more money from a dieing platform or something. But Threads:

“Spam attacks have picked up,” requiring new rate limit changes.

Are mitigating spam. That is reasonable and any sane platform will have rate limits in place to stop abuse. They only question is if the rates are low enough to affect normal users or not.

So just because two companies do the same thing does not mean they are strictly copying each other, here they have different reasons as far as I can see.

If you are going to complain about something, do it for reasons that make sense. Don't make shit up.