61–70 of 126 posts
Earlier quoted context omitted.
C just pushes the complexity onto the programmer without help.
Random subjective opinion presented as objective truth!
isn't?
I'm also not sure why stating my opinion is a problem. If you can't handle someone not bother to pussyfoot around and preface any statement with an "IMO" disclaimer, that seems like your problem.
Earlier quoted context omitted.
Random subjective opinion presented as objective truth!
because > Not OP but the reason I dislike Rust for OS/kernel development is that it's just too damn complicated isn't? I'm also not sure why stating my opinion is a problem. If you can't handle someone not bother to pussyfoot around and preface any statement with an "IMO" disclaimer, that seems like your problem.
I'm conflicted on this. I really do like the idea of a challenger to the linux monoculture (among devs)/the windows monoculture (among consumers), but I really hate the idea of google getting yet more power. If it was pretty much anyone else doing this.
Like Android, this is OSS. Sure, Google runs the core development, but everyone will benefit from this eventually.
Control the platform, control the market around the platform.
Sure it's 'open', but at the same time, heavily subject to the authority of the owners.
See also the systemd/gnome impact to linux ecosystem..
posix in general keeps unices and unix likes (including linux here) more open than other systems since the API is less fluid / under the influence of a single group..
this phenomenon won't occur here.
I'm conflicted on this. I really do like the idea of a challenger to the linux monoculture (among devs)/the windows monoculture (among consumers), but I really hate the idea of google getting yet more power. If it was pretty much anyone else doing this.
How exactly is Google getting power here? The code is totally open. They just seem to be giving themselves more flexibility and potential to build better products. If anything, this will result in less power over the Linux kernel for Google. It seems like that’s something you’d appreciate. (My response to s2g’s reply below because HN is terrible for commenting: I see your point that they now unilaterally control how…
Earlier quoted context omitted.
Why focus on the language and the possibility of a million and one bugs but not the architecture and design choices?
Because it's an easy indicator of someone who has no idea what they're doing in OS development. Choosing the wrong tool for the job is meaningful. Have you ever looked through Chromium's C++ codebase? The same people are working on this and it tells us that they haven't learned their lesson (or they want to tightly integrate Chrome with Fuschia, which is also a foreboding sign). Edit: I should clarify that I think C…
From appearances, the lead "someone" on at least the kernel appears to be Travis Geiselbrecht, who worked at the OS and/or kernel level on BeOS, the Danger Hiptop (Sidekick) OS, his own NewOS (now the basis for HaikuOS), and an embedded OS at Jawbone before joining Google and starting work on LK, which is being used as the basis for Zircon and the Android bootloader.
So I think maybe you mean
> Because it's an easy indicator of someone who does not have the same opinions about OS development than I do.
...because, y'know, that's fine! But "this guy obviously has no idea what he's doing?" Gonna agree to disagree there.
Earlier quoted context omitted.
because > Not OP but the reason I dislike Rust for OS/kernel development is that it's just too damn complicated isn't? I'm also not sure why stating my opinion is a problem. If you can't handle someone not bother to pussyfoot around and preface any statement with an "IMO" disclaimer, that seems like your problem.
Dude lighten up it was a joke :)
Earlier quoted context omitted.
Like Android, this is OSS. Sure, Google runs the core development, but everyone will benefit from this eventually.
Control the API, control the platform. Control the platform, control the market around the platform. Sure it's 'open', but at the same time, heavily subject to the authority of the owners. See also the systemd/gnome impact to linux ecosystem.. posix in general keeps unices and unix likes (including linux here) more open than other systems since the API is less fluid / under the influence of a single group.. this phen…
What is this supposed to become, exactly? Google hasn't said much about it and speculators are making big claims like how this will replace ChromeOS and Android. I don't see that happening any time soon considering how deeply entrenched both OSes are, but Google's dedication mixed with the lack of comments makes me think again.
I'm conflicted on this. I really do like the idea of a challenger to the linux monoculture (among devs)/the windows monoculture (among consumers), but I really hate the idea of google getting yet more power. If it was pretty much anyone else doing this.
How exactly is Google getting power here? The code is totally open. They just seem to be giving themselves more flexibility and potential to build better products. If anything, this will result in less power over the Linux kernel for Google. It seems like that’s something you’d appreciate. (My response to s2g’s reply below because HN is terrible for commenting: I see your point that they now unilaterally control how…