Live data from Hacker News

Project Fuchsia: Google Is Quietly Working on a Successor to Android

bloomberg.com

71–80 of 214 posts

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#71
post #32

> "The company must also settle some internal feuds. Some of the principles that Fuchsia creators are pursuing have already run up against Google’s business model. Google’s ads business relies on an ability to target users based on their location and activity, and Fuchsia’s nascent privacy features would, if implemented, hamstring this important business. There’s already been at least one clash between advertising an…

Would be nice if there were a competitor mobile platform to iOS that wasn't built from the ground up to sell you advertising based on personal data. I guess Blackberry was the last mobile OS that didn't need to know every detail of my pissing habits.

Blackberry gave the RCMP a global decryption key[0], then defended the practice[1]. Given the chance, they probably would have sold out their users as well.

[0] https://news.vice.com/article/exclusive-canada-police-obtain...

[1] http://blogs.blackberry.com/2016/04/lawful-access-corporate-...

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#72
post #10

Earlier quoted context omitted.

It will need some form of compatibility to get a foothold in the market, though.

From what I can tell, the compatibility plan is to market flutter/dart as a cross-platform development toolkit for Android and iOS. Fuchsia won't run android apps, but fuchsia apps will run on Android and iOS.

If you check the Zircon repo, you will see that they are backing in a linux virtualization layer in the kernel, so i imagine they will use that to bootstrap android linux apps in Fuchsia as a staging process, until android apps are completely native in a second phase.

Chrome OS already runs Android, so it would be a matter of stitching the Chrome os shell into Fuchsia to have both running in Fuchsia. First with virtualization of Linux, and later without it.

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#73
post #15

> "Switching away from Android could provide Google the opportunity to hit the reset button on any mistakes they believe they made a decade ago,". "They might be able to regain some power that they’ve ceded to device manufacturers and telecom carriers." How making a new OS achive this? What kind of problems Fuchsia could solve when Linux can’t solve? I personally hope Fuchsia would remain as an experimental project.…

https://spectrum.ieee.org/tech-talk/computing/software/a-mod...

There's basically nothing new in the Bloomberg article.

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#74
post #40
post #32

> "The company must also settle some internal feuds. Some of the principles that Fuchsia creators are pursuing have already run up against Google’s business model. Google’s ads business relies on an ability to target users based on their location and activity, and Fuchsia’s nascent privacy features would, if implemented, hamstring this important business. There’s already been at least one clash between advertising an…

> The ad team prevailed, this person said. Of course they did. A controversial idea, but you know how much easier this would be for everyone if Google offered an option for users to be paid for volunteering your information to them? It's a precedent most fledgling ad companies wouldn't be able to match... even if it's just a few dollars a month, or maybe 30ish bucks a year. It'd cut into Google's bottom line, but it…

It would be too expensive. Google is making $40 every time someone clicks on many categories of ads. They probably have users generating them thousands of dollars a year.

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#75
post #40
post #32

> "The company must also settle some internal feuds. Some of the principles that Fuchsia creators are pursuing have already run up against Google’s business model. Google’s ads business relies on an ability to target users based on their location and activity, and Fuchsia’s nascent privacy features would, if implemented, hamstring this important business. There’s already been at least one clash between advertising an…

> The ad team prevailed, this person said. Of course they did. A controversial idea, but you know how much easier this would be for everyone if Google offered an option for users to be paid for volunteering your information to them? It's a precedent most fledgling ad companies wouldn't be able to match... even if it's just a few dollars a month, or maybe 30ish bucks a year. It'd cut into Google's bottom line, but it…

I’ve got a better idea. Google could always ship a product that people are willing to pay enough for where it is a sustainable business without being as supported.

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#76

Earlier quoted context omitted.

Google doesn't sell your data. Advertisers pay Google to deliver their ads to the demographic they want to target.

Right. They don’t sell our data, they rent us out to the highest bidder. Much better.

It is much better, considering there are companies that do actually sell our data.

"rent us out to the highest bidder" is the perfect description of Google and FB's business model. It's hard to imagine how either company could change course at this point, even if they wanted to.

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#77
post #25

Apparently it uses a micro kernel, zircon. I'm curious about this kernel, honestly making something new from the ground up doesn't seem like a good idea. I wonder how much of an advantage it was for android to use linux as a kernel, but I guess it was a gigantic advantage, which let them focus on what mattered in the development of android. Other question: any kernel/OS developer here to explain if a micro kernel mak…

I'd like to know how Zircon compares to L4 (implementations).

When I asked Tanenbaum at FOSDEM why he didn't pick L4 for Minix 3, he just got annoyed and seemed to think I was asking why he didn't just use the L4 OS (which doesn't exist) instead of creating Minix 3 - or something. In any case I didn't get a good answer. He could have created his own implementation if he wanted, L4 is just a specification with a few existing high quality implementations that prove the concept...

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#78
Someone please answer this... I want to learn this.

Fuschia is getting swift support Flutter runs on fuschia Flutter uses dart

Do I learn dart or swift, personally I want to learn swift. Flutter only supports dart??? Fuschia supports swift

Is flutter going to support swift

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#79
post #9

I am really surprised Microsoft isn't doing something like this. They are losing the OS war.

They are. The fact that HN doesn't follow it just speaks to the anti-Microsoft bias here. They've had the OneCore project back in 2015-2016 to unify the kernel and core OS pieces, which was a success and is now powering every Windows device out there from Xbox to the PC. They have the UWP, their unified app framework.

They are also working on CShell, which is a unified UI/windowing/compositing system that will work across PC, Xbox, Mobile, etc.

CShell + OneCore + UWP are essentially becoming part of a "brand new" OS they're calling Core OS, which will strip the Win32 backward compatibility requirements and just work with UWP apps, primarily targeted at devices like phones and low power tablets.

You can search Project Polaris for more information

Re: Project Fuchsia: Google Is Quietly Working on a Successor to Android

#80

Someone please answer this... I want to learn this. Fuschia is getting swift support Flutter runs on fuschia Flutter uses dart Do I learn dart or swift, personally I want to learn swift. Flutter only supports dart??? Fuschia supports swift Is flutter going to support swift

> Do I learn dart or swift

I'm not terribly familiar with the landscape, but my suggestion is broadly applicable: learn both.

A developer shouldn't be constrained to a single language. Pick the one that's suitable for the project you want to work on. For the next project, do the same. In my experience you'll find it progressively easier to pick up new languages (and stacks, and paradigms, etc.) each time you do it.

IMO, a developer's goal should be to understand and implement design patterns, not individual languages.

... and for the record, I say this as someone who prefers a single language (Python) to all others I've encountered.

Post reply on HN