View Single Post
Posts: 515 | Thanked: 259 times | Joined on Jan 2010
#343
Originally Posted by mikecomputing View Post
it is questionable cause some people her seens to not know what Meego really is.
I'm sure there are many here who do.

I mean it is ok to brand Meego it could have closed components?
This is standard industry practice. We see this with Android. I see no reason this wouldn't continue.

what libs is not compliant? where does Nokia break compliaance? I know only one and thats packagemanager. But seems there is alot of experts in this forum who says it breaks more but none of them have actuallhy showed me any proof.
I'm not a software developer and I don't work for Nokia but I know one thing there will be components that are non-compliant. You know why? That's the way software works. I've seen enough software development to know that it is nearly impossible to not break compliance, especially because MeeGo is a moving target.

What does that mean? Between MeeGo Harmattan and MeeGo proper there will be changes required to get everything to work right. Will be minimal? I don't know I hope so. Is it a big deal? It's life in the software world. Show me an OS that has perfect forward and backward compatibility and I'll show you an OS that takes 3 to 4 years to release and still will not be 100% perfect.


Personally I dont know if apps installed on XX device must be allowed to work on Meego core to be Meego compliant I doubt so cause different devices has different HW.
I think people should expect that the first release or two of MeeGo won't be perfect. It'll get better, just might be a tricky first few months. Manage expectations and people won't mind the hassle. Promise / claim something that is impossible and people will whine / complain the whole time.