Looks like there is going to be a shift to using nftables in arch. The iptables package in core is currently for the legacy interface with an iptables-nft package for the new interface, but the core-testing iptables package is for nft interface and there is now a iptables-legacy package in core-testing.

My guess is they are moving packages that can work with nftables to depend on that instead of iptables which looks like it is shortly going to be using the new nftables interface anyway. Probably as part of migrating to nftables by default. Looks like docker does have experimental support for nftables in version 1.29 and that is when the dependency was added to the PKGBUILD script.

It does not look like nftables or iptables conflict with each other at a package level. And nftables can work with iptables rules.

It is probably worth just migrating to nftables now if you rely on managing iptables yourself.

The US government does not like welfare programs because it gives money to the poor. They would rather give tax reliefs to the rich instead.

There is loads of evidence that welfare programs can save more money then they cost. But that does not funnel money to those in charge.

People seem to forget that most of the open source language library code out there is written by people working for companies, being sponsored by companies or writing it so they can use it where they work. Some might start out as hobbiest projects but if it survives and grows it eventually will be sponsored in some form. Even if indirectly by some guy that wants to use it where he works.

Once had a missing semi colon at the end of a c header file. The compiler kept complaining about the c file and never mentioned the header. Not all errors lead you to the right place.

Though most of the time people just don't read them. The number of problems I have solve for people by just copy pasting the error they gave me back to them...

By clear receiver it means there is only one function a name can point to. For instance you cannot have:

struct Foo;
impl Foo {
    pub fn foo(self) {}
    pub fn foo(&self) {}
}

error[E0592]: duplicate definitions with name `foo`
 --> src/lib.rs:5:5
  |
4 |     pub fn foo(self) {}
  |     ---------------- other definition for `foo`
5 |     pub fn foo(&self) {}
  |     ^^^^^^^^^^^^^^^^^ duplicate definitions for `foo`

Which means it is easy to see what the function requires when you call it. It will either have self or &self and when it is &self it can auto reference the value for you. This is unlike C and C++ where you can overload a function definition with multiple different signatures and bodies and thus the signature is important to know to know which function to actually call.

Yes rust has a operator for dereferencing as well (the *). This can be used to copy a value out of a reference for simple types the implement Copy at least.

Where did you get that from?

https://small-modular-reactors.org/smr-cost-estimates/ suggests the opposite:

$2,000 to $6,000 per kilowatt for SMR vs $4,000 to $9,000 per kiliwatt for large scale ones.

Plus they don't take 10+ years to build, and each one is not a bespoke construction leading to better scalability as the more you can build the cheaper things become.

Well, Redhat is owned by IBM now so basically spot on

It is not impossible for people at Honda to care. Just not the right people, those that can actually make a difference. The decision makers are all looking for what gives them the most profit, if not then they are not in their position long or, really, never get to a position that matters in the first place.

The only thing that capitalism cares about is profit, by very definition.

So? It is basically always as efficient as resistive heating at its worst, and the vast majority of the time it is massively more efficient. And even then they can remain more efficient even as low as -25C and might need resistive heating backup at places that get below that. But even in places that can dip below that they are often not that cold all year round. So overall throughout the year they are way more efficient on the majority of days even if you need a less efficient backup system.

We really need to think of the whole situation rather than just focus on the but sometimes part of the problem. Yes, sometimes they dont work as well. But overall through a year for the vast majority of places a heat pump can be all you need and is a lot more efficient than other heating systems.

Nah, it is them trying to control the bill by saying they are for it - if only these concessions are made. The article shows what they dont want to give up, under the guise of safety and security and disallowing repairs that might weaken that. And since they have been increasing the number of parts that are serialised in the name of security I bet they would argue repairing these parts will weaken their security and therefore cannot be allowed. Also, they want to focus on authorised repair channels, which they already massively lock down to the point they are more shipping stations than actual repair places. But also want to force third parties to disclose when they use used or non genuine parts - which since they only sell whole assemblies rather than individual components will likely force everyone that is actually making repairs to advertise that they use used/refurbished parts.

So they still want control, they just realise they can have better control by claiming to be fighting for right to repair while undermining any useful impact any bills would otherwise have - all while claiming they are for right to repair.

But then people can choose the option that does not have them scrolling for hours. Which means less time and less views on the platform. Why would they give you that option?

It's the same, ctrl + r. It is a bash/shell thing so works on any os that uses bash or similar shells. Note, it is not the command key, but ctrl, unlike a lot of other shortcuts on macos.