31–40 of 175 posts
But from the linked page I couldn't figure out where any of the documentation of this "thing" is, nor how to install it, nor what platforms it's for.
Was it just me?
Written in C. What a shame. edit: Thank you to all of the repliers, I had no idea that most OSes were written in C. Er, actually, I'm more than well aware of that fact and I'm familiar with the number of CVEs that have occurred over the years because of the lack of memory safety involved in that C code. Sorry, I simply don't get the appeal of writing more operating systems and network-exposed code that isn't written…
I remember a post earlier today about how open source projects needed better marketing. prime example. I had to dive in to know what was the project all about...
I consider myself fairly tech savvy, and have done a little programming here and there. But from the linked page I couldn't figure out where any of the documentation of this "thing" is, nor how to install it, nor what platforms it's for. Was it just me?
https://fuchsia.googlesource.com/manifest/+/master/README.md
It runs on arm, arm64, and x64.
> It is good alternative to commercial offerings like FreeRTOS [1] FreeRTOS is GPL with an exception for static linking making it effectively free if you make no modifications. There is, however, an onerous clause prohibiting the publication of comparative benchmarks. [2] [1] https://fuchsia.googlesource.com/magenta/+/HEAD/docs/mg_and_... [2] http://www.freertos.org/license.txt
If it's GPL the source is effectively mine to do what I like.
I could make a trivial change to the source (or not perhaps), and call the result a FreeRTOS derivative and publish my derivative's benchmarks.
> It is good alternative to commercial offerings like FreeRTOS [1] FreeRTOS is GPL with an exception for static linking making it effectively free if you make no modifications. There is, however, an onerous clause prohibiting the publication of comparative benchmarks. [2] [1] https://fuchsia.googlesource.com/magenta/+/HEAD/docs/mg_and_... [2] http://www.freertos.org/license.txt
There doesn't seem to be much point to that benchmark clause. If it's GPL the source is effectively mine to do what I like. I could make a trivial change to the source (or not perhaps), and call the result a FreeRTOS derivative and publish my derivative's benchmarks.
I think that added restriction actually makes it GPL incompatible, and disqualifies it from being an actual open source license.
Written in C. What a shame. edit: Thank you to all of the repliers, I had no idea that most OSes were written in C. Er, actually, I'm more than well aware of that fact and I'm familiar with the number of CVEs that have occurred over the years because of the lack of memory safety involved in that C code. Sorry, I simply don't get the appeal of writing more operating systems and network-exposed code that isn't written…
It sounds like it's trying to be a RTOS for phones and modern hardware. But I know there has to be more to it than that.
Pink [1] and Purple [2] were both Apple codenames for operating systems. Probably not a coincidence, but I don't see an obvious connection...
[1] https://en.wikipedia.org/wiki/Taligent#Pink_and_Blue
[2] http://www.phonearena.com/news/Did-you-know-that-the-codenam...