Live data from Hacker News

Microsoft gives up on Windows 10 Mobile

bbc.co.uk

461–470 of 724 posts

Re: Microsoft gives up on Windows 10 Mobile

#462
post #232

Earlier quoted context omitted.

Original yes, but it also launched only on AT&T in US as well and wasn't all that successful. The real uptick in popularity started with IPhone 3G (with AppStore) which was available world wide.

I can't help but suspect that Jobs would have been happy to leave the iphone US exclusive if it had not been for the gray market of jailbroken phones. Hell, i could have sworn he had to be talked down from lawyerbombing jailbreakers and cydia into the ground.

> I can't help but suspect that Jobs would have been happy to leave the iphone US exclusive if it had not been for the gray market of jailbroken phones.

Why wouldn't he want to sell it worldwide and make Apple significantly more money?

Re: Microsoft gives up on Windows 10 Mobile

#463
post #253

Earlier quoted context omitted.

It's also just such a bad idea because they never get to mature their features, add uniqueness or allow 3rd party devs to build the ecosystem. They just build the same thing over and over again while their competitors keep refining, innovating and adding features. Really a bound to fail strategy

Maybe MS and the FLOSS world aren’t as different as we thought. Look up CADT by Zawinski for details.

Difference is I’m not paying them. We pay Microsoft a metric fuck load of money.

Re: Microsoft gives up on Windows 10 Mobile

#464
post #224

I was working in Microsoft about 5 years ago and Satya's not lying when they say they tried everything to incentivise app developers. It was a big focus of the company at the time. For keystone apps they tried to partner with developers doing most of the work for them. For more niche apps they ran promotions for students and independent developers giving away free phones etc. But nothing was enough to get over the pr…

I worked 3 years as a windows phone dev and i'm sorry to say but Microsofts efforts were ... almost insultingly bad. It started with windows phone 8 and the Metro UI. Bad Idea. The UI was too far away from Android/iPhone to be easily ported and adding corporate design to it was hard as it was too different. Silverlight and XAML was okay for the time. Then came windows 8.1 and windows desktop 8 which was universally h…

> it finally looked like the UWP Plattform might do the trick. Well nope. The SDK is garbage. Scaling from phone to desktop is hidiously bad and afaik still not solved.

A lot people tell me Xcode is garbage, Eclipse is a nightmare, but these apps keep getting cranked out. The Android / iOS language and platform api's are SNAFU, but people get still get into the IDE and start making, without any promise for a set of conversion-frameworks + XML files that will make the app for All The Things. At the rate an app builder is adding features, the universal-platform paradigm is cognitive overload.

I think a No-XML based approach to app development, similiar to VB6 / VBA, would have been greatly appreciated. If MS gives me a stable API to an email client, a calendar, a shared drive, and a messaging or video chat service, I'd spend the 5 hours to automate a 5 minute inconveneince. A windows phone with a bunch of "lifehacks" apps would tremendously useful to much of the smartphone market, as long as they had the cant-live-without-apps too.

Re: Microsoft gives up on Windows 10 Mobile

#465

Earlier quoted context omitted.

And frankly Winmo 7 was the bad move, not 6.5. Because 7 burned the app bridge with 6.5, thus making it ever easier for someone to justify moving to a different platform. Never mind that at launch iphone was more fancy featurephone than smartphone.

> Never mind that at launch iphone was more fancy featurephone than smartphone. Not really. iPhone was the first phone ever that shipped with a real, full-featured, non-crippled web browser. This was an astonishing achievement at the time, and one which made its existing competition look like "fancy featurephones," not the reverse. (Really an astonishing achievement period, considering it had 128MB of RAM).

http://mobilehtml5.org/ I'm interested in how you would define full-featured. Please check the symbian & opera columns. Also, iOS 1.0 ships with Safari3.0, not Safari3.1.1 in this test.

In iOS 2.0 they introduced a new feature that allows you to save web pictures to Photos. Full-feature redefined. :)

Edit: a full-featured television indeed, by Alan Kay's definition: https://www.fastcompany.com/40435064/what-alan-kay-thinks-ab...

Re: Microsoft gives up on Windows 10 Mobile

#466
post #250

Earlier quoted context omitted.

Yes. They also rewrite stuff half way through and tell you it's the same project just to piss you off. Windows Workflow and Windows Communication Foundation for example. I'm really disinclined to invest in any of their technology because my headspace is finite and I want to deliver business value, not change the unworn carpets once a year.

Same here. I can't even imagine how 3rd party tool developers feel. Let's say you have a grid component. In the last few years you had to do a Winforms and several XAML versions( WPF, WinRT, Silverlight and now UWP). The XAML look superficially the same but all have their set of weird limitations and bugs. I am definitely done with Windows desktop.

Wow, imagine someone trying to make this statement 15 years ago...things have sure changed.

Re: Microsoft gives up on Windows 10 Mobile

#467

Earlier quoted context omitted.

As someone that worked on migrations to Silverlight and then to UWP, I still don't understand why these are seen as such big deals. The APIs were more similar than they were different and XAML is still XAML. (The only big loss from Silverlight was being able to browser-host it, but even then that was probably worth losing for the greater good to avoid terrible plugin websites.) The only thing they really dropped was…

You couldn't just port from WPF to Silverlight. They took away tons of features. WinRT was even worse. No idea about UWP but I don't care anymore.

That's why I mentioned semver. APIs change all the time, backwards compatibility gets broken. Yes, conversions weren't always straight forward, but often were possible, and there was an evolutionary arc to it all, and a migration story to follow, even when sometimes that story was a bit rougher than anyone wanted.

Re: Microsoft gives up on Windows 10 Mobile

#468

Earlier quoted context omitted.

>We still can't get the basics like sound, wifi, etc out of the box. Complete and total fabrication. Video for gaming is still trouble, but I have no more issue with Linux wifi or sound output than I do with Windows. In fact, Linux networking to me is better than Windows.

"It works for me" has never been proof that a problem doesn't exist. I find it hard to take such comments seriously. To be frank: You are wasting everyone's time with such comments.

If I am wasting time, you're doing the same with generic comments. You provided as much proof as I did.

Re: Microsoft gives up on Windows 10 Mobile

#470

As much as I loved Windows Phone (I bought 4 of them), the app development side was never mature enough to take seriously by most professionals. The support from Microsoft on the development side was pretty limited, outside of "hey, we're MS, you need to do this!" At the time, the Metro theme seemed like a novel and interesting idea. In hindsight, mimicking the UX of iOS (which is exactly what Android did), was the c…

> My black Nokia 1020 with the recharging case sits in my desk. Worthless. Can I have it? Since it's worthless and everything. I'll pay shipping.

Well worthless is subjective. There's some value since the camera is pretty great and it can still be used as a legit phone. And I keep tabs on if anyone has built some 3rd party tools for it to turn it into something cool.

You can pester me on LinkedIn if you want: https://www.linkedin.com/in/chidave/

Post reply on HN