shrubble 13 days ago

The real issue is that Microsoft's "engineering culture" looked down on the use of co-processor chips and wanted to do everything on a big CPU.

Even in 2012 with the Pureview 808, Nokia had a pixel processing chip that could handle 1 billion pixel a second, with low power usage. Microsoft's inept driver architecture made it difficult to use, so later Microsoft versions of the Lumia phones actually had lower specs and power usage issues.

Elop was very likely Rick Belluzzo of SGI writ large; a mediocre thinker, a big-company bureaucrat who never cared about tech...

chiph 14 days ago

I miss Windows Phone. It was fast, did what I needed, and was easy to use one-handed. The Nokia hardware was good (especially the camera, for the time), except the plastic case & screen collected scratches like crazy.

I would have had no problem paying more for a premium metal & glass case for it.

  • juunpp 14 days ago

    I still have my Lumia 450. It looks as great today as it did 10 years ago. Windows phone is probably the only UI/UX Microsoft got right. Sadly, leave it to Microsoft to ruin a product by pulling the plug.

    • cromka 14 days ago

      If they open sourced it, it could easily become an actually popular, independent mobile OS to compete with Android/iOS.

      • Arainach 14 days ago

        No, it could not.

        Ignoring the technical challenges and impossibilities of open sourcing it (Windows Phone 10 is Windows 10, and the Windows Phone 7/8 codebase was its own crazy beast that was tough enough to work with even when you were being paid to do so), mobile operators do not want you running custom code on their stack, and they are the ultimate gatekeepers of what devices are allowed to connect. There will never be a popular, easy to setup open source phone without a complete reworking of cellular service, at least in the US.

        • cromka 13 days ago

          So all the alternative Linux open source phones, like Pine, or free (and secure) implementations of Android don’t work in the US?

        • justsomehnguy 13 days ago

          > without a complete reworking of cellular service

          There is a whole world, besides the US.

          But it doesn't matter because there would be no apps anyway.

          • cromka 13 days ago

            Apps already existed, it was around the time no one knew which platform will end up being most popular, so many apps had their Windows Mobile version. Not nearly as many as on Android or iOS, true, but they did exist. Especially in Europe.

        • toast0 13 days ago

          I don't think Windows Phone 7+ included anything wild on the baseband. It ran on qualcomm chipsets, and I suspect it was just using their modems as-is.

          Use an approved modem blob and you can connect. Easy peasey. VoLTE makes it a bit trickier, but not that much.

          I mean, yeah, it won't ever be popular. If it's open source, there's no way to sell user data to subsidize the price. And who wants to pay full freight for a phone that probably won't ever fully work... I think I learned my lesson with OpenMoko...

          I enjoyed Windows Phone, but I don't see how it would survive without big pockets and a dedicated, focused, and engaged team that can m move mountains. Big pockets alone weren't enough. Good hardware wasn't enough. Microsoft needed to have delivered on their promise of all WP8 devices getting an upgrade to WM10, and WM10 needed to be good on release. Incidentally, what I think was the final build for Lumia 640 was a lot better than the first build; if the first build was that good, the story may have ended differently. Mobile Edge was still garbage on that phone though; Mobile IE was ugly, but Mobile Edge put a queue between the UI and the engine, which meant when the engine was spinning on some page it could barely handle, you couldn't stop it... All your UI commands would be queued up and played later when the engine had finished whatever it was doing... Unless the watchdog timed out and the whole phone rebooted.

        • immibis 13 days ago

          You can buy a module that plugs into a Raspberry Pi and interfaces with cell networks. Many years ago someone wrote a phone program for one of these modules and called it the PiPhone.

    • asimovfan 13 days ago

      My friend had a folder of photos of peoples laps they all accidentally took when they first handled the phone.

  • pjmlp 13 days ago

    At the time with .NET Native and C+×/CX, with Visual Studio, it was the best development experience among all mobile platforms.

    Then after killing the mobile platform, they messed up the desktop experience as well, killing the goodwill among the strongest advocates of the WinRT platform.

  • Sakos 13 days ago

    The WP I had is still the best smartphone I ever owned and used. I've owned both iPhones and Android phones since then and they all pale in comparison even today. It's really too bad how terrible MS was at the whole WP project. Just end-to-end baffling decisions and bad execution.

  • chefkd 14 days ago

    The Windows 8 tiles were so cool and unique looking I evangelized Windows Phones in our house to this day I feel like a traitor for switching over to an iPhone haha

greatgib 13 days ago

   To be fair, Kallasvuo did try to build a software environment for Nokia phones. The largely open source Maemo operating system failed to take off
This is not fair to say that, Maemo failure again result from bad decision at leadership level, Maemo was never given a chance with standard consumer headsets because Nokia was afraid of hitting their Symbian cash cow at this time...
  • darthrupert 13 days ago

    I worked on that briefly as my first real job. It was totally a side show for Nokia. They (=every layer below the highest) didn't seem to give a fuck about how it goes and quite possibly actively tried to damage the project.

    I think this was a massive leadership failure.

    It destroyed Finland's economy in a way which it hasn't still properly recovered from. It was made worse by those managers moving to other companies after the crash, bringing their so-called culture with them.

  • thisislife2 13 days ago

    It evolved into https://sailfishos.org/ under a startup of ex-Nokia employees ... who knows what the mobile OS' future would have been if it was actually backed properly by Nokia.

nailer 13 days ago

I currently am having a conversation with a company that I have purchased window blinds from, And I cannot find my previous conversation. It may have been Instagram or WhatsApp or email I can’t find any mention of the company beyond certain date.

It’s probably Some other app, but I don’t know what. My understanding is that Windows phone had a universal message search which would mean I’m not in this position.

mydogmuppet 12 days ago

I had two Nokia 1020s. Yes Windows 8 was a nightmare. The 38Mpix camera sensor at 1/1.5 inches, Zeiss lens, OIS coupled with Pureview software rendered stunning images. Especially low light. 9 years on I've never quite got the same joy out of Pixel Pro or IOS images.

HermitX 13 days ago

When the times leave you behind, they won't even say goodbye.

pjmlp 13 days ago

And with that decision, they killed most of the UWP goodwill on Windows desktop as well.

doublerabbit 14 days ago

Sigh, now we've stuck in a world of Google or Apple. I recall a world where each phone had itself own OS, or firmware. Every phone was different.

I miss my Lumia and my Sony Ericsson k700i and just the simplicity of texting.

  • immibis 13 days ago

    Android phones are already like that. Samsung phones will keep pestering you to enable Samsung-specific features and the UI has been rewritten by Samsung.

    • daghamm 13 days ago

      Is it really a bad thing? I really like the Samsung UI and their included features are mostly useful.

      And the world would be a very boring place if everything everywhere looked identical

hulitu 12 days ago

> Ten years ago Microsoft bought Nokia's phone unit – then killed it

Embrace. Extend. Extinguish. The only things they do good. /s

Meanwhile pressing the "X" button on a maximized window causes the window and the one below to close.