No, but 5-level paging is opt-in anyway, so its presence isn't problematic if assuming a 48-bit address space. Linux won't allocate space outside the 48-bits unless you give an address hint to mmap outside the 48-bit range.
Briefly, algebraic data types add polarity to the types so that we don't have both S <= T and T <= S, which would imply equality. Instead we have S+ <= T- and T+ <= S-. The positive types represent a value source and the negative types are a sink. For example, in a function call, the args are negative and the return type is positive. Inside the function its formal parameters become positive and its return type is negative. Variables exist in an "ambipolar" state which can be both the source or the sink, depending on whether we're using it on the rhs or lhs of an assignment.
In practice, projects that take this approach do the majority of development in house, and external contributions are small. It makes sense that a company that may have spent several years developing a product can sell commercial licensing. The only alternative way to monetize AGPL works is to provide services and support.
Nobody is forcing anyone to give away their rights. You can always distribute contributions under AGPL in a forked repo.
The alternative is that if you're making meaningful contributions then it's in the company's best interest to hire you full time to do it.
Contributing upstream can benefit the ecosystem around the project, and the money that comes from commercial licensing also benefits it. In some cases the project would die if it didn't have the commercial side. They're not running a charity and if they aren't generating enough revenue they'd likely be working on something else rather than maintaining a FOSS project that doesn't make any money.
Clean has been doing this for nearly as long as people have been using monads, but it never got the attention Haskell did, which I think is quite unfortunate. Rather than implictly keeping track of references, uniqueness types are marked explicitly to inform that their values cannot be aliased. They can also be used with monads to improve ergonomics a bit.
Granule has uniqueness types like Clean built onto a linear type system, which offers some additional advantages.
In the case of forced vaccination, it's a reasonable comparison, as it violates several item of the Nuremberg code.
Some places did force vaccination, and even where it wasn't, there were plenty of high profile figures calling for it.
It's just a terrible idea to even contemplate trying this. The solution to misinformation is an informed public, which doesn't come about by censoring information, but allowing unfettered access to it so that people can make an informed judgement.
Who even decides what is misinformation, and how do you prevent them from lying and spreading those lies themselves (or lying by omission)?
In 1615, authorities labeled Heliocentrism as misinformation.
The Chinese authorities label the Tiananmen sq. massacre as misinformation and "prevent lies from spreading."
Even many of today's "scientists" are dogmatic in what they consider misinformation because they have an all-knowing god called "peer review," and some of them promote censorship.
This is the kind of thing where the censors think they're doing the world good by "stopping the spread of misinformation," but they will be the historical villains in future because all they're doing is giving an authority the powers to misinform the public, because any information these authorities don't want spread can be labeled misinformation.
The only thing that isn't potentially misinformation is that which you witness with your own eyes. Since everyone has their own eyes, calling what they witness misinformation is known as gaslighting.
The only way to prevent people sharing their experiences is called censorship.
What you're really asking is "can we stop people from lying?"
What about Arthiris? There's some link between UC and RA. I get both flare up at the same time, and I use the same medication (Azathioprine) to keep both in remission.
It's always about protectionism. No company wants the government interfering with its business. They want the government interfering in their upcoming competitor's businesses.
Probably the biggest development in seL4 since this is the MCS (mixed criticality systems) addition, which provides capabilities for budgeting CPU usage to give guarantees for components that need higher priority. There's some videos by Gernot Heiser on YouTube covering it.
Have a look at the MongoDB license (SSPL) as an example of an almost open source license which doesn't really impact personal use, but impacts big service providers who would be required to release the entirety of their source code. You can provide a proprietary alternative for those.
If you dual-license you will require a contributor agreement that any contributor grants you the right to relicense their contributions.