8 ms·
As a .Net developer, I find all of the recent announcements from Microsoft really exciting. I just wonder if these type of things are enough to sway people's o
by slg 13y ago
As a .Net developer, I find all of the recent announcements from Microsoft really exciting. I just wonder if these type of things are enough to sway people's opinions regarding the platform. There is just so much baggage in the developer community when you say .Net or Microsoft (edit: as one of the three comments at the time of this posting proves). Are these moves just going to stave a potential exodus of .Net developers or will it actually lead to new developers picking up the language?
- ragesh 13y agoAs someone who recently moved from C# to working with Node, Angular and Python full time, the recent announcements definitely make me want to go back to using .Net again. I love where all of the new stuff is headed.
- UK-AL 13y agoI've worked with various languages C#, Python, Ruby, Objective-C(I was an iOS developer) but I prefer strongly typed languages for larger projects, and the refactoring tools that it allows for. Eventually I would like a completely statically typed inferred language, go mainstream(Aka Demand for it) C# is my best option atm.
- ragesh 13y agoI agree. My recent forays in to javascript have left me wanting to rewrite big chunks of my new app in TypeScript instead. :)
- badman_ting 13y agoI moved away from C# and .NET about 4 years ago, and use all those things too. The recent developments are great, but I view them more as a cool glass of water for people in a hot place (not hell, far from it). I don't like how .NET as a platform/ecosystem/community lags on certain things that are almost taken for granted in other areas, like deployment tools and package managers. Then again, when I worked with .NET those things were my responsibility so I guess their lack affected me more than many .NET devs.
- UK-AL 13y agoWell the good news is that those things are standard now.
- troygoode 13y agoYes, those are standard now because they're "old" in the rest of the industry. It remains to be seen if newer tech that is starting to become standard outside of the Microsoft ecosystem today (containers, for example) will be integrated fast enough to matter.
- UK-AL 13y agoContainers? You mean like MEF(Included in .net framework) or Unity? .Net has always had containers like that.
- Guillaume86 13y agoNo he mean ressources isolation containers (tiny VMs)
- UK-AL 13y agoI don't know how they would do that with windows, since it requires features in the linux kernel.
- mtrimpe 13y agoIt will never sway a large part of the community. What Apple is to selling integrated hardware, Microsoft is to integrated software. Both are essentially eternal niches; they afford you more ease-of-use if you stay within the mold but their monoculture will make certain things unlikely to happen. Not even so much because it's impossible, but because it goes against the mindset that led to the platform in the first place.
- s_kilk 13y agoNope. I've done .NET development before, and there is essentially nothing that could tempt me back and away from Linux/Clojure/Python/PostgreSQL/etc.
- personZ 13y agoWhile the announcements may be very exciting if your lot is in with Microsoft (^1), for people on mixed platforms and with real technology choice it just seems reactionary. That Microsoft moved configuration files from XML to JSON is really Microsoft's technology choices in a nutshell. I have programmed on the Microsoft stack for many, many years, and still make a good deal of coin in .NET and SQL Server, so I'm not coming at this with an agenda. At the same time I can as easily leverage other technologies so I don't feel as grateful when Microsoft catches up. ^1 - I was working at a shop when .NET was first introduced and one chap was making a case for why we should adopt it. His case made a very compelling case for why the shop should have adopted Java years earlier, and it was actually eye opening to me because it was a demonstration of an organization and a team who saw their universe of choices as being defined by Microsoft.
- DougWebb 13y agoOf course it's reactionary; the entirety of ASP.Net MVC is a reaction to web frameworks on other platforms. The key, I think, is that it's a very positive way to react. In the past Microsoft always took the negative road, trying to destroy competition, rather than the positive road of integrating and collaborating with competition and letting their products stand on their technical merits.
- TheCraiggers 13y ago>In the past Microsoft always took the negative road, trying to destroy competition, rather than the positive road of integrating and collaborating... Wait, what? Have you never heard of the phrase "embrace, extend, and exterminate" before? What you describe is simply step one of their modus operandi. I think the only difference between the 1990's Microsoft and the one we have today is they aren't as good at the exterminating part. They still extend things like crazy, but either they really are trying to play nice or they just don't have the weight to exterminate much any more (that wasn't already swalloed by them). My opinion is it's likely a mixture of the two.
- wting 13y ago
- adamors 13y agoFrom my POV: as soon Mono becomes a first class citizen (starting with a robust, cross platform IDE to hosting on Linux without hassle/shortcomings) I'm sold. Until then, everything .NET is a non starter because I don't care for Windows. At all. Mind you, I don't need it to be open source/FOSS etc.
- Aaronontheweb 13y agoThey're headed there - it's not a coincidence that the new compiler (Roslyn) was announced with full Mono support and Miguel de Icaza standing next to Anders.
- outworlder 13y agoThe C# language is fine, F# is also fine (let's pretend VB does not exist). The CLR is fine (and, in some cases, even better than the JVM). What is not fine is the rest of the ecosystem. Going Microsoft usually means Windows (good luck convincing etc corp. to run on Mono), and sometimes, even things like Sharepoint. Thanks, but no thanks. I'd pick C# over Java any day, but dragging all that baggage is not acceptable.
- giulianob 13y agoDid you read the article? "ASP.NET vNext (and Rosyln) runs on Mono, on both Mac and Linux today. While Mono isn't a project from Microsoft, we'll collaborate with the Mono team, plus Mono will be added to our test matrix. It's our aspiration that it "just work.""
- weego 13y agoHe clearly did, and I echo his sentiment that the chances of Business X buying into the strategy of going .NET but without the ecosystem (what in most people eyes is the safety net of guaranteed support etc) are very close to zero. Even more so when they start trying to hire .net devs with strong linux devops skills.
- Spearchucker 13y ago"(let's pretend VB does not exist)" What's wrong with VB? It does no more and no less than C# does, with different syntax. Shall we just do away with English, because German is just so much more to my taste?
- taspeotis 13y ago> It does no more and no less than C# does, with different syntax They're basically equivalent [1] and I (personally) would rather MS drop the engineering efforts they have in place with VB.NET and focus them on C#. [1] In one or two places VB.NET has more functionality than C#. It has syntax for the CLR's Exception Filters whereas C# does not (although I believe the C# dialect that Roslyn supports is going to change this).
- spamizbad 13y ago> Are these moves just going to stave a potential exodus of .Net developers or will it actually lead to new developers picking up the language? I definitely think these changes will keep existing .NET developers in the fold. People who haven't embraced the Microsoft ecosystem at this point probably won't in the future. Things I'd say hurt outsider adoption: 1) The ecosystem of freely available .NET libraries is minuscule compared to what you have with Python, Ruby, PHP, Java, and probably even Node. And the quality of .NET's 3rd-party commercial packages are typically worse than what you'd expect from free open source libraries in terms of both software quality and documentation. 2) Going along with #1, things like database/service drivers, web service APIs, etc, are never as robust or feature-complete as their Python/Ruby/PHP/Java etc counterparts. And sometimes they're really late to the party getting just a basic implementation going. 3) Many .NET shops are technologically conservative, for various reasons, and don't embrace the new technologies. If you're a developer excited about these technologies, understand that probably 80% of .NET shops will never touch these changes with a 10-foot pole for the next 5-10 years outside of rinky-dink projects. 4) The .NET library itself is kinda unwieldy, and only becomes easier to work with if you invest in expensive tools (Visual Studio). In the OSS world, you may have to install a few freely-available tools first, but you get the first-class experience for no cost pretty much right away. In the editor of your choice. 5) Once you step out of Azure, advanced deployments of Windows server have a sizable learning curve that rival Linux in terms of difficulty and complexity. In fact, today its probably harder, ever since Microsoft re-did technet to make it way more difficult to get comprehensive information on stuff.
- morganherlocker 13y agoIn reference to #1, check out this summary of module counts for each package manager[1]. The TLDR is that Java, Ruby, and Node.js dominate in terms of module numbers. [1] http://modulecounts.com/ http://modulecounts.com/
- jongalloway2 13y agoBut not in terms of average growth, which is an important metric.