Slashdot Mirror


Nokia, Intel Merge Maemo, Moblin Into MeeGo

AVee writes "Intel and Nokia just announced a new project called MeeGo. MeeGo is supposed to be the result of merging Maemo and Moblin, bringing together the best pieces of those (already quite similar platforms). Interestingly this means that Intel will be sponsoring a mobile Linux distro which will run on ARM."

3 of 162 comments (clear)

  1. Re:Package management by EvilIdler · · Score: 4, Interesting

    RPM, says Intel. Can't find a link, but there is much gnashing of teeth over that at work here. I would prefer to keep the repository apt, at the very least. But apt+dpkg would be lovely.

  2. Re:There can only be one! by alexandre · · Score: 3, Interesting

    Well, iPhone is doomed to stay as proprietary garbage, as is WinMo 7.
    Now what's left: Android, Meego, Palm, ...

    Those 3 could probably work together... Maybe Android is too full of itself and Samsung should join Meego and drop Bada too.

    The question for all these is who control the app store, and i think meego allows all of them to control their own while still staying compatible.
    This also means open access to an open market of different store for consumers if the platform is to stay open and thus attract people.

    Are we seeing the computer software industry transform into a "Label" that distributes apps?
    I can't understand this model in a world where everyone can setup their own distribution channel for 20$.
    It's only a winning move if you can sell hardware and the only way to compete against the über monopolistic Apple model is this.

    So the cycle of proprietary / FOSS reaction goes on ...

  3. Re:Package management by MoralHazard · · Score: 3, Interesting

    I'll bet you haven't used RPM in-depth since before YUM became the preferred front-end. If you had, you would have already known that rpm:dpkg what yum:apt, and there really isn't much of a difference between the two stacks, at this point.

    It's funny how little some people can be bothered to know about the Linux world outside their own little preferred ecosystems. Last week, I suggested that a co-worker might want use RPMs instead of tarballs to distribute a patched custom LAMP stack to a server farm. Rather than admit that he didn't know anything about writing spec files and couldn't be bothered to learn, he started lecturing me on the evils of "RPM dependency hell".

    In 2050, I'm sure some people who use some kind of Linux on a daily basis will still be spouting these old saws, feebly unaware that everybody is just too polite to whack an old geezer with the clue bat.