MeeGo 1.2 Released
jrepin sends word that the Meego project has announced the release of version 1.2:
"This release provides a solid baseline for device vendors and developers to start creating software for various device categories on Intel Atom and ARMv7 architectures. This release also includes the following: Netbook UX, In-Vehicle Infotainment (IVI) UX, Tablet Developer Preview and MeeGo SDK."
Does this allow me to use Meatloaf's scheduling libraries? The guys music sucks but he is a wizard when it comes to writing API's for low level hardware control.
With sadness we note that this will probably be the last release of a doomed (Microsoft killed) project.
I'm being sarcastic, of course.
Why they are focusing on netbook/tablet/tablet-buried-in-a-dashboard variants?
I am a little confused. I have a netbook with version 1.4. Have they decided to just call all versions 1.2 or just the core, especially since the netbook page no longer lists 1.4 updates?
I really liked MeeGo's interface on my netbook but the styling is kind of childish. The other downside is the lack of applications offered and 3rd party audio support.
[J]
As a former Intel employee, I can assure you that the ground-level people at Intel think MeeGo is a fair target for any and all off-campus, lunchtime humor.
I'm sure that all three people who still care about MeeGo were really excited about this.
Intel would be silly to 'step up'.
Progress was slow even with Nokia giving it their full backing, but with Nokia effectively dropping it, this thing is dead as a mainstream, competitive smartphone OS.
Don't get me wrong - I was it weren't true. I wrote code for the original Nokia 770 and its successors would have preferred to see Maemo (or Meego) succeed instead of Android, but I've moved on and am now using Android and so should Intel.
And, speaking as someone who cares about the success and health of Linux, open-source, and the many other forms of openness, I guess I shouldn't be picky. Android might not be everything that Maemo was in those regards, but it is still most of those things that I care about. And when you look at alternatives like iOS and the BB OS, the differences between Maemo and Android seem absolutely tiny.
So, instead of lamenting the slow death of Maemo, we should probably be celebrating the fact that this truly is the year of Linux on the client (a.k.a. desktop), as demonstrated by the figures released yesterday for worldwide unit smartphone sales in 2011 Q1 which showed Android with a decisive lead of 36% compared to iOS and BB at 17% and 13%.
Subj: Molo drops Empoor support on Ekkienong Doodad
by Jacques Chester (151652) on Thursday February 19 2009, @10:48AM (#26916357)
In a shocking twist, Mknnnr was also found to have backstabbed Hoolihooli in a deal with Farnanook.
In unrelated news, it has been found that 98% of "Web 2.0" business names are created by cats walking on keyboards. Footage at 11.
It's also a barrel of monkeys when the summary not only doesn't tell you what the thing is for, *at all*, but also doesn't even give you a link to their web site or Wikipedia or anything. Time to bring up the old Google...
Unity? Screw that: XFCE. Slashdot Beta? Screw that: SoylentNews. Australis? Screw that: Pale Moon. UX developers DIAF
Yeah, nothing quite as awesome as adopting a platform wholly controlled by another company.
Isolated, insular, and unhelpful to the greater open source community?
But on a moment's notice, everything but a handful of packages in Android could be closed up as tight as iOS whereas MeeGo cannot.
I see people virtually cheering for some terrible fate to befall MeeGo, in favor of an OS that absorbs effort from outside but benefits no one but Google and can be closed up tight on a whim (with actions to show they can and are willing to!)
Comment removed based on user account deletion
http://www.youtube.com/watch?v=d8Tiua4BNQo
This is running MeeGo, and we were able to confirm the screen is 720p and has a 12MP camera. So, that's pretty exciting...
AMD has pledged the contribution of its "engineering expertise" to the further advancement of the open source OS.
http://www.engadget.com/2010/11/15/amd-will-contribute-engineering-expertise-to-meego-development/
http://en.wikipedia.org/wiki/Mi-go
>^_^< I can't help but smile when people choose names that are already associated with something else, even if they vary the spelling. (When the Teabaggers hit the new a few years ago I roflmao'd till I turned blue!) You know folks, you can Google this stuff before you publicize your chosen names...
This was a gambit by them to promote the use of Atom and try to get some leverage in the mobile OS market. Without Nokia they have no horse in this race and no reason to continue supporting Meego...
Perhaps you haven't been paying attention to what Intel's been saying. I'm not sure they'll be successful, but if continued work on Meego is part of their plan, I'm glad to see them try.
>Yeah, nothing quite as awesome as adopting a platform wholly controlled by another company.
And what's to stop Intel or Nokia from changing the license for future releases?
>Isolated, insular, and unhelpful to the greater open source community?
And yet Android has more open source activity from the open source community than Meego.
>But on a moment's notice, everything but a handful of packages in Android could be closed up as tight as iOS whereas MeeGo cannot.
Once again, they could easily switch the license for future versions and close it up on a whim.
>I see people virtually cheering for some terrible fate to befall MeeGo, in favor of an OS that absorbs effort from outside but benefits no one but Google and can be closed up tight on a whim >(with actions to show they can and are willing to!)
Absorbs effort from the outside? Really? It seems your issues are with Google and Android rather than furthering the movement of open source mobile operating systems. Try not to blame the popularity of Android for steamrolling your platform of choice. I suggest you direct your frustration to the company that recently 'partnered' with Nokia for the slow demise of Meego.
At least from a developer perspective, Android seems a lot closer to BB OS than Maemo/MeeGo. It uses a bytecode interpreter, a non-X GUI, and a Java SDK with libraries that are highly reminiscent of J2ME.
On the other hand, Maemo doesn't look deader now than it has at any time over the last five years - a new device (the N950) is coming out with a new Maemo version, Maemo 6. I'm cautiously optimistic that it will continue to fill the power-user niche that it does now.
The GPL? Virtually all of the software is under GPLv2, barring a few non-critical bits.
Well yes, when you hype it up, throw money at it, and convince people that you are the open mobile OS (but only for mobile handset vendors and carriers) then you'll get attention.
Repeating a point made in ignorance doesn't make it true.
I am concerned with the movement of open source mobile OSes, and Android is completely detached from everything that exists already. On top of that, it's held almost entirely by Google who have show no hesitation to close the source when they saw it fit.
But hey, rant with more bad information more.
Agree that Intel have little incentive now. Before it made sense to hedge their bets when the OS of their main partner Microsoft had been a dismal failure and one of the largest mobile handset manufacturers in the world had thrown their weight behind Meego. Even at the risk of raising the ire of one of their best partners in the previous couple of decades, the volume of Nokia sales was too hard to ignore.
Now with the only mobile manufacturer committed to MeeGo paid off to kill it, why would Intel continue? They don't make phones. They certainly aren't a software company set up to compete with Google and its Android OS. The fastest rising star in mobile phones Samsung is committed to Bada and Android. Blackberry have committed to QNX.
Seems pretty dead to me. Shame as I wanted one.
Phillip.
Property for sale in Nice, France
"Maemo doesn't look deader now than it has at any time over the last five years"
You must have been living under a rock.
It uses a bytecode interpreter
JIT compiler, since 2.2.
And, of course, native SDK is available since 1.5. These days they even provide handy C wrappers for UI-related Java stuff, so you can really and truly write the whole thing in native code, including event handler entrypoints.
a Java SDK with libraries that are highly reminiscent of J2ME.
I wouldn't say that Android libraries are reminiscent of J2ME, to be honest, aside from the fact that they're also written in Java.
Are you sure about the N950 having Maemo 6? Everything I've read said that Maemo 6 became MeeGo and that any new devices will be running that.
But on a moment's notice, everything but a handful of packages in Android could be closed up as tight as iOS whereas MeeGo cannot.
The core os uses the licenses of upstream projects (which aren't all copyleft licenses) and UX components are generally permissive OSS licenses.
In any case the idea that it couldn't be 'closed up' is silly anyway, in both projects the open source code exists, if either project turned to proprietary replacements for those open components (be it different software or a proprietary fork) it's likely development of those open components would continue via OSS forks anyway.
Android might not be everything that Maemo was in those regards, but it is still most of those things that I care about.
Isolated, insular, and unhelpful to the greater open source community?
functional, available, working, usable...all the things meego isn't.