.NET goes NATIVE!!!!!!
21 - 30 of 30 Posts
Joined
·
19,572 Posts
This is not a replacement for the already dead XNA. MonoGame actually continue XNA legacy and is being developed constantly this days. However as the MS BUILD conference shows DX12 will have support for C# if i understood right and this technology is going to allow the same. In other words you could go forward and do whatever you want. Talking of which this lead me to an inevitable question..... what's the future of C++ if this get developed forward?
C++ holds the golden standard and is being widely used around the world because it offers ways to do things you can't do on other technologies that easy. However there are tons of companies out there that would use C# instead because of it's beauty, fast development and great productivity but because they have no other chance they still use C++. I've worked for several companies myself that would gladly switch and even the one i work right now would love to switch. The problem however is that some tasks won't work as good as they expect them to be if the actual .net was used.
Still... there is a special case were we work with vector graphics that now use WPF using a wrapper i wrote. I've demostrated that a good written application in C# can perform excellent and things may change in the future if this continues like this. There is still a long way to go but this is some exciting news for all those who actually love C# and probably the start of a nightmare for those who never expected this change.
C++ holds the golden standard and is being widely used around the world because it offers ways to do things you can't do on other technologies that easy. However there are tons of companies out there that would use C# instead because of it's beauty, fast development and great productivity but because they have no other chance they still use C++. I've worked for several companies myself that would gladly switch and even the one i work right now would love to switch. The problem however is that some tasks won't work as good as they expect them to be if the actual .net was used.
Still... there is a special case were we work with vector graphics that now use WPF using a wrapper i wrote. I've demostrated that a good written application in C# can perform excellent and things may change in the future if this continues like this. There is still a long way to go but this is some exciting news for all those who actually love C# and probably the start of a nightmare for those who never expected this change.
Joined
·
7,407 Posts
People mocked me regularly for developing primarily in C# & VB.NET years ago. Now, everyone seems to realize just how excellent the .NET framework really is and everyone's a C# aficionado. Funny how that works.
(not speaking of anybody here)
Back on topic, this is very cool news. The few .NET naysayers will have nothing left once .NET = .NET native... err, natively.
(not speaking of anybody here)
Back on topic, this is very cool news. The few .NET naysayers will have nothing left once .NET = .NET native... err, natively.
Joined
·
19,572 Posts
Not only you but that was my case too. The main reason is that a lot of developers out there didn't properly used C# and even worse they started completely wrong. Also most of the points and issues against .Net were based on older versions that no longer apply to newer versions of the framework which is pretty fast and solid. We also have the Ryu Jit this days and a hell bunch of posibilities that were not available in the past. Because of that the awesomeness and great posibilities of the framework were overseen but thanks God time proved how great it is.
I mentioned on my last post a project at work that was simply impossible to achieve with C++(at least for the timespan we got). I finished the project 3 days ago and showed how fast and great a properly written WPF/C# application can be and they are extremely happy. So happy that nobody ever says something against .Net anymore and everyone is willed to learn it and use it in our future projects. In most cases my project while having a bigger amount of vector graphics is up to 3 times faster than the C++ simplistic version not to mention smoother. As a comparison about 1 and half year ago mentioning .Net was like insulting most of devs at work as all they thought was ".Net is so slow" but ironically never trying it out themselves but basing there words in a old project that was badly written like 5 years ago.
I wrote a wrapper to allow interaction between C++ and C# via MVVM as well as a MVVM core and few C++ classes that makes it easy to work with both languages. Right now we continue the work in C++ but more and more parts are getting .Net implementation and in the future there are plans to fully replace everything necessary.
Basically there is absolutely nothing left once is added to the desktop version of the framework which should come in the near future.Back on topic, this is very cool news. The few .NET naysayers will have nothing left once .NET = .NET native... err, natively.
Joined
·
4,074 Posts
Indeed c#/.net is so much more productive and safer to use than C++. I worked at a C++ embedded device place, and the software was terrible. Hanging pointers/null pointers everywhere, terrible architecture, etc.. Now i'm working at a .net 4.0 place, and its so much more fun to code, and so much cleaner too. I'm learning WPF and MVVM on my free time and it has such a deep learning curve, but it looks so much nicer than Winforms.
Joined
·
19,572 Posts
Yeah, C++ has it's use tho. and most specially when dealing with hardware and other stuff like we do at my workplace but it shows it's age and the syntax is overrated in comparison to the clean architecture C# has when written properly.
As for MVVM and WPF... make sure to check my WPF/MVVM tutorial i posted here a while ago. It's far from perfect and i've found ways to improve it further so i will probably write an update in the future. MVVM and WPF has a lot of advantages over Winforms and if you use it properly your applications will work faster because you will save a lot of search, casting and other things you usually need in a Winforms application. The reason is quite simple and that's because you will execute the code exactly where its needed and you will mostly have all the info you have at the right place while having a clean architecture.
The idea is forget about controls and events tied to a certain UI element but focus on your logic and the way you do things. This not just increase the posibilities but make your application far more flexible and dynamic without requiring silly and dirty tricks.
Joined
·
2,853 Posts
Does this mean active-x for Internet Explorer now possible to be port to other web browser now?
Joined
·
19,572 Posts
This isn't about porting active-x controls from IE but far beyond that. The idea is to be able to natively compile .Net code using the same Compiler as C++ while having the same amount of optimizations and Speeds as well as retaining .Net Features and advantages. In other words what this does is turn a language like C# into the new C++.
Joined
·
19,572 Posts
They clearly said that they will look into that in the future but for now they are focusing in store apps. However, with Windows 10 and desktop store apps support as well as universal full trusted app you pretty much have desktop support for .net native in another way.
21 - 30 of 30 Posts
