3 ms·
I think the cause of this phenomenon is that most HN readers are not qualified to comment on Fuchsia, are ignorant of any and all facts about it, but are also c
by jeffbee 5y ago
I think the cause of this phenomenon is that most HN readers are not qualified to comment on Fuchsia, are ignorant of any and all facts about it, but are also compelled to comment. So you get this thread, and most threads here. Actual technical exchange between people who are both not obviously wrong is rare here.
- rejectedandsad 5y agoGooglers thinking non-Googlers are unqualified to comment on anything seems like a fairly common theme to me. I really wonder what caused this kind of ideological entitlement. Was it a company culture that never said "no"? Was it the constant talk of how Googlers are just smarter and more brilliant than everyone else? Genuinely curious.
- lacksconfidence 5y agoIt was the part where people decided to ignore what was actually being presented, and instead derailed every possible conversation about google into their predetermined track. Not you specifically, but this entire fuschia thread. What is someone to think when every time their work is presented publicly the comments are all completed unrelated to what was presented? You too would conclude that group is unlikely to present meaningful feedback or thoughts. (I have never, and will never, work for google).
- rejectedandsad 5y agoI agree, actually, but that's fundamentally different from saying people aren't "qualified".
- KozmoNau7 5y agoPerhaps it would useful for Google and googlers to "read the room" - as it were - and consider why a lot of people have such strong reactions to Google's conduct and methods, why a lot of people are distrustful of anything that comes out of Google (and FAANG in general), and why the reactions are so strong from privacy advocates and the open source/free software crowd in particular, in context of where and how Google started and where it is now.
- lacksconfidence 5y agoI'm not sure what you are suggesting here. Should the developers that work on specific input methods for fuscia be "reading the room" and instead spend their time switching to work on ad tech, where they can influence it? Google has 10's of thousands of engineers, wedging ad tech discussions into the output of every last one of them seems completely and utterly unrelated to the article.
- KozmoNau7 5y agoI would humbly suggest that people working for companies that have become notorious for customer-unfriendly behavior and a complete disregard for privacy, reconsider whether that is something they wish to continue to contribute to, or not. Do they wish to contribute to the coffers of a company that will use every possible means available to erode privacy, to extract maximum value from open source without giving one iota back, and to enforce more and more corporate censorship on the open web. Advertising and a complete disregard for privacy is in every part of Google's DNA, you cannot possibly claim ignorance of it, simply because you are in a department not directly working on advertising. That is equivalent to covering your ears with your hands and going "la la la I can't hear you". That is why it gets brought up in every discussion about Google, because one bad apple really does spoil the entire bunch, their bad behavior in regards to privacy and a complete lack of customer support taints the entire organization, and everyone who works for Google has sold their respectability for a Silicon Valley paycheck. Everyone who works in tech needs to take a good long hard look in the mirror, and decide for themselves whether they're OK with everything their employer is doing, and if not, perhaps consider why they choose to still work there.
- jeffbee 5y agoWays to become qualified to comment on fuchsia are as simple as using it or reading its source code or docs.
- cpach 5y agoI wouldn’t say rare. But yes, the phenomenon you describe definitely takes place quite a lot.
- thu2111 5y agoI disagree, I think the state of this discussion thread is about what should be expected given what Fuchsia is and how the project is run. Firstly, there is little technical discussion of Fuchsia here because there's actually very little to discuss. Fuchsia is, design wise, a pretty ordinary operating system differentiated from Linux mostly by using a microkernel. If you've ever looked at SEL4 then you've got the gist of what's going on here. I'm not aware of any obvious ways Zircon differs from any other microkernel design. Like all such systems it has an inter-component RPC layer (called FIDL) which if you've ever used the Android Binder will look familiar. And it's got a component system. In some ways these upper layers are reminiscent of COM and the whole OS has a bit of a Windows NT 3.1 architectural vibe. That's about all there is to say on the matter. Fuschia is an oddly unambitious platform. Here's a representative quote from the docs: "There is no concept of inter-package dependencies because transitive dependency closures have unbounded resolution time" This statement is technically correct but practically incorrect: when users complain about dependency resolving package managers, they are complaining about out of date packages, broken dependency graphs, centralized repositories and other things. The fact that dependency resolution can be NP-complete in artificially constructed worst case scenarios never comes up because in the real world, dependency resolution takes a few seconds and the problems surface elsewhere. But they found an excuse to avoid doing anything hard or new in the world of software distribution, so they took it. Elsewhere people promote its ABI stability compared to Linux. Maybe, but this is Google we're talking about. Constantly obsoleting stuff is literally built into their incentive structures, so we should double check that right? https://fuchsia.dev/s/results?q=deprecated https://fuchsia.dev/s/results?q=deprecated 120 results for deprecated already! Nobody even uses this OS yet and they already changed their mind about APIs all over the place. The same lack of ambition is visible if we look at the Architectural Principles section of their site. Their principles are: "Secure, Updatable, Inclusive, Pragmatic". That's it. "Secure because capabilities" is a very old discussion with not much to add, and the rest is vague or just not that interesting. Those principles brings us to the final reason the HN discussion is so lacking in technical depth. The OP complains that the discussion here is all about politics and wonders in jest if there's a social justice forum where they might find technical discussion of the project. Amusingly the OP's wish is easily satisfied by the Fuschia website itself. Fuschia is by far and away the most ideologically biased operating system project you will have ever had the misfortune to encounter. It is something the world has never seen before, an entire operating system controlled by the hard left. Every single page in the docs has a giant banner across the top saying "Google is committed to advancing racial equity for Black communities". Note the demand for equity, not equal opportunity. Classical liberalism is dead here, tokenism is in. Of only 4 so-called architectural principles one of them is "Inclusive". They make a brave effort to pretend this is actually about technology by claiming that being just a microkernel+RPC is inclusive because they don't provide any language runtimes for the users (i.e. spinning missing features as a form of moral purity). Then it all falls apart and they go back to talking reducing harm and bias via language control - another tenet of hard left thinking. So let's imagine we're looking for something better, fresher, bolder than Linux, macOS or Windows. We look at Fuschia. What we see is an extremely conservative OS design in which the most modern ideas in it pre-date Linux itself. We see an overwhelmingly political project, run by a company that has in the last year been systematically erasing from its platform crazy wack-jobs like, er, doctors and professors simply because they disagreed with the WHO. And we see that there's no discussion, anywhere, of any features that end users might actually care about. That's why there's no discussion of technology in this thread.