81–90 of 214 posts
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
> "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.
"One person who has spoken to Fuchsia staff described the effort simply: "It’s a senior-engineer retention project." This has been my therory for a while. You see all these different projects competing against each other (multiple messaging apps are a good example) and you think: why is Google so unfocused? But what Google basically wants to do is hoard engineers so they don't leave and go work for competitors and ma…
If you look at the industry as a whole products wax and wane based on market trends. Market leading products often struggle to innovate under the weight of their own success and are eventually replaced by a new innovator that's doing something right.
Google, by virtue of creating many different types of products in one category somewhat insulates themselves from this effect. They have effectively infinite money, so from their perspective they can somewhat emulate the greater market internally. They can let "startup" style teams form internally so if someone supplants one of Google's products, it's likely to be a Google team.
There are significant downsides to this (eroding consumer trust) which may take their toll on Google with time.
I wrote a small Flutter app recently and rather enjoyed the experience. I'm reluctant to spend more time on the technology, though, since it seems like it has a high chance of dying out. But as I understand it, Fuchsia would have native apps written using Flutter as well, which would be great, so I really hope it does take off.
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
In a basic sense, Flutter is based in Dart, but if you want to call into another language like Swift, there is a way to do so, called FIDL. I'm not sure if Swift has FIDL bindings yet, but I'm sure that it and many other languages will, in time.
Even today Flutter has support for Swift code on iOS the same way it supports ObjC, via MethodChannels. (This is also true for Java and Kotlin code on Android.)
"One person who has spoken to Fuchsia staff described the effort simply: "It’s a senior-engineer retention project." This has been my therory for a while. You see all these different projects competing against each other (multiple messaging apps are a good example) and you think: why is Google so unfocused? But what Google basically wants to do is hoard engineers so they don't leave and go work for competitors and ma…
That's a lot of money to pay just for retention of people who are not producing anything of value, consuming many other resources (office space, network, hardware, perks), and deeply committed to a project that supposedly will never benefit their employer.
A rich employer may retain an unproductive employee for a limited amount of time if they expect it to ultimately pay off. It just doesn't make any sense to retain someone indefinitely if they're not going to produce anything of value, and (implicitly) will quit the moment you try to put them on any sort of real-world valuable work. Google is a public company with fiduciary responsibilities to its shareholders and a legally accountable board, it can't just throw tens of millions of dollars away without good reason or explanation.
> You see all these different projects competing against each other (multiple messaging apps are a good example) and you think: why is Google so unfocused?
There are many good reasons to have multiple teams competing against each other, building the same product. Often it will bring a strong drive and pace to all competing projects, as well as cross-pollination, and eventually they often merge to a single deliverable that is better than any of the projects could produce individually.
> what Google basically wants to do is hoard engineers
I'm not sure why all these improbable theories make more sense to you than the plain fact that Android was designed quite a few years ago, has many natural deficiencies, and - like all technologies - will eventually be replaced by a superior successor.
That's exactly what Fuchsia is about. Its existence does not require any elaborate conspiracy theory. On the contrary: given how strategically important the Android market niche is for Google, it would be very surprising if Google was not working on a viable successor. It's as if Sony didn't have a successor for the PS4 in the pipeline, and just expected it to sell forever, with minor patches here and there.
> "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…
Have you not seen their Opinion Rewards app for Android? They do precisely that.
"One person who has spoken to Fuchsia staff described the effort simply: "It’s a senior-engineer retention project." This has been my therory for a while. You see all these different projects competing against each other (multiple messaging apps are a good example) and you think: why is Google so unfocused? But what Google basically wants to do is hoard engineers so they don't leave and go work for competitors and ma…
I think Google's self-competition is something they are doing strategically. If you look at the industry as a whole products wax and wane based on market trends. Market leading products often struggle to innovate under the weight of their own success and are eventually replaced by a new innovator that's doing something right. Google, by virtue of creating many different types of products in one category somewhat insu…
I know of several other prominent examples, but can't mention by name because I'd be breaking an NDA.
Also, Fuchsia is a successor, not a competing project, strictly speaking. It would be the "gauntlet" scenario if Google was running multiple ongoing projects all competing to "inherit" Android (which quite possible it does...)
> "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.…
There is a ton of cruft in the APIs, like any large project would have.
One of the engineer in the Android framework team described creating APIs as generating future regrets.
Some of the mistakes are pretty small. Like internally the system reuse drawable instances in order to save memory, but instead of making this process entirely automatic, before calling let's say `setTint(color)`, you need to call `mutate()` so the UI framework spins a copy of the drawable for you. it would have been easy to integrate this behavior by default without having you know about mutate but since it was done differently, this behavior has been preserved in order to do not break retrocompatibility.
There are many small API issues like this. Big issues of course are corrected but often preserve the old behavior in case you are targetting an old version of the OS.
The View system is incredibly complex. Some of it is due to the inherent complexity of the problem, but some of it is due to the constraints of the time and some decisions that could have been better.
So there are many things you can improve by restarting from scratch and it is often easier than having to deal with the legacy APIs too.
So quietly that they pitched a story about it to Bloomberg.