4 ms·
Glad to see Apple moving away from ObjC (when it makes sense to). This seems to contrast MS when they released .NET but shied from using it in their own system
by raverbashing 8y ago
Glad to see Apple moving away from ObjC (when it makes sense to).
This seems to contrast MS when they released .NET but shied from using it in their own systems (though I might be wrong)
- qalmakka 8y agoBecause especially in its infancy .NET was quite slow for the machines of the time (they somewhat fixed that up in later releases); it also meant a full rewrite most of the time (COM interop is well supported, but still rather nightmarish at times). Given the paramount importance Microsoft gives to back compatibility, I understand why they took their choices.
- ComputerGuru 8y agoApples and oranges. .NET is a higher-level framework for JIT languages (mainly C#). Only last two years (almost 20 years after its inception) has .NET Native come into the picture. The performance difference between the garbage collected runtime and its C predecessor was too much and initial attempts at the rewrite in C# with Longhorn were a major fail.
- sitepodmatt 8y agoThere was Paint.net, and they did use god awful WPF in Vs 2010 iirc
- ptman 8y agoIt doesn't seem to be by microsoft: https://en.wikipedia.org/wiki/Paint.net https://en.wikipedia.org/wiki/Paint.net
- imandride 8y agoYeah if your are referring to paint.net in the app store the developer is not Microsoft.
- sitepodmatt 8y agoI stand corrected, thanks
- pjmlp 8y agoSQL Server Management console, Visual Studio, Windows Phone 7, Silverlight. Then there was Longhorn, which failed more due to internal politics than due to technical issues, as Midori later has proven just to be killed by management, as decribed by Joe Duffy postmortem reports. WinRT/UAP/UWP are built on top of improved COM, and .NET has a native personality for them, using AOT compiler for WinRT/UAP (MDIL) and UWP (.NET Native). Most of the new UWP stuff is written in .NET Native, with C++ taking care of the UWP runtime infrastructure, and the DirectX composition engine (Visual Layer). The majority of Windows UI team UWP and FluentUI demos are usually done in .NET Native.
- raverbashing 8y agoThanks for these examples. Do you know since when was SQL Server Management Console done in .NET? (to be fair the last one I used was around 2008) Silverlight was more of a platform than an "internal product" and it was based on .NET so it was only natural (it doesn't seem to have taken off though) And yes .NET makes COM usable (well it is usable using MS libraries in C/C++, otherwise, forget about it :) )
- apple4ever 8y agoI'm not. Objective-C is a beautiful and amazing language. They should have done Objective-C 3.0 instead of Swift.