Linked by Thom Holwerda on Wed 9th Feb 2011 00:04 UTC
Speaking of Nokia - Engadget got their hands on what is supposedly an internal memo sent to Nokia employees by the company's new CEO. It's... Brutal. As in, brutally honest. There's no sugar-coating here, no unicorns, no glitter. "Nokia, our platform is burning." Update: Android is probably out of the question. Will it be Windows Phone 7, after all? Damn; Palm tonight, Nokia Friday - what a week for mobile! Update: The "Communities Dominate Brands" blog published an in-depth analysis of the memo, which claims with sound arguments that it might well be a hoax.
Thread beginning with comment 461508
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:2010-10-13
Member since:2005-07-08
Member since:2005-09-27
You think Qt slowed them down?
By far it did, and drayned a lot of money in the process.
it would estimate the time taken to make a Qt interface/application set (browser/mail/media player) of comparable quality to the current (gtk) n900 stack, to be around 3 months for a moderate sized team
You dream to much, and the reality says the contrary.
It would be faster, it would be portable and it would be feasible
"It would" differs from "It does", being multiplatform brings zero to the table, it just need to run well on Nokia phones.
The n900 was 5 years late
In the contrary, it was a phone ahead of its time, many many agree with me.
Member since:2006-07-14
Member since:2006-08-08
I owned a n900 for exactly 2 weeks:
GPS locking time was horrendeous; the need to wait more than 5 minutes to lock-in is too much.
The video output was hillarious. the 3.5" screen had 800 pixel (width) and the video out 640 pixels; the video output changed proportions: every circle on the n900 was an ellipse on the TV. Great!
There was more but this is what comes to mind as soon I think of the n900.
Member since:2005-09-08
News
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
Google 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.
Linked by Thom Holwerda on 05/15/13 23:03 UTC
"During its Keynote today, Google announced new features coming to its flagship search function - you know, that thing we all started using Google for. VP Amit Singhal spent some time discussing what Google's search functionality will eventually morph into. Google's strategy is summarized by three words: answer, converse, and anticipate. Singhal explained that many of the pieces of these upcoming changes can already be seen in products that Google has recently introduced - namely, Google Knowledge Graph and Google Now, with perhaps a splash of Google Glass, too." I hold on to my hat every time Google changes Search. It's such a vital product in my daily life.More News »
Sponsored Links
Member since:
2010-10-13
You think Qt slowed them down?
I would estimate the time taken to make a Qt interface/application set (browser/mail/media player) of comparable quality to the current (gtk) n900 stack, to be around 3 months for a moderate sized team.
It would be faster, it would be portable and it would be feasible. It would not have been QML, that was not out the door, but it would have been Qt as known and loved by legions, and the KDE dudes could have gone to town on the resulting device.
The n900 was 5 years late, under loved and an only child. Nokia rode a lone horse (Symbian) architected with way too much of an emphasis on performance (at the cost of extensibility, convenience and broad usage) straight into the ground.