Slashdot videos: Now with more Slashdot!
We've improved Slashdot's video section; now you can view our video interviews, product close-ups and site visits with all the usual Slashdot options to comment, share, etc. No more walled garden! It's a work in progress -- we hope you'll check it out (Learn more about the recent updates).
Atleast, that's more logical than assuming the new guy managed to convince the board (in a few months) to make a massive change to the strategy by killing everything.
Ex-Nokian here. I lost my job due to "Elop's" strategy. But pre-Elop Nokia was fucked. Perhaps he accelerated the decline, but atleast I see a possible (unlikely) future for Nokia now. Previously I saw no future (MeeGo had been stabbed multiple times over a period of many years by the Symbian team as was going nowhere)
Betting on Android always seems like a stupid long term idea to anyone except google. In the short term, sure. See Samsung making money hand over fist. In the long term, lets wait and see what Google's plans with Motorola is (not to mention eventual price erosion of all Android handsets as everyone just starts competing on price)
As an end-user (and an employee of Nokia at the time), I would've preferred Nokia going it alone with MeeGo or even Android. But it made zero sense logically.
And I'd ignore Ahonen on Nokia related news. Most of his opinions are taken apart here: http://dominiescommunicate.wordpress.com/
Anyway, it's blatantly obvious the WP7 decision was not by Elop. The board that needs to approve any of the decisions hadn't changed (and still held the past two CEO's). Could a new-comer (Elop) really change everyone's opinions that quickly? More likely that the board had decided to move to WP7, needed someone new to make the changes, and hired an ex-Microsoftie to do the business.
Elop is just the fall guy.
No they aren't! It's all they have left and the plan is to stick with S40/NOS on the low end (with a Smarterphone UI) and WP7 on the high end
8 months. I worked in Nokia at the time and trust me, that was by far the fastest they ever worked. Most of us never expected to see a phone on the market for 18months (the usual time to market assuming they were just taking an existing product and just changing mechanics -- and this was with a new platform that was never used internally)
Sure, Nokia's imploding; but credit where credit is due. The time to market for (unwanted, apparently) products is ridiculously quick since the Elopcalypse.
Navigation is actually one place where Nokia/WP7 is ahead of the competition (Still prefer Android/Google Maps for finding local shops/locations -- Bing Maps, I'm sure, is terrible
Everything else you said. I'd agree with
you're in an urban canyon. Which will block GLONASS, Galelio, Beidou, etc.., in an equal measure.
But the more independent constellation systems you have in the orbit, the greater the chance you're going to actually see a few satellites in "challenging" scenarios.
So perhaps in a certain location when your car's satnav would usually lose it's fix, it may now continue to track because it can see some GLONASS (or Beidou, or whatever) satellites
Plus, GLONASS is actually designed to give maximum visibility in places like Siberia specifically to work around the problems with GPS with high latitudes. Few links regarding this design decision off wikipedia: http://en.wikipedia.org/wiki/GLONASS#System_description
The constellation's orbital pattern is uniform across the entire surface of the Earth.
Technically, yes, but this assumes you have good visibility of the sky. At high latitudes, especially when you're in cities/urban canyons (where you only have a narrow view of the sky & can't see the horizon), fewer satellites are visible (compared to closer to the equator)
In these circumstances, having an additional constellation to track (GLONASS, Beidou, etc) means more satellites visible, so better performance (faster fixes, better tracking, higher accuracy, etc)
Agree with the rest of what you said
Actually, I never said the current strategy could not succeed. Just said it was high risk. Also note that WP7 is only one part of the strategy (well, it's the only public part)
At the end of the day, Elop is right. Nokia cannot create a viable ecosystem by putting out one phone every 12-18 months (yes, it works for Apple, but Nokia will never be Apple; and even Apple has iPhone, iPod Touch and iPad to drive the ecosystem) Nokia either required the volume of Symbian, or a number of other manufacturers to join them in Club Meego. And no one did (ironically, LG joined just as Nokia left)
This might change in 2-3 years, but by that time it's too late -- you're looking at total domination by iOS & Android with everyone else having under 5% market share.
A new plan was required, and that plan is to use WP7 to slow the Android juggernaut. (I guess the hope in feb11 was that MS will still have HTC & Samsung on board so it's not just Nokia trying to win market share for WP7)
All the above is public knowledge, so I guess I've not said anything new. What isn't public knowledge is what plans Nokia has in 3-4yrs time when hopefully it's a three way split between iOS/WP7-8/Android. Throw in QT, Mobile Phones, "the next billion" for ecosystem building (part of the N9 announcement) and you have your answer (this is also the reason Elop *needs* N9 to be picked up by devs -- and everything he's ever said both internally & externally shows that he's committed to Qt)
Like I said, high risk. Most likely outcome is that WP7 bombs, taking Nokia down with it. But there is a plan in there.
Oh and I don't think MS will ever buy Nokia. Why would you? MS effectively owns Nokia as it is. Nokia takes all the risk. Plus the second MS buys Nokia; HTC, Samsung, all other vendors will bail and MS is in a worse position than before.
Well, unless MS has a secret reason to own a lot of phone factories around the world
(well there also is loads of IP, I guess *shrug*)
Sorry about the earlier comment eating all the breaks! That'll teach me not to preview before I post
OK, the conspiracy theories are getting ridiculous now.
Full disclaimer: I'm an (ex)Nokia employee and was caught up in the great purge of developers following the feb11 announcement. So I'll very soon be out of a job (but as the redundancy package for all the employees at my site is extremely sweet, I'm very happy to bail -- plus this is not the company I joined all those years ago)
Even as an employee, I could see that there is no consumer device they have released in the last 4years (since the N95) that I actually cared about (except the N900; which is not really a consumer device, but it's certainly the best mobile computer on the planet!
Anyway, back to the article; that video was available on the Nokia intranet for employees worldwide to watch. The event was not filled with journalists/bloggers but employees (inside a Nokia site). This is not a vast conspiracy to hurt the N9 (as there are tons of similar videos released internally every week whenever an exec speaks "publicly" at a nokia site; that obviously no one bothered to leak) -- the difference this time is that there are a massive number of disgruntled employees worldwide who have been told their role is terminating/moved to Accenture/projects canceled etc. I assume a random employee leaked this.
You could still say that it's stupid to have confidential videos available to employees worldwide, but that's just how Nokia operates. There is a large amount of trust towards the employees (which is regularly broken), and they've resisted from turning into a massively secret organisation in full lockdown mode (& this is one of the things that makes it a wonderful place to work)
The above is not meant to be taken as me standing up for Elop. I disagree vehemently with his strategy; but there are parts of it that are yet to be made public (well, it is public now, but no one has joined the dots yet
Of course, it's still possible Elop's an MS stooge trying to run the company to the ground. If so, he's doing an amazingly good job of hiding it (internally; where the strategy is known). The only really stupid (public) mistake he's done so far is to EOL Symbian before the successor was in place. I have no idea why, but I assume MS gave Nokia a billion reasons to force him to make that statement.
Anyway, I think Nokia's finished. I'm glad the N9 is out. Full linux distro, root access with a shell out of the box (OK, you need to enable dev mode which is just a UI toggle) -- I have a phone for the next 3 years and a large payout & couldn't care less about what happens to the company
But do keep the conspiracy theories reasonable, guys
Umm... a quick google search will show you that Bluetooth uses more than an order of magnitude less power than WiFI during data transfer (of course, the data rates are lower too, which need to be taken into account). Typical uses, like checking email, webbrowsing, etc all involve short burst of data and long periods where the network is idling which is where BT extremely low (50-100uA sniff current) power consumption really make the difference
Sure, most smartphones use the same chip (and share the same antenna), but that does not mean the energy consumption is the same (the RF is different, even on the same chip)
Range and bandwidth is not the same between BT and WiFi -- you really don't know what you're talking about. Anyway, even if range and bandwidth is the same, that does not mean the energy consumption will be identical. It depends on the considerations taken when designing the protocol (a simple example would be that there is always a trade-off between latency as this dictates how often the devices wake up to "listen" for incoming traffic -- I'm really oversimplifying here, but anyway)
WiFi tethering is completely overkill (atleast from a battery consumption PoV) and the only reason it's popular is that Android (pre 3.0) and iOS do not support a Bluetooth DUN server (or PAN profile accessible from the GUI)
That's one reason I'm holding off buying an Android tablet. I'd like to have an ultra cheap phone with bluetooth (something like the Nokia C2-01. 3G & BT enabled dumbphone) and a tablet that tethers over BT (shell commands to enable this on rooted devices do not count
I installed debian + squeezeserver on it; plugged in a 1Tb drive and I haven't need to mess with it since. That was about two years ago (OK, I do update it occasionally, but as it's firewalled off The Net and just plain works; I'm relucant to mess too much
Absolutely wonderful little box, and couldn't be happier with my Plug
Two USB slots, eSATA & WLAN are all nice additions. Bur I'm still struggling to see the point of bluetooth (it's mostly going to be used as a headless server -- not much point for mice/keyboards; can't see the point of an A2DP headset connection) -- Plus, any usecase that could do with Bluetooth is probably better served by the Beagleboard
Maybe I'm just not trying hard enough
Hmm... I've definitely used dial-up via my mobile phone "back in the day"
I used the phone as an IRDA modem for the Palm Vx for Internet on the move. Good times....
Good. They can start with the Bible.