The most valuable thing for the community to extract from projects like these would be capability based drivers, ideally on top of seL4.
The choice to not use seL4 as a base for Fuchsia is also confusing. It lends credence to the idea that Fuchsia is a project to retain engineers, rather than to build a solid OS. I think it would be possible for a team like the Fuchsia team to build a better platform than Genode, but starting from scratch without seL4 is unlikely to produce anything better. They definitely didn't come up with a better security model, or IPC performance.
The exact quote is :
>But then she noticed something even stranger - her kitchen was covered in a thick layer of butter.
>Butter went everywhere! On the ceiling, on the floor, on the refrigerator, on the toaster
Your phrasing sounds like something I'd read to my son and I could see him repeating all the items and adding some of his own.
Why? Quite easy actually - having random passwords is better than reusing the same everywhere. Random passwords are impossible to remember by a regular human, hence you need a password manager. Using a local file as a password manager poses a usability/availability risk (you have to sync it yourself, you have to back it up yourself, you have to make it available on all devices without putting it at risk, you have to secure it, etc.), hence cloud-based password managers are better for the average person, especially coupled with MFA for critical accounts (banks, email, etc.). If you're a highly technical or highly security conscious person, or under threat, the equation changes of course, but the recommendation for a cloud-based password manager isn't meant to apply to everyone, just most people.
Saying that I agree with you in that I see this technology as a tool that can be used by humans to make amazing things. No one really has yet as the outputs have just been blunted, sloppy things. But if I’m an artist I see these tools as the latest tool to help make things.
> not just the usual errors, inaccuracies and "common deviations" that you find in every C compiler, and that force you to secure libraries with #ifdefs.
And extension keywords for microcontrollers specific features, intrisics for CPU instructions, DSP specific capabilities,....
Yeah I am already used that what goes for Pascal gets another weigth when placed against C.
When the artists whose work was stolen to train these models are compensated for that work then maybe its a "tiny part". Until then it is taking peoples work and using it to create an ultimate competitor in their own market that they cannot compete with. They now have to compete against themselves and they haven't even been paid for that "privilege".
It was surprisingly easy- for all of LastPass's faults, at least they don't use shady vendor lock-in practices (like making data export needlessly difficult). And 1Password has a LastPass-specific import page, which made the migration dead-easy.
The value to consumers is hypothetically that splitting it up will increase competition in the ad tech space. This will in turn lower ad spends from brands and hopefully push their real metrics to be more accurate, less fraud, etc. This will in turn lower advertising spend for these brands will which theoretically end up in lower costs to consumers.
Some other random thoughts.
1. Why would google (or any of them) make a good faith effort to stamp out fraud when it is lining their pockets? They are so big their really isn't a strong alternative and brands can't choose to just not play.
2. Why should the dominate browser effectively drive the privacy/tracking conversation for the largest ad tech player? This is an inherent conflict of interest and is unlikely to lead to better privacy for the consumer.
3. Why should a company that benefits from tracking/analytics be driving the development of one of the top 2 OS for mobile. On face value we are heading towards a world where buyers have to pay a premium for privacy (arguably iPhone, debatable), but android (largely budget phones) have no such or at least inferior protections. Why would they ever strengthen consumer privacy on mobile if its lining their pockets now.
Citation needed. Which is the point of the person you're responding to. For an untrained person to even get to what is considered 'high' intensity in their first workout is not common.
I do all sorts of training with trained and new people alike and have never seen rhabdo in person. I know it can happen, but I think the stories stick out because it's so uncommon.
During peacetime, the US Coast Guard is now part of the Department of Homeland Security. (It was part of the Department of Transportation fro 1967 - 2003.)
Bitwarden isn't much better, but they do have a cli technical users can cobble something together. (I ultimately decided to skip on Bitwarden also)
After some time with pass, I switched to a more integrated solution, with KeePassXC on desktops and Keepass2Android on mobile, with sync via OneDrive.