Linked by Thom Holwerda on Tue 21st Dec 2010 22:56 UTC, submitted by fran
Windows Very light on details, but this is interesting nonetheless - very interesting, and potentially one of the biggest things to have hit the operating systems business this decade. Bloomberg is reporting that Microsoft plans to announce Windows for ARM processors at CES in January 2011.
Thread beginning with comment 454508
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[13]: what's the point?
by Nelson on Wed 22nd Dec 2010 23:18 UTC in reply to "RE[12]: what's the point?"
Nelson
Member since:
2005-11-29

I really don't think its too far of a reach to name another mobile platform in a discussion about mobile platforms. Especially since I first made the assertion that I am more productive with one, having developed for three. Not by a small margin either.

Additionally, it just speaks to the point about knowing the language and the platform well, but still running into practical limits of the platform. I could just as easily have named iOS or to a much lesser extent, webOS.

Reply Parent Score: 2

RE[14]: what's the point?
by TheGZeus on Wed 22nd Dec 2010 23:31 in reply to "RE[13]: what's the point?"
TheGZeus Member since:
2010-05-19

When did this become a discussion about mobile platforms?
I thought we were talking about _development_ platforms and operating systems.
Even that's a digression from operating systems and processor architectures.

You mentioned silverlight, I mentioned Java.

No one brought up Android/Dalvik until you stuck it in there like the stuffy-guy it is.

Edited 2010-12-22 23:34 UTC

Reply Parent Score: 2

RE[15]: what's the point?
by Nelson on Wed 22nd Dec 2010 23:52 in reply to "RE[14]: what's the point?"
Nelson Member since:
2005-11-29

When did this become a discussion about mobile platforms?
I thought we were talking about _development_ platforms and operating systems.
Even that's a digression from operating systems and processor architectures.

You mentioned silverlight, I mentioned Java.

No one brought up Android/Dalvik until you stuck it in there like the stuffy-guy it is.


I first mentioned them in an off the cuff remark about Silverlight at the end of my first post. In fact, it's the part of my post you ran with.

Now, why are you wasting time with technicalities and semantics instead of commenting on the substance of my post.

Reply Parent Score: 2

oiaohm Member since:
2009-05-30

I really don't think its too far of a reach to name another mobile platform in a discussion about mobile platforms. Especially since I first made the assertion that I am more productive with one, having developed for three. Not by a small margin either.

Additionally, it just speaks to the point about knowing the language and the platform well, but still running into practical limits of the platform. I could just as easily have named iOS or to a much lesser extent, webOS.


Problem here. OpenKode. Works on iOS. Also works meego and symbian and windows ... Basically everything bar the Xbox 360 (unless you pay for development kit for native program then you can make OpenKode stuff work) Thinking it worth while paying for native on the Xbox 360 since native runs a lot better than XNA, blackbery and the Windows Phone 7.

QT also has the same kind of everywhere coverage and its growing. QT is a broader API than OpenKode.

The simple point here you are productive in the most non cross platform solution. For me spittng out a OS X/Windows/OSi/Windows mobile 6.5/Android/sybmian application is basically code all the same things and just build for each platform.

Blackbery and Windows Phone 7 are the two that are complete crap to me. Since I would have to go out of my way to make custom code to support the platforms.

I don't call you productive. In fact I call you non productive since you cannot build effectively for 90 percent of the market out there. Sorry 90 percent of desktop is less than 50 percent of the total market out there for graphical apps.

I don't class webos as a competitor to worry about. Market share is too small. .net skills don't help you at all with webos. HTML 5 skills do. So to support it you support web users again. Not coding for a single set of platforms from 1 company.

If what you are coding in is not proper cross platform you are wasting your dollars these days.

Reply Parent Score: 1

Nelson Member since:
2005-11-29


Problem here. OpenKode. Works on iOS. Also works meego and symbian and windows ... Basically everything bar the Xbox 360 (unless you pay for development kit for native program then you can make OpenKode stuff work) Thinking it worth while paying for native on the Xbox 360 since native runs a lot better than XNA, blackbery and the Windows Phone 7.


Except that OpenKode is built upon the same set of dodgy standards which have variable support across devices. I take it you've never tried to implement OpenGL ES across more than one Android device? I have. Surely you're aware of the missing vendor extensions, different texture depths to accomondate, and outright quirky behavior of some popular handsets, right?

You've seen the differences in the OGLES implementation of Tegra SoCs vs the Snapdragons or TI SoCs right? No? Okay then.

It's a pain in the ass, a big fucking pain in the ass.


QT also has the same kind of everywhere coverage and its growing. QT is a broader API than OpenKode.


QT is decent, and I've dabbled in Qt Quick, but you're still going to run into a practical limit of productivity. A lot of the Qt stuff is in its infancy when it comes to rich media presentation, and even so, the maturity of the platforms, not to mention the tooling, is woefully inadequate.


The simple point here you are productive in the most non cross platform solution. For me spittng out a OS X/Windows/OSi/Windows mobile 6.5/Android/sybmian application is basically code all the same things and just build for each platform.


I think that's a huge problem. Sure, you're cross platform, but you're forced to shoe horn experience into a least common denominator across all of them.

You're not as cross platform as you think, and even if you are, quality suffers.


I don't call you productive. In fact I call you non productive since you cannot build effectively for 90 percent of the market out there. Sorry 90 percent of desktop is less than 50 percent of the total market out there for graphical apps.


The slice of the market we target is not as relevant as is the amount of returns we get on our investment. We had to spend very little money to get our existing code to go from working on Windows and OSX to working on Windows Phone 7. So in one month we were able to create a new stream of revenue at a cost of very little man hours.

And not just that, we were able to, due to the power of Silverlight, deliver a consistently compelling experience to our customers.


I don't class webos as a competitor to worry about. Market share is too small. .net skills don't help you at all with webos. HTML 5 skills do. So to support it you support web users again. Not coding for a single set of platforms from 1 company.


webOS was actually trivial to do, since web technologies mesh well with how our service pushes data to our clients. Again, a testament to the interoperability of Wcf and its web services.


If what you are coding in is not proper cross platform you are wasting your dollars these days.


I think that's really a cop out, and it's cutting corners. I'd rather be really good on a handful of platform, than mediocre on all of them.

Our returns relative to our investment are good enough for it to be considered a success story in house.

Reply Parent Score: 2