Well Tizen's openness is a lie too, at least in wearables. Both Gear S & Gear 2 are already depreciated by Samsung, and the wearable image you can build yourself from source is missing most key components you would use on a watch (for example, you won't have S Health is closed source, Nokia maps -included in Gear S- is closed source too), and even the sensor framework is unusable in an opensource form, since half of the apis are closed and undocumented (you can check all this by taking a look at the srpms from build.tizen.org)
Even if you could overcome that, you would still need to make your own companion app for the phone and framework, since all that is Samsung proprietary too.
That's exactly why I'm the sole mantainer of Gear 2 & Gear S Android Wear ports...
IMHO it would be easier to clean up AOSP and make an open variant of Android Wear, rather than reimplement it all from scratch, but who doesn't like a challenge! At least they can use some parts of Nemo/Sailfish OS
Tizen's openness is also a lie for phones. Just like AOSP, community involvement is not welcome in the Tizen development process and doesn't have any role in deciding what ships on phones.
Are you advocating an OS from the guys that are worse than Apple, closed as much as possible? The "CM cannot support us", "If you flash anything, we blow a fuse", "Crapware is good for you" Samsung?
Granted, I haven't tried Tizen. But I AM using a Samsung device at the moment and let me state it as clear as possible: Samsung is the worst, the absolute worst, phone manufacturer in my frequently changing usage. I wouldn't trust Samsung with anything.
Incidentally I've been at a Samsung HQ (not phone related, printers) a while back and the manager in charge stated something like "We're great at hardware, we suck at support". I had a hard time keeping a straight face.
Honestly: There's no phone company that is worse than Samsung. I am not convinced that Tizen can fix that.
(I have a S6E right now and I constantly want to throw it against various obstacles)
The poster I was replying to was working on an embedded device, and they would like a system that's similar to Android but more like regular Linux. Tizen is that system.
Samsung's policies on their devices have nothing to do with how another company might deploy Tizen.
I'd argue that Maemo/Meego were that system, but I already admitted to know really not a lot about Tizen.
You might be perfectly correct. I wouldn't want to touch anything (Software. Hardware is a different story) made by Samsung with a 10 foot pole and cannot imagine that Samsung would be great as upstream, however you plan to deploy the software.
Again, apologies. My beef is with every piece of Software Samsung published around me, not with you, your opinion or Tizen. I'm extrapolating and generalizing and obviously have a gripe here..
"Popular reputation" means "how it's commonly perceived".
I'm not saying Tizen is popular; on the contrary, I was trying to say that it has a reputation as a pointless also-ran Android clone. But past that prejudice, it's actually a competent Linux platform for embedded systems.
Even if you could overcome that, you would still need to make your own companion app for the phone and framework, since all that is Samsung proprietary too.
That's exactly why I'm the sole mantainer of Gear 2 & Gear S Android Wear ports...
IMHO it would be easier to clean up AOSP and make an open variant of Android Wear, rather than reimplement it all from scratch, but who doesn't like a challenge! At least they can use some parts of Nemo/Sailfish OS