Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

First Rule of Google Fuchsia OS Is to Not to Talk About It

fuchsiatalks.com

Post reply on HN
Print view View original

41–50 of 58 posts

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#41

Post by posixplz »

johansch wrote: post #38
spun wrote: post #19

Earlier quoted context omitted.

I had the same experience at Amazon with their secret projects, including each iteration of their kindle fires

Yeah, every company kinda does this. It seems like most of the the time it's a combination of: a) we have no idea if this is unique or not (hint: a Kindle Fire revision probably isn't) b) it makes things seem more exciting. The weird thing about Fuchsia is that all of the development is done in the open, but noone wants to give any context.

Well if the company is publicly traded, secrecy of internal matters is a legal requirement and contingency of employment.

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#42

Post by drewg123 »

rckclmbr wrote: post #23
drewg123 wrote: post #16

The first rule of almost any project at Google is not to talk about it. It the only job I've ever had where I could not tell my wife anything about my work, aside from how lunch was. My wife joked that Google was almost as paranoid as the DoD or NSA, and thought it was very presumptuous of them to force so much secrecy.

Have you worked at any other public company? It's pretty common to not share private company information...

There's private, and there's Google.. I work at Netflix now, and we are quite open in my area. Eg, I can tell my wife what I'm working on, ask her to proof-read my presentations, show her the office, etc.

Before Google, I worked for a privately held company, and it was quite a bit more open as well.

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#43

Post by johansch »

posixplz wrote: post #41
johansch wrote: post #38

Earlier quoted context omitted.

Yeah, every company kinda does this. It seems like most of the the time it's a combination of: a) we have no idea if this is unique or not (hint: a Kindle Fire revision probably isn't) b) it makes things seem more exciting. The weird thing about Fuchsia is that all of the development is done in the open, but noone wants to give any context.

Well if the company is publicly traded, secrecy of internal matters is a legal requirement and contingency of employment.

By default, certainly.

Btw: In February I spent some time looking at the then about 100 committers to Fuchsia/Flutter. Some quite impressive names. I think Fuchsia is a really serious effort in the Chrome team.

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#44

Post by tyingq »

theDoug wrote: post #14
Ajedi32 wrote: post #2

Not really any new information here. It's fun to speculate about what Fuchsia might become, but it's pretty clear Google's not ready to announce anything yet. The only reason we even know it exists is because they made the source code public.

Exactly this. And So fun to speculate on something far from its likely end goal or release state, because _only_ of who made it public. A lot of cooks in the opinion kitchen looking out the window at wheat growing, pretending it’s already a baked cake, and of which they already dislike the taste. (Disclosure: I work at Google, not on this.)

Of course, they chose to bake the cake out in the open, with an air of mystery about the purpose.

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#45

Post by trendia »

ProAm wrote: post #25
CountSessine wrote: post #15

Earlier quoted context omitted.

We all have bad days, but some of this rant is really toxic. Dear god. I looked at the kernel and it's awful Stuff real operating systems have solved decades ago WTF? This is hilarious. Did they decide to reinvent all the wheels badly just because someone at Google was bored? The ex kernel developer in me feels insulted that a serious company would release something this immature So, have they actually released Fusch…

> Did they decide to reinvent all the wheels badly just because someone at Google was bored? This is how projects are born and die at Google. They live until no one is interested in them anymore and they are abandoned.

> They live until no one is interested in them anymore and they are abandoned.

Sometimes they don't even wait until no one is interested!

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#46

Post by mckillop »

swetland wrote: post #8
tyingq wrote: post #3

Saw this rant about Fuchsia on reddit that appears on the surface to make some good points: https://www.reddit.com/r/programming/comments/6a026o/googles... Not my area of expertise for sure though. Any kernel dev types here had a chance to look at Fuchsia? Is the criticism warranted? Update: Fixed link to point at the right comment. Edit: Should have mentioned the tone is a bit over the top. More interested in the ac…

I'd suggest that it's possible we're using simple, but functional placeholder implementations of things so the entire system can boot and run, and then various parts of it can be worked on at various paces, in parallel, etc. Lot of moving parts in a kernel, or OS, and one could try to write all of them in their final form first and hope they all work together when done, or one could take a more incremental approach.…

I also encourage anyone that sees something that could be done better to sign up and submit some code!

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#49

Post by bitmapbrother »

tyingq wrote: post #35
bitmapbrother wrote: post #33

Earlier quoted context omitted.

>The ex kernel developer in me He seems to be reciprocating the years of criticisms and verbal abuse given to him by Torvalds.

His comments sound more like he contributed to one of the BSD kernels.

He doesn't really indicate what kernel he worked on. Regardless, Linus knows no kernel boundaries ;)

I'm also surprised that someone, who purports to be knowledgeable on kernel development, was not cognizant of the fact that the code he was looking at was only started 8 months ago and no where near production quality. To start making assumptions on the quality of an OS based on very early code was extremely immature and makes me wonder what exactly his qualifications really are. The primary goal of the Fuchsia team is to try and get something booting up and running and then start to iterate and polish.

Re: First Rule of Google Fuchsia OS Is to Not to Talk About It

#50

Post by tyingq »

mckillop wrote: post #46
swetland wrote: post #8

Earlier quoted context omitted.

I'd suggest that it's possible we're using simple, but functional placeholder implementations of things so the entire system can boot and run, and then various parts of it can be worked on at various paces, in parallel, etc. Lot of moving parts in a kernel, or OS, and one could try to write all of them in their final form first and hope they all work together when done, or one could take a more incremental approach.…

I also encourage anyone that sees something that could be done better to sign up and submit some code!

I suspect some are holding back since there's not been much shared about the end purpose. At the moment there's still speculation as to whether it's for mobile devices, desktops, both, or something else.
Post reply on HN