Slashdot Mirror


More Windows Phone Update Problems

angry tapir writes "Yet another problem has cropped up preventing some Windows Phone 7 users from getting two software updates, adding a new chapter to the update saga that started in February."

9 of 103 comments (clear)

  1. I just saw this in a fortune cookie... by dachshund · · Score: 4, Insightful

    "If you have time to rigorously test only one component of your software platform, make sure it's the update functionality."

    Words to live by.

    1. Re:I just saw this in a fortune cookie... by RobbieThe1st · · Score: 4, Insightful

      It'd be solved /really/ easily if MS simply mandated a "unbrickable" device, something like how the Nokia N900 does it: A special bootloader that, when booting with the USB cable plugged in, can boot from code transferred over USB, and chainload that into a proper flash.
      Then when you brick your device, just flash it back to the last version and go on with your life.
      But that'd be too easy. Especially as it might let someone run *gasp* custom firmware! Abd we can't have that!

  2. Re:Windows Phone 7 by Znork · · Score: 5, Insightful

    It's quite obvious that Microsoft is astro-turfing heavily. They like to get a couple of these in early on every story. They're getting a little bit better, but phrases like "What is great about WP7 is its support for developers." are easily identifiable as marketing drone speech.

    Most likely they have a bunch of evangelists and/or subcontractors whose only job is to monitor and comment on tech sites; the debacle when Vista marketing got run over by the realitytrain made it quite obvious how expensive it could be to lose control over the narrative.

    And with windows phone being a warmed over windows mobile they certainly have their job cut out for them...

  3. Re:Windows Phone 7 by Nikker · · Score: 5, Insightful

    Jebsus man the shill factor on that comment went over 9000. You posted a press release style 3 paragraph comment the same time as the article (8:21). You set a preemptive attack on the hardware manufacturers. A strawman against Apple. Then out of nowhere a plug for developers on a developers forum again with the preemptive against 'haters'.

    Is obvious shill obvious? Comment below!

    --
    A loop, by its nature, continues. If that didn't make sense, start reading this sentence again.
  4. Re:Update saga? by nstlgc · · Score: 5, Funny

    It means it's Micro$oft bashing time!

    --
    I'm Rocco. I'm the +5 Funny man.
  5. Re:Update saga? by gbjbaanb · · Score: 4, Insightful

    it means that all those WP7 developers might have the latest, coolest, Silverlight based .NET development tools, but once something doesn't work the way the pointy-clicky development environment says it will, they're pretty much clueless.

    It means that they can't get an update to work on a handful of phone models running 1 version of the software. (think what would have happened if they had the hundreds of models that Android has been released on).

    It means that dumbing down development only leads to very poor engineering practices. Most of the time you don't notice, but when you need that old-style expertise, you really miss it.

  6. Re:Update works fine on my Focus by clang_jangle · · Score: 4, Insightful

    Well it's nice to hear that microsoft have finally coded a media player for their new phone platform that works. Curious choice to do so after release of the platform to customers everywhere, but at least their platform is now almost caught up to where Apple, Palm, and Nokia were in 2006. Or will be, when updating doesn't strand anyone anymore.

    --
    Caveat Utilitor
  7. Re:Windows Phone 7 by Bogtha · · Score: 3, Insightful

    Yes, I get the point, but in my experience this is one of the worst things about the Microsoft stack, by far. I've got no problem sharing infrastructure at the CLR level, but once you go beyond that to try to make applications written for one paradigm fit anywhere the CLR is, you end up with an unholy mess. The "integration" doesn't make things easier, it just forces you into one colossal fuckup instead of a more sensible approach of platform-specific front-ends over a portable base.

    Microsoft's approach to web frameworks is an ideal example of this. They tried to make developing a website like developing a desktop application; and web forms, postbacks, and all of that gigantic mountain of failure was the result. ASP.NET development is about as far away from the architectural principles of the web as you can get without dumping the technology altogether and using plugins instead. They tried to abstract away HTTP when it's one of the most fundamental parts of the web, they did a shitty, incomplete job because the architecture of the web and traditional desktop applications are entirely different, and they ended up with a failure that they are now attempting to replace altogether.

    So when somebody comes along and says that they are making a game that can be "web-based" because Silverlight's integration lets them do that easily, my immediate reaction is that it's not "an interesting move", it's a continuation of the same terrible fucked up attitude that Microsoft don't show any real signs of shaking. Hence the question - is this actually a web-based game - i.e. does Silverlight's "integration" really deliver, or is it the same old fuckup they always come out with?

    --
    Bogtha Bogtha Bogtha
  8. Re:Windows Phone 7 by symbolset · · Score: 3, Interesting

    Well obviously one of them will be along presently to point out that "nobody knows" how well WP7 is doing since release because Microsoft won't tell us. Since I know, I may as well nip that one in the bud: Abysmal is not an exaggeration. Panglozz has been scraping the Facebook user statistics weekly since November for all the major phone platforms, and has assembled that delightful analytical spreadsheet that tells us week-by-week how it's doing relative to other platforms.

    Facebook user stats may not be perfect, but it's a huge sample and lines up perfectly with other reports, which seem to be bending over backwards to avoid stating the obvious truth. The phone is not selling. After six months WP7 total facebook users don't add up to two days worth of increase in iPhone and Android platforms. The user base is not there, and ultimately that's what developers care about. They don't care if it's fun to write apps for the phone. They care if there are users to use the apps - and there aren't enough to speak of. The trend is clearly in decline, so not only are the users not there, they're not ever going to be there. Writing Windows Phone apps is not going to be profitable for nearly any developer, and it's not going to make them famous either. Nokia can't save this.

    Some of the numbers we've seen for WP7 are totally bogus. Obviously if nearly three times as many people downloaded the software development kit for WP7 as use WP7 for Facebook, something is amiss. Phone software development is not a 3x more common activity than Facebook posting. Somebody is trying to make it look like the thing is more popular than it actually is - perhaps by including the WP7 SDK with some other tools.

    Which makes me glad that Panglozz is keeping track of this for us. It may be a little bit OCD, but it's helpful.

    --
    Help stamp out iliturcy.