It better not, C# with .NET is I think one of the best programming languages out there.
The dying platform: .Net
41–50 of 110 posts
Re: The dying platform: .Net
#42One of the things that I've often thought MS could do to attract more developers to this platform, is to release the brilliant piece of software that is Visual Studio, for FREE. Not just the "Express" edition...the full blown "Ultimate" edition. They should also buy Red Gate and Jet Brains and bake their products into VS and SSMS themselves, while happily releasing updates and enhancements for FREE. Bah...what do I k…
If they do that, they kill the commercial viability of alternatives, which among other things has anti-trust implications.
Re: The dying platform: .Net
#43I guess all that MS software such as office and sharepoint which many a business has deeply integrated into their day to day life, and also extended by using .Net to automate or improve it for their particular needs will be really disappointed that .Net is dying.
I'd imagine they will have a clean and easy migration planned in the next 3 years.
Re: The dying platform: .Net
#44Java isn't looking too good, either, at least in the desktop. You know your platform has jumped the shark when it comes bundled with a toolbar. The question is, where to next? I've been watching Go for a while, but it looks like a tool from Googlers, for Googlers. Pulling all my dependencies from HEAD? No, thank you. Ironically, Javascript looks very promising right now, compared with the alternatives.
You want to do JavaScript on the desktop? No. Go learn Python and Haskell.
Re: The dying platform: .Net
#45From what perspective are you coming from that you think .NET is dying (student, education, corporate, open source)? MS has never been a technology leader as they tend to let others make the early mistakes then charge in, ask Netware, OS2/IBM, Sony, Netscape. Early bird gets the worm but the second mouse gets the cheese!
All of the above? A little background: some of my earliest bits of programming were on VB5, then VB6, and then .NET 1.0 when that first showed up. I spent most of my early years on MS platforms, and for the most part I liked them. I picked up a Surface RT to hack on last year, after a long absence from .NET. The state of .NET shocked me. For one thing, the subset of .NET that's available on WinRT vs. "real" Win8 vs.…
A more general complaint is MS's schizophrenic support of .NET
How so? Microsoft has been completely behind .NET for a decade now. Early on, some .NET advocates demanded that Microsoft only back .NET, with complete ferocity (e.g. that Win32 would become a second class citizen), but that was silly to begin with and is unnecessary.
Various technologies that might have used .NET have come and gone, but Microsoft has been completely behind .NET.
Re: The dying platform: .Net
#46.NET, like practically all tolls by Microsoft, is good for one thing - Large scale enterprise development for Windows. It plays well with Office, Access, Sharepoint, Active Directory, IIS etc. and it's the best around at what it's doing. You can also do webdev or solve highly concurrent problems with .NET and it's great at that as well (I'm very fond of the Nancy framework and C#'s async/await are a godsend) but it's…
While I agree that the C# language is wonderful and some of the .NET framework is very well designed, I think most of the .NET 'Enterprise' SDK's and API's are terribly, horribly overengineered and complicated. SharePoint, Dynamics CRM come to mind. I wish this part of .NET would die, but I am not convinced it will go away anytime soon.
Re: The dying platform: .Net
#47Java isn't looking too good, either, at least in the desktop. You know your platform has jumped the shark when it comes bundled with a toolbar. The question is, where to next? I've been watching Go for a while, but it looks like a tool from Googlers, for Googlers. Pulling all my dependencies from HEAD? No, thank you. Ironically, Javascript looks very promising right now, compared with the alternatives.
I find it strange that people are hung up on this remote dependency "issue." It's a convenience for small projects and quick samples. There is absolutely nothing stopping you from checking out a Go package locally and importing it just like any other dependency in any other language.
It encourages package creators to simply maintain a master branch instead of creating stable releases, and this can turn into a huge headache down the line.
Let's take a recent scenario: the YAML vulnerability in Rails. What if a similar vulnerability is found in a widely-used Go project? Well, you can move to HEAD, but you have no idea what else changed in the meantime. It's impossible to know how your application may break. Or you can try to merge just the security patch, which may not be trivial.
Re: The dying platform: .Net
#48I always wonder if it's a better strategy for Microsoft to introduce the Windows AppStore in Windows 7 first and grow the eco-system there, just like what Apple did MacAppStore to Lion, heck, even 10.6.6 (Snow Leopard) has access to it.
Oh, well, perhaps the higher-ups in MSFT need to have a clue first.
Re: The dying platform: .Net
#49Enterprise standardized on Java and won't change anytime soon (i.e. in the next century or so). Seriously, COBOL is still well and alive at many places. Consumer market is on Objective-C (iOS) or Java (Android). Games are written (mostly) in C++ (and this will stay this way to enable cross-console portability). OSS uses any number of languages that have an openly developed compiler (c, c++, python, ruby, JS, go, you name it), but most certainly not .net. So, who is left? There are isolated silos here and there, but it's really a niche language and there are no use cases that will change this.
Re: The dying platform: .Net
#50> Inherent hatred for Microsoft and anything it does, even if it is good. I think is pretty sad since I see this attitude from people that should be objective from a technical standpoint, licensing can’t always be an issue.
Actually, yes it can. I think Microsoft (especially Microsoft Research) is amazing and have been one of the most innovative companies of the last 30 years. But I'm not gonna pay them for the right to use a language. I'm also not going to lock myself into a system which requires me to pay them for other things as well (Windows Server, SQLServer, etc). I know there is Mono, but it is not the same. Its a shame, cause F# is one of the coolest languages out there right now.