Entries:
Comments:
Discussions:

Loading user information from Channel 9

Something went wrong getting user information from Channel 9

Latest Achievement:

Loading user information from MSDN

Something went wrong getting user information from MSDN

Visual Studio Achievements

Latest Achievement:

Loading Visual Studio Achievements

Something went wrong getting the Visual Studio Achievements

Discussions

Elmer elmer I'm on my very last life.
  • Jury: Google allowed to use Java APIs in Android

    Oracle were always going to struggle with their argument, when Sun had apparently previously given approval (albeit reluctantly) for the use of Java APIs in Android. The jury appears to have decided that Oracle can't un-do that approval, which seems reasonable enough.

  • Surface phone

    , Wodd wrote

    But, the Lumia product line simply no longer fits elmer's taste.

    It's not a matter of "taste" but a matter of Lumia offering no compelling reason to invest my hard-earned.

    Microsoft are ensuring that you can get the same apps & services from them regardless of what platform you choose, which means that there is precious little reason to favour the Microsoft device.

    I don't think (and I don't believe that I have ever said) that the 950 is a BAD phone (from a hardware point of view) but WM on Lumia brings nothing to the table that either iOS or Android devices can't offer as well or better, and lags way behind both of them in too many areas.

    If a 950 were to be offered at 1/3 of its current off-plan price, then that might be a valid reason worth considering. But when it costs as much (or more) than the alternatives, and offers less than them... why would I choose it?

    With regard to running Win32 applications, that is probably still impractical.

    *snip*

    The point of an x86 device was never to run W32 apps on the handset, but to enable them to be run when docked. A feature that the competition could never offer.

    However, the x86 handset appears to be dead & buried, now that Intel have pulled the plug on low-power Atoms, so unless Microsoft can develop an x86 docking device that allows this ability to run W32 apps (we've discussed this concept in other threads) then we are back to Lumia(Surface) phones offering no compelling reason to choose them, and a long list of reasons not to.

  • Nasty Microsoft

    As Paul Thurrott says here

    "My God, Microsoft. Just stop."

  • Nasty Microsoft

    @bondsbw:

    , bondsbw wrote

    *snip*

    If it were only that simple.  Many people just want to use the same OS with no changes whatsoever.  But then they also want it to have the latest security and performance enhancements along with compatibility with the newest applications and other improvements.

    There are always extremes (Steve Gibson for example) but I believe that most people object to change on a simple "who moved my cheese" basis, and would be less resistant if MS was not so intransigent in the way it deals with this type of feedback.

    Support for personalisation to the degree that users could immediately feel comfortable with a familiar UI, and then explore the newer options at their own pace, would go a long way to placating the resistance many users and businesses have - needing to relearn-retrain just to be able to do the same task, is a pretty reasonable argument for saying no.

    As an example, Stardock (with a small team) has shown that it's perfectly possible to provide users with a familiar start menu they can select, that does not impede the functionality of W10 but allows users to apply what they already know, while making use of what's new. Sure, those who know about it can buy the product and fix that problem cheaply, but it would have made things less of a drama if MS actually listened to what people are saying, and provided what they asked for.

    I know that Steve Jobs famously proclaimed that users don't know what they want until you give it to them, but that level of arrogance only works with Apple.

  • Nasty Microsoft

    GWX is an example of corporate stupidity and incompetence.

    Stupidity on the part of the people who actually think this is a good idea, and incompetence on the part of higher management who let them damage the company by not restraining them.

    Microsoft - make a product that people WANT to install.

  • MS selling feature phone business

    I suspect that I'd be quite happy with this, rather than a Lumia/Surface phone.

    https://www.microsoft.com/en/mobile/phone/230-dual-sim/

    3 weeks standby... I remember my Nokia 6310 used to do that.

    The only problem being that the carriers where I live are killing off the GSM network this year.

  • MS selling feature phone business

    http://company.nokia.com/en/news/press-releases/2016/05/18/nokia-signs-strategic-brand-and-intellectual-property-licensing-agreement-enabling-hmd-global-to-create-new-generation-of-nokia-branded-mobile-phones-and-tablets

    Now that MS have divested themselves of all things Nokia to a group wanting to re-start the Nokia brand, it's probably unlikely that there will another Lumia from Microsoft, as Lumia is still too closely associated with Nokia.

    If Microsoft continue to design new phones at all, they will be Surface Phones, and of course they will outsource the production the same way as they do with other Surface devices.

     

  • a thread with no name ??

    , figuerres wrote

    I am surprised a bit that no one on the staff @ MS has taken a minute to edit the thread  to make it work or readable with out the <  >  chars ?

    It's clearly more of a problem than not being able to read this thread title... the lack of sanitizing is an attack vector, allowing hijacking of the click to a malicious website.

  • a thread with no name ??

    Actually... I'm not about to try it, but I wonder what would happen if you created a title something like this...

    </a><a href="http://www.google.com">Innocent looking title</a><a href="#">

  • i think MS just screwed up my 950.

    @magicalclick: I had that scenario once, when on the fast-ring. In the end, the only thing that smacked it back into line was to leave the insider program and then rejoin it. Note: YMMV.

    FWIW:  14342.1001 - Stuck at Windows Screen After Install (Mobile)