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."
All Linux distros can potentially run on ARM ...
I'm a minority race. Save your vitriol for white people.
MeeGo is supposed to be the result of merging Maemo and Moblin
Who named these platforms, a Lord of the Rings fan with a speech impediment?
Q Will MeeGo use .rpm or .deb as its packaging system? .rpm format
A: MeeGo will use the
http://meego.com/about/faq
Also Quim Gil of Maemo stated that it will officially support both GTK+ and Qt (original plan for Maemo 6 was to officially support only Qt and deliver GTK+ via community supported packages)
http://talk.maemo.org/showpost.php?p=527251&postcount=87
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.
Still better than the other way around:
Maggot.
The mobile OS from Yugo. ^^
Any sufficiently advanced intelligence is indistinguishable from stupidity.
No that's not it.
It's really a problem? I mean, package wars are so 1999. I recently switched to a RPM based distro after 9 years using and loving APT. And while there're differences (some advantages, some disadvantages), these days they're pretty much the same thing. I'm using KDE 4.4 from Fedora rawhide in my Fedora 13 base system, just as I would have done in Ubuntu. There're things far more important in this merge than using RPM instead of DEB. Like, for example, focusing on QT instead of Clutter.
Both Maemo and Moblin started off Gtk-based, using the Clutter toolkit on top of Gtk. Now both have switched over to Qt. Are there any other serious users of Clutter left?
I hear lots of projects starting with or switching to Qt these days, and none that switch to or start with Gtk. Having programmed in both Gtk and Qt, I have to say I understand why. Qt is hands down the better and more elegant toolkit, despite my preference for C over C++. Qt also makes it easier than Gtk to port between Linux, Mac and Windows. Gtk on the other hand is stuck with a horrible dependency hell that prevents using it for anything serious on non-Linux platforms.
I think the way forward for Linux on the desktop is to standardize on one GUI toolkit, and there is no doubt that this toolkit would have to be Qt. It is a bit sad, because I always like Gnome better than KDE, and I see no easy way for Gnome to convert over to Qt.
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 ...
I was recently worried they'd both wither on the vine trying to compete against Android and filling almost exactly the same space. Thus I was thinking I'd have to base a project on ChromeOS, which seemed strategically foolish (at least Nokia and Intel will have divergent interests to keep development focused on solving problems well in the abstract, rather than quick-n-dirty tangents a single vendor can accept).
Especially if they stay with the mainline kernel, which Google isn't interested in doing, together Intel and Nokia are going to be much more successful than competing poorly against each other and Google.
So, here's one developer's intent to go this way rather than Android (for a non-phone project). Congrats to the adults in both camps.
My God, it's Full of Source!
OUTSIDE_IP=$(dig +short my.ip @outsideip.net)
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.