.NET going open source!

.NET going open source!

Didn’t see that one coming!  VS15 going cross platform for Windows, iOS and Android, and – with an OSX .NET core – soon for OSX as well, I guess.

   

26 thoughts on “.NET going open source!


  1. You can’t blame the platform for shoddily written software, Simon!  A bad programmer will be a bad programmer on any platform in any language 🙂


  2. Simon Stuart which .NET version do you refer to? Even though I am quite a “Delphi Head” close to being biased – I could not notice the “curse” you refer to in my C# projects. Your instances will never be released as long as they are referenced somewhere – besides of that GC in .NET works well – doesn’t it?


  3. Lars Fosdal “A bad programmer will be a bad programmer on any platform in any language” … but with some IDE and Component Sets his customers will never feel any pain whatsoever, because the tools constrain him from being awfully bad.


  4. Simon Stuart  Yes – obviously it could be that this .NET problems do not occur in my developments due to a less demanding context. But to be a little iffy – to use problems of a client software as an argument against .NET, just because the client was developed by good developers, seems a little bit unfair.


  5. Mono is open source – which is interesting in this context – will they replace their stuff with MS’s stuff as far as possible, or remain a divergent implementation of .NET?


    Given the current market share of Unity, it would be strange if this culling problem was a general problem? 


  6. Isn’t Steam written in C++? A quick Google says so.


    Simon Stuart .Net does have some GC problems that I know of, but none of them are ‘doesn’t release objects at all’. (It doesn’t suffer from circular references, even.) Do you have a link describing the issue more closely? I’d be very interested to read it.


    I do know there are some issues, and some colleagues at my last workplace wrote a custom memory and GC implementation. That was for a very unusual product with very unusual memory requirements, though.


  7. That leakage is in a C++ Game Engine with a Mono C# wrapper, not in MS .NET.


    If someone fails to attach required non-standard assemblies with their installation – how is that MS’s and .NET’s fault?


  8. I guess. I spent many years doing manual memory management in C, Delphi and C++ (where sometimes there were smart pointers, but sometimes not. I used them when I could.)


    These days on Delphi I use interface references everywhere, and I can’t wait for the day automatic refcounting arrives in the desktop compiler. It’s just something I don’t want to have to worry about. I can do it, but I don’t want to.


  9. No safety net needed.  Just like if we in Delphi fail to explicitly free memory, the memory manager should run out, not do magic.  Retraining sounds like the way to go.


  10. Is delphi even used for new development? The reason I am asking is that with the .Net tools and Xamarin you can produce apps for Andoid, iOS, and Windows. Since Visual Studios offers a community edition and RAD studios would cost me around $2500 CAD, it seems to be a better choice going with .NET. Also a lot of forums refer to delphi as being dead and the community is shrinking. What are your thoughts on that?


  11. It looks like the VisualStudio Community Edition has a licensing limitation on the type of software that is developed. 


    http://programmers.stackexchange.com/questions/262916/need-help-understanding-visual-studio-community-edition-license


    According to this article, it’s more expansive than the older “Express” version, but has restrictions on the “enterprise settings” and a 5 person team limit. Also, “The shift that’s happening here is Visual Studio is basically going freemium. ”


    http://techcrunch.com/2014/11/12/microsoft-makes-visual-studio-free-for-small-teams/


  12. Simon Stuart Indeed I have my first .NET project with memory problems at the moment. Did not think .NET would cause me a problem in such a way – but to be fair, am not sure if it is not maybe caused by the caller not releasing what it should.

Leave a Reply