Printable View
The blog post is pretty easy to find:
Introducing .NET Core
Somebody saw fit to post this thread in General Developer instead of in the .Net ghetto here where it probably belongs, not really being of general interest. Yet here we are!
That aside I have to wonder why the truth threatens so many of the wishful thinkers here who have been spouting all sorts of "facts" made up of whole cloth.
Umm "ok". Well general is general as the topic can go in various directions of discussion. We dont have a general .net discussion forum.Quote:
Originally Posted by dilettante
Fair point to be sure.
So i have read that blog post, and i come to completely different conclusions to you and the guy you linked to, which isn't surprising really :rolleyes:Quote:
The blog post is pretty easy to find:
Introducing .NET Core
.Net Core is an attempt to bring all those separate Frameworks into 1 unified Framework which will work across all O/S's and Devices.
In your mind it has already failed where as those of us less clairvoyant will see how successful this is in the coming months and years.
Once again putting your own view/beliefs onto others, firstly who's truth? as its certainly not mine, and secondly why on earth would i feel threatened? what is there to be threatened aboutQuote:
That aside I have to wonder why the truth threatens so many of the wishful thinkers
Did you read the comments? Many questions were asked there and answered by the author.
For example:
Once again you seem to be projecting a lot of wishful thinking onto the actual situation.Quote:
@Yiannis Berkos: Let's say that I want to create a desktop application targeting windows, mac and linux. How can this be done?
I'm not aware of any plans to provide a cross-platform UI framework, if that's what you're asking for.
Here is some more that helps dispel the murk:
“.NET Core is the future”, but whose future is that?
The answer to that we already know of course. So-called ".Net full" fell into maintanance mode quite a while ago.Quote:
The simple question that popped up in my mind when I read about ‘.NET core is the future’, is: “if .NET core is the future of all .NET stacks, what is going to happen with .NET full and the APIs in .NET full?”
A colleague went digging and he did come up with a list of enhancements in the 4.6 Preview release of the .Net Framework, a subset of:
What's new in the .NET Framework 2015 Preview
So in truth there is still more going on than simply maintenance.
I did, and the full response to that comment was more interesting -Quote:
Did you read the comments? Many questions were asked there and answered by the author.
His logic makes complete sense to me, and if i can create a solution with basically a shared back end and business logic layer and then just have separate projects for the various front ends that would be fantastic, it is a more sensible and better goal than think there will be 1 UI to rule them all.Quote:
I'm not aware of any plans to provide a cross-platform UI framework, if that's what you're asking for.
In general, I don't think we believe in using the exact same bits on all platforms. From personal experience I'd say the goal of any successful cross-platform strategy is maximizing sharing while not compromising the experience due towards the lowest common denominator.
So I'd say: think of your app as a burger, representing the layering. The bottom bun will require OS specific implementations, but we'll probably provide a good chunk of it. The top layer (UI) is also very likely to require leveraging OS/experience specific functionality. The beefy part in the middle represents your business logic and you should make sure you can share most of it across all platforms. OS specific concepts should be either pushed down or up (via inversion of control).
The thing is none of us know exactly where this will go, it is not that black and white. There is a lot up in the air, a lot in progress so we cant fully realise the shape of things, and a lot of positive sounding stuff (well to me, obviously not to you )
One further reply by the author in those comments
Quote:
So basically WPF will die together with the old .NET Framework that will eventually be superseded by .NET Core?
No. The .NET Framework doesn't die -- it simply versions slower. You can think of .NET Core as the faster moving younger brother.
Admit it, really your just Jealous of all the current attention on .Net :)Quote:
So in truth there is still more going on than simply maintenance.
I'd agree with this. Trying to create a unified UI is a nightmare (Java is a prime example of crap UI). UIs have a fluidity to them, as we see across all our devices, that can and do change based on whims - and real reasons.Quote:
Originally Posted by NeedSomeAnswers
Microsoft have been present on the Mac OS desktop for sometime with Office (It seems to be a much more polished product on the Mac than Windows, but that may just be the Retina talking). If the rest of Microsoft - the developers - can pare themselves away from relying on Windows, then Microsoft becomes a software provider and not just a Windows provider. The just so happen to offer an Operating System, also.
So hes calling the FW the slower older brother. Why would anyone want to work with him when they can work with the younger faster brother. That would make one think that the older brother will get retired soon.Quote:
Originally Posted by NeedSomeAnswers
Oh and what grounds does that author have to make teh statement that WPF is being retired? (sorry didnt read it all)
What he was saying in the blog was that the existing .Net Framework for windows desktop development will still be developed but slower, but if you are doing any web or mobile development then you absolutely would want to be targeting the .Net Core Framework which will version faster.... when its ready, that's how i read it anyway.Quote:
Originally Posted by RobDog888
So they are absolutely looking to be concentrating more towards web and mobile and Windows App Store Apps, and pushing Azure services, not that that is a revelation in anyway.
It wasn't the author that said that but one of the commenters. The Author actually linked to the WPF Blog which does layout some of a road map although its a bit vague as to what when.Quote:
Originally Posted by RobDog888
There are some nice sounding things though like -
"We are super excited to announce that we are building a whole suite of debugging tools for WPF apps that enable you to inspect the live visual tree and modify the properties of the elements while debugging"
It certainly wouldn't bother me to see the FW version slower. As far as I'm concerned, all the major additions have been made. The last couple versions added things that are nice for specific subsets of programming, but nothing huge for everyday use. The language has matured, so there isn't all that much need to keep adding features...except to keep making sales, but with the Professional version being released for free for most users, sales may not be the driving force in VS these days.
That would be great! Just like FireBug can debug the html-DOM, having a way to poke at the WPF-xaml-like-DOM would be really great!!Quote:
Originally Posted by NeedSomeAnswers