UX is a very subjective matter.

Bad news is that it is not clear at this point whether Mozilla is going to go forward with the implementation. A post on Reddit by one of the project members suggests that the build is a "rough proof-of-concept". Some features tested in the build "did not survive". It is unclear which did not, as they are not mentioned. Mozilla is, however, implementing those that survived the cut into Firefox. Again, the poster does not mention which those are. It is also not verified that the poster is actually a member of the project team, so take this with a grain of salt as well.

Source: https://mastodon.social/@bagder/112192351400749028

• Careful choice of program to infect the whole Linux ecosystem
• Time it took to gain trust
• Level of sophistication in introducing backdoor in open source product

All of these are signs of persistent threat actors aka State sponsor hacker. Though the real motive we would never know as it's now a failed project.

Source: https://turnoff.us/

Source: https://infosec.exchange/@fr0gger/112189232773640259

There is a work-in-progress version of Firefox for iOS with Gecko engine.

But, there is also a challenge that Mozilla is facing as Apple is still trying to make life of developers of other browsers as difficult as possible.

So, not sure how the whole thing will turn out.

Known issues and limitations

Currently, Intel x86_64 is the only supported host platform.
    AMD will most likely work too but is considered experimental at the moment.
Linux is required as a host operating system for building and running VirtualBox KVM.
Starting with Intel Tiger Lake (11th Gen Core processors) or newer, split lock detection must be turned off in the host system. This can be achieved using the Linux kernel command line parameter split_lock_detect=off or using the split_lock_mitigate sysctl.

Source: https://github.com/cyberus-technology/virtualbox-kvm

Not just MS Team, but the whole MS ecosystem.

This is how I explained it to one of my friends who is/was definitely a member of “I’ve got nothing to hide” club -

• Suppose you are in a pay-to-use toilet minding your own Business.
• That pay-to-use toilet is managed by a public/private entity called ToiletBook.
• Suddenly you notice a (hidden) camera in the room.
• When confronted, the owner confirms the only reason they took your picture to suggest you the perfect underwear based on your size. And, there is a legal guarantee that picture/data will never be used for any other purpose and only be processed by machine.
• Will you still go to such toilet?

BTW, that friend stopped talking to me afterward; not sure why 🤔 (Edit: I should stop giving shitty examples to anyone, as it seems ) 🤐

Back in '50s, the connection between Tobacco products and Cancer was evident. Since '70s connection between Fossil fuel and Global warming was evident.

Yet, no one heeded those warnings at the time. With cancer rate going up, and climate becoming increasing unpredictable/extreme, people now started to take notice.

With so much information to process, Human brain ignores information that doesn't have a clear relation to a significant real world problem that immediately impacts their lives. This makes us intelligent (at short term) and dumb (at long term) at the same time.

Using a service at free of cost (at the expense of your privacy) is acceptable by majority of population as it has no significant real world impact on their lives.

If tomorrow, a huge data leak from these imbecile data hoarders leads to massive transaction fraud/identify theft that impacts a significant percentage of population and their daily lives, only then there will be massive outrage that you expect.

Till then, we are the only one who escaped the Matrix, while rest embraced it.

The test data on article is about server setup which is the right use case for this change.

Moreover the L3 cache on CPU is what makes significant difference, IMO.

If that is true, not sure how much improvement consumer-grade desktop will see, given that most consumer-grade CPU will not have that much L3 cache on chip.