On Wednesday, 18 September 2013 at 07:59:43 UTC, Manu wrote:
On 18 September 2013 17:45, PauloPinto <pj...@progtools.org> wrote:


It is mostly C# actually.

The VS 2010 rewrite was a way to fix WPF bugs and prove the developers at
large that big applications could be done in WPF.

As far as I can tell from MSDN blogs, the only C++ bits left standing were
the ones related to C++ development.

This most likely changed with the whole "Going Native" story afterwards.


It's clear that MS have no idea WTF they're doing with VisualStudio, that's been clear for half a decade... I'm just waiting for a viable alternative
to emerge.
Still nothing...

I think it is all very political what is driving them.

With Longhorn, there was the plan to make the OS .NET based, similar to how OS/400 works, and to certain extent Android and WP7 were done.

As Longhorn project was rebooted and Vista came out, whatever problems the teams were having with Longhorn rewrite of Win32 into .NET was attributed to the tooling.

As we all know in our jobs it is easier to blame tooling as the people.

As such the native tools group inside Microsoft felt empowered and started pushing into the back to native direction we see nowadays.

Even the WinRT runtime is nothing new, it was actually developed in 1999.

Microsoft Research proposed a language neutral COM runtime, which eventually became .NET instead.

http://blogs.msdn.com/cfs-file.ashx/__key/communityserver-components-postattachments/00-10-32-72-38/Ext_2D00_VOS.pdf

Full story here, http://blogs.msdn.com/b/dsyme/archive/2012/07/05/more-c-net-generics-history-the-msr-white-paper-from-mid-1999.aspx

I have no idea how far or close from the truth this is, but it is my gut feeling how these events developed themselves.

Typical enterprise political games, which affect everyone that wants to target Windows as well.

--
Paulo

Reply via email to