Why? Did Fuschia enable any new features on Google Home Hubs which would have been more difficult/impossible with a Linux kernel? It's an honest question, my bias is that Fuschia is a solution in search of a problem but I am happy to be convinced otherwise.
Hubs are fully vendor locked in, and Google controls every single but running there. Security argument, while valid like everywhere, seems BS. I’d be surprised if security profile for a hub was main concern for the product.
Anecdotally my hub got much less responsive around the Fuchsia update. I’m not blaming Fuchsia directly for it, but one could wonder what would happen, if resources dedicated to that, were spent on usability improvements.
Let’s be honest, Fuchsia was rolled to a Hub, because it’s a product no one really cares about and team needed some guinea pig/stuff in production to justify its existence. I say that confidently, as someone working at big tech, and having myself experience being in rollouts like that.
The Nest team definitely won't agree with your value judgement of these devices, nor do many of the users who paid for them. To this end, even if there are different motivations for different teams and other tactical considerations, it is absolutely necessary for the owning team of a product to have a real motivation for such a significant operation as replacing the entire firmware and runtime in the field. That set of motivations are rooted in the properties of the OS: https://fuchsia.dev/fuchsia-src/concepts
It's not at all dishonest, the article itself highlights that Trump's administration was also concerned about misinformation, especially early on in the pandemic in regards to things like economic stability and availability of goods.
> The United States government pressured Twitter to elevate certain content and suppress other content about Covid-19 and the pandemic. Internal emails that I viewed at Twitter showed that both the Trump and Biden administrations directly pressed Twitter executives to moderate the platform’s content according to their wishes.
> At the onset of the pandemic, the Trump administration was especially concerned about panic buying, and sought “help from the tech companies to combat misinformation,” according to emails sent by Twitter employees in the wake of meetings with the White House. One area of so-called misinformation: “runs on grocery stores.”
It goes on to talk mostly about the Biden administration, but that's an editorial decision. The author in no way claims that Trump's administration wasn't sending moderation requests to social media companies. This is not a Republican vs Democrat thing; every government under every administration coordinates with social media companies.
If you're going to approach censorship through a purely partisan lens, you're not going to get very far.
I should have been more specific so asinine comments like these who can't read the story before commenting don't show up:
Imagine if the Trump Administration had people who donated predominantly to their cause making decisions at the highest level at Social Media companies and directly affecting policy of posts being taken down such as Jim Baker asking why "don't be afraid of COVID" isn't taken down.
Imagine if employees at social media companies took the view that they knew better than abortion and lgbt activists and overruled coverage of their protests, flagged their tweets, locked their accounts from gaining any distribution.
Imagine if the Trump administration established a department within the San Francisco field office of the FBI to EXCLUSIVELY check social media feeds of their political opponents to have them reported to twitter under government pressure to take them down.
I thought all of this was implied and anyone reading this comment would at least acknowledge the severity of these revelations, but here we are.
Apple in many cases goes out of their way to avoid collecting your data. See Maps for example. Users' usage of Maps is associated with a random rotating identifier not tied to their accounts. This is quite different from Google Maps.
> historically they have never told my spouse about my affair
Have we forgotten Google Buzz? Google changed GMail to publicly list the people you email most. In one case, this de-anonymized a woman's blog and enabled her abusive ex-husband to stalk her. https://fugitivus.wordpress.com/2010/02/11/fuck-you-google/
This is IMO the most likely way that "bad stuff" will happen: not maliciously, but through privacy-invading misfeatures connected to pushing people to share more.
Thats 12 years old... I think it's a real testament to Googles privacy behaviour that amongst their 2 Billon+ users over 11 years, there are no fresher news stories that come to mind.
Compare with facebook/instagram, where it seems every other week someone messes up the privacy settings and posts something to an audience they didn't intend because the product is deliberately designed to encourage accidental oversharing.
> Trump announced his intention to fill the U.S. Strategic Petroleum Reserve “to the top” on March 13 [2020] as global oil prices went into freefall amid the coronavirus outbreak as governments issued stay-at-home orders that have obliterated fuel demand.
An emboldened Russia started a war of conquest, drastically reducing supply. Though honestly there's plenty of effects from the coal market started by China's big moves, so it can't all be places on Russia. And Russia was going to do this at some point, it's been inevitable since their 2014 invasion, and also how their prior invasions and involvements have had almost zero pushback.
The pandemic made oil drilling + refining look like a bad investment, so the industry underinvested in new oil resources. Then Putin cut the oil and gas supplies to the world in an attempt to extort Europe into standing aside and accepting his conquest of Ukraine.
In addition, there was an explicit push by the Biden admin to make drilling less profitable (less permits, increased oil royalties, increased investor reporting requirements, and a PR push). It's not politically useful anymore - even the admin can't continue this while sanctioning Putin for his war of conquest - so people pretend it did not happen.
It might be acceptable in higher level languages where some things will simply break in corner cases, at which point the developer will just say 'don't do that' and all is fine. If you're aiming at a true low-level bare-metal-capable syscall-winapi-native-speaker language, this is not an option.
It’s weird and confusing, but also performant. Remember Rust is first and foremost a systems language. You can get a 10x speed boost by using the right string (str vs string) in certain circumstances.
I think you DO have to know about those, or close analogs, in writing Rust. I like both C++ and Rust but I will rise to defend C++.
1. Exception safety becomes "catch_unwind." You might object that nobody cares about that, but major C++ codebases (Google, LLVM, Mozilla) don't care about exceptions; they are built with -fno-exceptions.
2. Move semantics in C++ are annoying, and so is the borrow checker. In Rust you get hit by things like "this code is fine here, but you aren't allowed to refactor it into a function" because there's no interprocedrural visibility into struct fields.
3. Meta-template higgery-jiggery is real and bad in C++, but has a mirror in Rust. With C++ duck-typed generics you write dumb code that does the thing, and then you can refine it with hilariously awful techniques like SFINAE. In Rust you're googling higher-ranked trait bounds before you can even write the thing. What does `for` do again? I think "strongly-typed language, duck-typed generics" is a bit of a sweet spot and C++ has lucked its way into it.
4. "30 years of cruft" means things like "I speak C preprocessor" which is practical. C compat is why C++ is both so awkward and so successful. There's no smooth ramp from C++ to Rust, the way there was from C to C++; that's a choice and maybe the right choice but it has a price.
"Hilariously awful" template metaprogramming is a thing of the past. It has been years since it seemed needed, or since I read any. New, more intuitive features have displaced it.
With concepts in C++20, you get to choose whether templates are duck-typed.
