Linked by Thom Holwerda on Fri 11th Feb 2011 11:35 UTC
PDAs, Cellphones, Wireless A lot of people are wondering why Nokia didn't choose to go with Android. How can Nokia differentiate themselves when Android is a lot more open and free than Windows Phone 7? As usual, the key to this is in the details. If you read the announcements carefully, you'll see that Microsoft offered Nokia something Google most likely didn't. Update: What a surprise. Elop just confirmed Nokia has a special deal with Microsoft. Whereas HTC, Samsung, and so on are not allowed to customise WP7 - Nokia is, further confirming my theory.
Thread beginning with comment 462148
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[6]: So
by Nelson on Fri 11th Feb 2011 17:54 UTC in reply to "RE[5]: So"
Member since:

I don't care what cushy little number project you've got yourself on to that you might deliver some time in the next decade

We took it from white board to in customers hands in four months. It was a rewrite of a legacy C++ LOB app filled to the brim with COM using very legacy database solutions. We turned it into a mixed mode WPF app with O/RM using the Entity Framework, and to boot we were able to significantly improve performance, feature set, and maintainability (through separation of concerns, unit testing, and UI automation). We cut tens of thousands out of support dollars for a fraction of the cost it took to maintain that sinking ship for the same amount of time.

when you've moved it to .Net 54.2 for the umpteenth time, but normal enterprises are chock full of legacy COM, C++ and VB applications that won't be rewritten in .Net.

Most shops are moving towards at least WinForms, some WPF and some Silverlight depending on how well its pitched and what kind of needs they have.

Most anybody who does this kind of contracted work already specializes in both COM iterop and mixed mode applications, insofar as to maintain a lot of business logic, or at least salvage a significant portion of it. Things move very quickly once we get whiteboarded.

Anything new or rewritten in the past decade was written as a web application. That's right. One of those things that doesn't need a Windows platform.

This is ridiculously false. Don't just make shit up. The majority of LOB I see is all .NET, differing versions (some even .NET1.0/1.1) but the vast majority are .NET for the LOB sector.

The few that have those creaky MFC and C++ solutions are very dated and its usually the one thing hindering them from moving to a more modern OS because it relies on some weird shim specific to that version of Windows. A worse horror is one where most of the original maintainers of the code have gone, or the contracted company doesnt even exist anymore, so they really have no idea whats going on.

People have been telling me that .Net has been happening for a decade, and while I occasionally see the odd system that's been rewritten about fifteen times for Winforms, WPF, Silverlight or whatever the MSDN loons have put out this week, the stuff that sits there and actually works uses.......something else.

.NET is not coming. .NET has arrived. The developers number in the millions. C# is extremely popular, Visual Studio is the undisputed IDE king. The age of these barbaric, runtimeless languages has come and gone. I for one, embrace our type safe, just in time compiling overlords.

So no one apart from Microsoft then? Glad we cleared that up.

Those are all frameworks used by thousands and thousands of developers. They have quite the following.

It's alright. Game developers have been doing that for years, and they've been doing unspeakable things in that that most normal developers would never do because speed matters.

Most of the performance gains in the video game sector from the past decade have been in the realm of pure graphics. When it comes to using the GPU: A shader is a shader. Done in C++ or done in XNA with C# or done in Unity with UnityScript, once it's on the GPU, it does not matter. So a lot of the worries about performance is misplaced.

Areas which legitimately may suffer under a managed environment are physics, AI, scene node construction and management, some CPU bound calculations on geometry, things like that. However many SIMD instructions exist in .NET (Mono.Simd comes to mind) which brings the performance on par, and even in some cases, surpasses native code performance due to the JITer having more runtime intelligence about the target machine than a compile time toolchain.

Reply Parent Score: 4

RE[7]: So
by MysterMask on Fri 11th Feb 2011 19:14 in reply to "RE[6]: So"
MysterMask Member since:

We cut tens of thousands out of support dollars for a fraction of the cost it took to maintain that sinking ship for the same amount of time.

Congrats! So your customer moved from a Windows only solution to ... another Windows only solution. Poor idiots ..

Reply Parent Score: 1

RE[8]: So
by segedunum on Fri 11th Feb 2011 20:20 in reply to "RE[7]: So"
segedunum Member since:

Congrats! So your customer moved from a Windows only solution to ... another Windows only solution. Poor idiots ..

ROTFL. Yer, that's why .Net simply hasn't happened in the past decade despite what idiots like this tell us.

Right, so you want us to rewrite this application that took us years to develop and maintain that now works in something completely new and shiny, and it will do exactly the same thing functionally if we're lucky? Errr, right. That support reduction is the usual crock you get when this is raised. Web applications don't need installation or deployment which is why people have found those more interesting in the past decade.

Just about everything significant that's needed to be written for the desktop has already been written and the inertia from those applications is huge.

Reply Parent Score: 2