4 ms·

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

tyingq 9y ago
His comments sound more like he contributed to one of the BSD kernels.
- bitmapbrother 9y ago
  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.
  - tyingq 9y ago
    He does, later in the thread... "I just learned by doing. Got annoyed by something being bad in one of the BSDs, found out how to get into their secret chat channel, started whining and got told to shut up and write the code. So I did." And rambles more about why he feels Fuchsia did the wrong thing. Specifically because better implementations of some parts with licenses compatible with Fuchsia existed. Which I suspect is a nod again to BSD. With a more calm tone I think saying that writing your own suboptimal tick timers, or locking strategy, or whatever...versus using something known good, is fair criticism. Not being my space, I wasn't sure if the base criticism was valid. The responses here seem to indicate they are.
    - bitmapbrother 9y ago
      The problem with his criticism is that he seems to think the present decisions the authors have made, for an 8 month old OS, are written in stone. It's like reviewing a car while it's still being assembled at the factory. Fuchsia is probably 2 or more years away from an Alpha release. Things are changing at a rapid pace.
      - tyingq 9y ago
        No, I got that idea. But, for his examples, he mentions existing solutions could have been lifted. If the suboptimal stuff was existing, I take your point. Perhaps it was straight from LK? But writing something new, that has flaws, as a placeholder...when something better exists already, and has a compatible license...that seems fair game to question. Especially if it's something that has tentacles and creates dependencies. Placeholders sometimes don't stay as such.

tyingq 9y ago

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

bitmapbrother 9y ago
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.
- tyingq 9y ago
  He does, later in the thread... "I just learned by doing. Got annoyed by something being bad in one of the BSDs, found out how to get into their secret chat channel, started whining and got told to shut up and write the code. So I did." And rambles more about why he feels Fuchsia did the wrong thing. Specifically because better implementations of some parts with licenses compatible with Fuchsia existed. Which I suspect is a nod again to BSD. With a more calm tone I think saying that writing your own suboptimal tick timers, or locking strategy, or whatever...versus using something known good, is fair criticism. Not being my space, I wasn't sure if the base criticism was valid. The responses here seem to indicate they are.
  - bitmapbrother 9y ago
    The problem with his criticism is that he seems to think the present decisions the authors have made, for an 8 month old OS, are written in stone. It's like reviewing a car while it's still being assembled at the factory. Fuchsia is probably 2 or more years away from an Alpha release. Things are changing at a rapid pace.
    - tyingq 9y ago
      No, I got that idea. But, for his examples, he mentions existing solutions could have been lifted. If the suboptimal stuff was existing, I take your point. Perhaps it was straight from LK? But writing something new, that has flaws, as a placeholder...when something better exists already, and has a compatible license...that seems fair game to question. Especially if it's something that has tentacles and creates dependencies. Placeholders sometimes don't stay as such.