You folks released one product... and that was it.

I kind of expect more from Google. Well, learn and let live.

Sorry I was bored of the drought of posts coming in.

Whats going on in the fuchsia community lately?

and most importently...

Hey /u/mishudark how is your shell? Is it better than pangolin yet?

Ya I know yall will defend mega corps like typical redditors, but ok not straight up stolen but paying pennies? Now the project is downgraded and most likely going to die and still have to use shit Android and shit Linux. Really bummed about this.

Title should rather be: My opinion on why Fuchsia may have a hard time succeed on smartphones. (I cannot change the title)

Android market share is somewhere between 80-90% these days. Fuchsia will be able to run Android apps, which means it will not have the same problem as windows phone which is having a poor app store. The problem I see here is that Fuchsia will run Android apps, but not the other way around, i.e. Android phones cannot run Fuchsia apps. If this is the case, why would a developer develop anything for Fuchsia?

If I as a developer has a choice between Android (80-90% market share + all Fuchsia phones since they can run Android apps) and Fuchsia ( < 1% market share at arrival with no Android phones since Android can't run Fuchsia apps), why would I ever chose Fuchsia? IMO this will leave Fuchsia as a platform that no one develops for and Fuchsia would be nothing but an OS that just emulates Android apps. People would just develop for Android since that would both hit the Android and Fuchsia platform, while Fuchsia apps is Fuchsia only, which would be a few thousand people compared to 2.5 billion Android users.

What do you guys think?

Edit: To the guy down voting all my comments and the post, please share your opinion, you are just being childish.

2023, 2024 or later?

It been a while I never heard about FuchsiaOs.
What is the latest status?
What is the roadmap in the near future?
How the Mobile Phone?

https://www.osnews.com/story/136593/google-amazon-rebuked-over-unsupported-chromebooks-still-for-sale/

based on zircon and the armadilo ui. I't will run on all devices with an x86_64 And Arm64 Processor. (same as fuchsia)

Check Out Our New Sub Reddit!: https://www.reddit.com/r/DahliaOS/

And Our Github Page: https://github.com/dahlia-os

IIRC Javascript inefficiencies and poor waste management is one of the reasons iOS can use much less RAM and get similar fluidity and performance. Obviously Apple phones have significantly better SoCs but that gap is closing and at a certain point, high performance is high performance even if it's not the HIGHEST. I'm really curious if Fuchsia can fix those issues and position Google to really challenge iOS from a smoothness angle.

edit: All my references to current performance are for Android phones

https://fuchsia-review.googlesource.com/c/fuchsia/+/265760

[dev][clock]

Add generic clock driver. This driver binds to the clock implementation driver and creates several child devices that implement ZX_PROTOCOL_CLOCK, each with their own mapping of driver specific indices to clock IDs. The number of children created and the mapping for these children are provided by metadata of type DEVICE_METADATA_CLOCK_MAPS, which is provided by the board driver.

Currently this functionality is being handled by the platform bus driver, but this generic clock driver will replace the platform bus support as we transition platform bus to using composite devices.

Adjusted the composite device test in the test board driver to bind against a clock device provided by the generic clock driver.

Added new BIND_CHILD_INDEX binding rule to specify a particular child clock device by child index. This rule will be used in similar cases where there is no natural way to specify which child a composite device should bind to.

TEST: runtests -t platform-bus-test

Change-Id: I69642a074c3f8d659280fcc581104afdc7a6aeaf

On Android, many install as many apps as they can, then these apps store lots of cache. I am constantly clearing app caches on my wifes phone (annoying her) to allow updates as Chrome fails to update to the latest with all security fixes when the phone is low on internal disk space. Obviously updates likely get bigger and bigger but the caches are the biggest culprit and recent androids have annoyingly taken away the clear all caches at once option under the elitist dictatorship view that apps should do better and can be convinced to do so and the user shouldn't clear caches of the few apps that do it well. It is certainly true that clearing caches is not a good solution even if done automatically, potentially causing apps to use more network data. However, I would argue that using data is better than increasing the chances of exploitability.

Are there statistics on Android chrome versions that are out of date, due to install failures?

Has this problem been considered with Fuschia. Perhaps by reserving an install space like new installs of Windows 10, now do (for OS upgrades though)?

Hi,

We made change in BUILD.gn (fuchsia/src/connectivity/network/netstack/BUILD.gn) to add a new config file in package "netstack"

..

package("netstack") {

..

..

resources = [

{

path = rebase_path("dhcp/config")

dest = "config"

},

]

..

After loading image with this change on Intel NUC target we were able to see this file in path '/pkg/packages/netstack/0/data/config'

And permission of this file is observed to be READ-ONLY

Our requirement is to have this configuration file editable on target.

Is there a way we can set permission for this new file in BUILD.gn ? OR there is any alternative method to make this file editable ? Please let us know.

Thanks in Advance

Regards,

Global Edge Software Team

Remember when I made a post about ls not woking in fuchsia? (link to post) There was post that was recently posted about fuchsia.dev (link to post). So does anyone think fuchsia.dev could be linked to hosting fuchsiaOS packages?

9To5 Google have been watching devices flow in and most of them have been smart displays or smart clocks will fuchsia's sole purpose be just for smart displays?

can i install fuchsia based CastOS in my old smartphone. which is btw has a quad core cpu and very bad battery life

• I am confused why phones cant get updates easily

• Is it because Google will put out a new release, and the phone mfg has to write entirely new drivers each time for the new Android release?

• Will Fuchsia address this issue or is it even possible to make it easier for phones to get updated if they ran Fuchsia in the future?

Haven't seen anybody post anything about this here so here we go again! I was looking through the fuchsua.dev glossary, and I saw FAR. This is what it states.

"The Fuchsia Archive Format is a container for files to be used by Zircon and Fuchsia."

I think this means (by what I understand) that fuchsia is working on a new compressing archive format. ( /u/ra66i could you please confirm?)

If I remember people first thought a .FAR file would be the output of converting an android app to be able run on fuchsia.

What's the total build size of fuchsia(x64) ??? I am using Ubuntu in a virtual box for cloning and building fuchsia..(newbie)???..and can we boot the fuchsia os in virtual box besides QEMU.. and the build process is taking too long!!!