Linked by Moochman on Tue 24th May 2011 21:11 UTC
MeetMeego.org has the dirt on the details of Nokia's next two MeeGo devices [German]. To sum up: the first device, the (very) long-awaited N9, has a similar design to the N900 - a horizontal sliding 4-line keyboard, but this time with a tiltable screen, a 1GHz ARM Cortex A8-based processor, a 12MP camera with Carl Zeiss lens, and HDMI out. It will be a developer device, distributed at developer conferences such as the MeeGo Conference in San Francisco in a couple of days.
Thread beginning with comment 474505
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
Member since:2005-07-08
I agree.
I think the major issue with Symbian was that they never managed to bring the OS API up to date.
PIPS and QT were a nice addition but you still needed to get dirty with Symbian C++ and the horrible toolchain.
This was one of the reasons that many developers jumped to other platforms.
Back in the day I had hopped that when the ABI was broken, the API would be improved. Instead they introduced API level controls with certificates and DRM.
Member since:2005-07-06
The major issue for developers maybe. If Symbian had had a fighting chance of battling the iPhone, it wouldn't have mattered--apps would be developed for it one way or another. But sadly the UI in general--both the frameworks and the OS itself--simply couldn't compare to the iPhone's slickness, so the consumer demand wasn't there, so the developers ignored it....
Member since:2008-09-11
But since Nokia apparently now wants to go "the wow starts now", and get into Microsoft OSs on one side and Linux with lots of GPU-accelerated eye candy on another side, they'll also have to put very fast and power-hungry hardware before things work smoothly, whether they like it or not.
They don't need hardware which is more power hungry than iPhone or the tons of Android phones out there. They need roughly the same hardware.
And I'm sure that Nokia will tailor the hardware and software to be as power savy as it gets. That's why I love my Nokia phones, beside making quality hardware that can be used for years, the battery lasts a lot comparing to other phone brands.
Member since:2010-03-08
"But since Nokia apparently now wants to go "the wow starts now", and get into Microsoft OSs on one side and Linux with lots of GPU-accelerated eye candy on another side, they'll also have to put very fast and power-hungry hardware before things work smoothly, whether they like it or not."
They don't need hardware which is more power hungry than iPhone or the tons of Android phones out there. They need roughly the same hardware.
They don't need hardware which is more power hungry than iPhone or the tons of Android phones out there. They need roughly the same hardware.
This is the kind of hardware which I called very fast and power-hungry. As compared to usual Nokia hardware, I mean, which tends to be a bit underpowered for Symbian already, but also have crazily long battery lives as a compensation.
Eseries used to do their job nicely with only ~350MHz ARMv6 chips at hand, as an example. I don't think this will work anymore if Nokia shift focus on lots of smooth eye candy and want larger, higher-resolution screens.
And I'm sure that Nokia will tailor the hardware and software to be as power savy as it gets. That's why I love my Nokia phones, beside making quality hardware that can be used for years, the battery lasts a lot comparing to other phone brands.
Yeah
Past Nokia cells have been very good for me, too. I'm worried about the future, though. Everyone seems to go to heavy OSs that are close to desktop ones, and put faster hardware in phones to run them. As batteries rarely get more capacity (I don't know for how many years phones have dealt with a few Wh in their batteries, but I think it's safe to say that an order of magnitude improvement is not coming soon), and CPU efficiency is already very high in the mobile world and does not get much higher, I see low battery lives becoming a fatality, and mid-end phones becoming increasingly sluggish. I think Samsung's decision to have the bada OS use two different kernels depending on which hardware it runs on is best in the long run. RTOSs are best for low- and mid-end phones with not so much processing power. Heavier kernels with much less snappy event handling, like Linux, should only be used on high-end devices (that have, like, 1GHz processors), where other priorities mandate their use.
Edited 2011-05-25 13:40 UTC
Member since:2009-06-20
And I'm sure that Nokia will tailor the hardware and software to be as power savy as it gets
I am afraid that is the very reason they waited so much to release a Meego phone (despite thousands of R&D engineers and millions of $ already spent) and went the WP7 route: as Meego is a bleeding-edge (btrfs, wayland), full linux stack, they have a hard time making it efficient.
Member since:2009-05-19
News
Linked by Thom Holwerda on 05/18/13 21:06 UTC
"At the end of a week in which Electronic Arts confirmed it wasn't developing a thing for the Wii U, one of the software engineers in EA Sports' Canada studio, in a series of since-deleted tweets, disparaged the console as 'crap' and suggested Nintendo should give up on hardware altogether. 'The Wii U is crap. Less powerful than an Xbox 360. Poor online/store. Weird tablet', tweeted Bob Summerwill, listed as a senior software engineer at EA Canada, in a reply to a tweet posting a link about EA's no-Wii U news. 'Nintendo are walking dead at this point'." The Wii U is turning into the 21st century's Virtual Boy.
Linked by Thom Holwerda on 05/18/13 7:37 UTC
"In NixOS, the entire operating system - the kernel, applications, system packages, configuration files, and so on - is built by the Nix package manager from a description in a purely functional build language. The fact that it's purely functional essentially means that building a new configuration cannot overwrite previous configurations. Most of the other features follow from this." Interesting approach. A Linux distribution, sure, but with some very refreshing ideas about system configuration.
Linked by fran on 05/18/13 1:38 UTC
Appfour added, among other features, C/C++ support to its new version of AIDE. From Android-IDE, "Now you can write parts of your app or your whole app in C/C++ on your device. AIDE supports the Standard Android NDK toolchain (GCC 4.6 + Bionic, STL, ...). No changes are necessary if you want to build an app developed on a PC with Eclipse. C/C++ development is fully integrated: Build errors appear in the error list and files can easily be navigated to with Go to file. The editor supports C/C++ syntax highlighting."
Linked by Thom Holwerda on 05/17/13 23:35 UTC, submitted by kragil
Ars nails it: "The answer is that Google did announce what amounts to a fairly substantial Android update yesterday. They simply did it without adding to the update fragmentation problems that continue to plague the platform. By focusing on these changes and not the apparently-waiting-in-the-wings update to the core software, Google is showing us one of the ways in which it's trying to fix the update problem."
Linked by MOS6510 on 05/17/13 22:22 UTC
"It is good for programmers to understand what goes on inside a processor. The CPU is at the heart of our career. What goes on inside the CPU? How long does it take for one instruction to run? What does it mean when a new CPU has a 12-stage pipeline, or 18-stage pipeline, or even a 'deep' 31-stage pipeline? Programs generally treat the CPU as a black box. Instructions go into the box in order, instructions come out of the box in order, and some processing magic happens inside. As a programmer, it is useful to learn what happens inside the box. This is especially true if you will be working on tasks like program optimization. If you don't know what is going on inside the CPU, how can you optimize for it? This article is about what goes on inside the x86 processor's deep pipeline."
Linked by Thom Holwerda on 05/17/13 22:15 UTC, submitted by Tom
"It was the only moment I heard regret slip into Otellini's voice during the several hours of conversations I had with him. 'The lesson I took away from that was, while we like to speak with data around here, so many times in my career I've ended up making decisions with my gut, and I should have followed my gut,' he said. 'My gut told me to say yes.'" The world would've been a much different place - Apple would have been less dependant on Samsung for its chips, which probably would've meant less money for Samsung to develop its Galaxy business.
Linked by Thom Holwerda on 05/16/13 21:41 UTC
Glass is getting some love at Google I/O as well. New applications have been released - Facebook, Twitter, Evernote, Elle, Tumblr, and CNN. Perhaps more interesting: the newly announced Google Glass Developer Kit will allow offline applications and direct hardware access - great for hacking and expanding Glass' potential. This kit will really allow hackers to put Glass through its paces.
Linked by Thom Holwerda on 05/16/13 17:04 UTC
"But Beck and Merrill decided that simply banning toxic players wasn't an acceptable solution for their game. Riot Games began experimenting with more constructive modes of player management through a formal player behavior initiative that actually conducts controlled experiments on its player base to see what helps reduce bad behavior. The results of that initiative have been shared at a lecture at the Massachusetts Institute of Technology and on panels at the Penny Arcade Expo East and the Game Developers Conference." Absolutely fascinating stuff. I'm a League of Legends player, and to be honest, the community isn't nearly as bad as some make it out to be. I'm happy Riot games has the guts to employ science to address the issue.
Linked by Thom Holwerda on 05/16/13 13:17 UTC
"Android and iOS, the number one and number two ranked smartphone operating systems worldwide, combined for 92.3% of all smartphone shipments during the first quarter of 2013 as Windows Phone crept past BlackBerry for 3rd place. According to the International Data Corporation Worldwide Quarterly Mobile Phone Tracker, Android smartphone vendors and Apple shipped a total of 199.5 million units worldwide during 1Q13, up 59.1% from the 125.4 million units shipped during 1Q12." Windows Phone doubles from a few to twice few, iOS loser market share as its growth is slower than that of the overall market. BlackBerry continues slide into irrelevance.
Linked by Thom Holwerda on 05/16/13 12:06 UTC
"According to the latest research from our Wireless Smartphone Strategies service, global Android smartphone profits reached US$5 billion in total during the first quarter of 2013. Samsung dominated and captured an impressive 95 percent share of all Android smartphone profits." Wow.More News »
Sponsored Links
Member since:
2010-03-08
The thing is, this worked with Symbian, because Symbian was designed for mobile and embedded devices in the first place. But since Nokia apparently now wants to go "the wow starts now", and get into Microsoft OSs on one side and Linux with lots of GPU-accelerated eye candy on another side, they'll also have to put very fast and power-hungry hardware before things work smoothly, whether they like it or not.
Edited 2011-05-25 09:55 UTC