3 ms·
Whether it was Android, Microsoft, or slowly dying, people working there would be affected, so I'm not sure the choice of Microsoft changes things too much from
by davidw 16y ago
Whether it was Android, Microsoft, or slowly dying, people working there would be affected, so I'm not sure the choice of Microsoft changes things too much from that point of view. With Android, perhaps they could have kept more people on board to hack on it and customize it, but still, the axe was going to fall.
Should be interesting to see how this is handled in Finland. Stock is down, layoffs, and some "arrogant foreigner" in charge would be a recipe for even more change in some places.
- rbanffy 16y agoAndroid could be built/merged with MeeGo. They have the same kernel and all hardware-specific work would be reused. Both userlands could run side by side.
- zokier 16y agoI don't think you realize how different Android and MeeGo (or atleast Maemo) are. They aren't running the same kernel and their userland is completely different. The fact that both have bits of linux inside doesn't really make them alike. It probably would be easier to port Qt for WP7 than integrate Android on top of MeeGo.
- rbanffy 16y agoIt cannot be that hard. If Linux, MeeGo and Android kernels diverged too much, maybe it's time to unify them in a way they all can share the maximum amount of code and effort. I agree porting Qt to WP7 shouldn't be much of a problem too, or a much larger one. But I suspect that Nokia's plan may prove hard to follow because it will be very hard to convince people to use WP7 phones.
- darklajid 16y agoThat's still missing the point and exactly what _Android_ not did. While MeeGo is quite close to your standard "Linux on the Desktop" (Sorry, was hard to resist), Google suffered from a lot of NIH based design decisions. On the other hand they probably chose the easier route for themselves (instead of solving their problems in a codebase that's outside of their control) by creating things from scratch although "standard" alternatives were available. In short: I'd say it probably _is_ hard and I'd even go so far as to say that MeeGo moving into Android would be pointless. For code and effort sharing maemo/MeeGo was the better stack.
- alf 16y agoSomething tells me Google would have been very happy to help Nokia add the Dalvik VM to MeeGo. Nokia would get Android apps and developers, while still being able to diversify their OS and and UI from the competition. Google would get Dalvik as the dominant development platform in mobile.
- sjs 16y agoNokia had been moving towards an open-source culture. Those are the types they've attracted the last several years. This is a very radical departure from their previous path.
- davidw 16y agoSure, I think Android is in some ways closer and more interoperable, but still... people were likely to go in any case.
- spiffworks 16y agoYou should've seen Ryan Paul's twitter feed today. It was brutal watching his love for Meego break down into cynical snark for Nokia.
- leon_ 16y agoYup, I started liking Nokia again because of their Maemo/Meego engagement. I'm an iOS developer but in private I use a Maemo phone (the N900) which fulfills my geek needs. I hoped for a cool N900 successor with a cap. touch screen and a little more power but ... well ... I guess Nokia will make something half assed. Meego phones (which run a real linux - not closed bullshit like android) would have been an awesome alternative to iOS and Android. At least for the more geeky consumer. :/ Good bye, Nokia.
- berntb 16y agoHear hear. An open O/S for my phone named the same as a Lovecraftian monster... I was starting to read the Qt docs, Gnome/Mac user and all. :-(
- joezydeco 16y agoKnowing a little Qt isn't a bad thing, and it's kind of fun to prototype stuff on a desktop and have it run in an embedded environment with a quick recompile.