10 ms·
Getting productive and happy in the .NET ecosystem has a learning curve similar to that of Eve Online. There is this amazing world locked away behind a byzantin
by bob1029 5y ago
Getting productive and happy in the .NET ecosystem has a learning curve similar to that of Eve Online. There is this amazing world locked away behind a byzantine matrix of legacy bullshit. You could waste an entire month struggling with differences between legacy framework and new framework tutorials.
The branding is honestly trash. I feel like if C#10 and latest .NET framework were renamed to something completely different and relaunched under some new company, we wouldn't go a single day without it gracing the front page of HN.
What % of developers are missing out based on principles alone? Microsoft is certainly an oppressive monster but they arguably produce some of the best tools in town right now.
- piva00 5y ago> Microsoft is certainly an oppressive monster but they arguably produce some of the best tools in town right now. Can you expand on this point? What tools Microsoft provides that are the top-of-the-crop right now?
- tasogare 5y agoVisual Studio. Always has been. And the base class library of .net.
- 5e92cb50239222b 5y agoDid you actually try the alternatives? If we're talking about dotnet specifically, then Rider? It's miles ahead of VS in every way that I can think of. I don't personally know a single dotnet developer who kept using VS after trying out Rider for a few weeks.
- radicalbyte 5y agoIt depends on what you're doing; Visual Studio with ReSharper is still very good (as long as you have a beast of a machine).
- tonyedgecombe 5y agoEvery time there is a new version of Visual Studio I try and use it for as long as possible before I give up and install ReSharper. So far VS 2022 looks like it might be good enough without it.
- jmnicolas 5y agoI'm using Visual Studio without Resharper since 2009. What did I miss? :p I never felt I was lacking anything in stock Visual Studio and since my company won't pay for anything I never considered Resharper. Fwiw I have Linux at home and trying Rider (I have used Android Studio before) I much prefer Visual Studio.
- tester756 5y agoVisual Studio with Roslynator (free, needs less resources)
- kovac 5y agoI did. I tried Rider and continued to use VS when I was programming on Windows. On Linux I use Rider (though I'm mostly off. Net stuff now). Reason for using VS is because I like it's UI (like the colour scheme more) and I think there are at times issues with resolving dependency issues like nuget stuff (which is what my colleague told me who is a fulltime rider user but fires up VS rarely to resolve them). I haven't tried things like parallel stack watches, debugging dlls and remote debugging. I just liked these things the way they are in VS. Though I'd rank Rider higher than VS since it runs on Linux.
- konamicode 5y agoVS's windowing system is better than Rider's. I often use VS with a layout which takes up two full screens (editor on one and Tests Explorer/Solution Explorer/Output Window/Find window etc on the other). I haven't yet found a way to replicate this in Rider.
- GordonS 5y agoI use Rider, and often have a code editor on my main monitor, debugger at the top of my secondary monitor, and tests at the bottom of my secondary monitor - it all works great. At the top right of each window pane is a popup menu that let's you change the window mode, it's that simple.
- Const-me 5y ago> It's miles ahead of VS in every way that I can think of When I need to write advanced SIMD code, or consume C libraries like FreeType designed to be hostile towards FFI, I often make C++ DLLs to be consumes from C#. Unlike Rider, Visual Studio is not just .NET IDE, it's a C++ IDE as well. The two debuggers are integrated too, it's easy to debug both C# and C++ at the same time.
- piva00 5y agoAnd Rider is not just Rider, it's based on the IntelliJ platform that can also support multiple different languages, including C++, Python, Java and so on.
- dotancohen 5y agoAs a Linux user, what do I need to experiment with .NET 6 to replace Python for mostly simple file processing? 90% of my use would be to open and read/write files, read from stdin and argv, regex, maybe some http requests and math no heavier than the occasional integral or limit.
- Scarbutt 5y agoDownloading .NET 6, a text editor and reading docs?
- dotancohen 5y agoYes, of course! There was much mention in this thread of the docs being out of date, referring mostly to older dotnet APIs. Also, by mentioning specific use cases, I was hoping - and got - very specific and helpful recommendations.
- thrower123 5y agoYou're probably better just sticking with Python if that is all you are doing. DotNet and C# works fine for all of those things, but it's definitely simpler to get spun up with a Python script for the quick and dirty. DotNet really shines as things get bigger and you need to have more structure.
- pjmlp 5y agoMiles ahead only for those that don't know how to use VS properly. It has tons of features missing for Windows development, debugging across .NET languages, C++, COM and WinRT. Debugging of GPU code, parallel code, integration with mocking frameworks like Fakes, architecture modeling even for files without source available (code maps).
- R0b0t1 5y agoThose latter things (COM, WinRT) are gated behind the enterprise license, IIRC. Most people will not have cause to want them. I know I don't.
- pjmlp 5y agoAny serious Windows developer will.
- R0b0t1 5y agoThey're a sign of dated tech. Nothing modern necessarily needs them. I know how to use them and I can respect the design, but pay gating them for so long has made them irrelevant.
- pjmlp 5y agoNot only those things aren't gated, they are the modern APIs on Windows since Longhorn, they are only irrelevant if you are stuck on Windows XP.
- R0b0t1 5y agoThe developer tooling was pay gated until VS2019 or something. You needed this tooling to make use of the APIs in a reasonable way, or alternative tooling. Most people just responded by not using those APIs or recreating them.
- GordonS 5y ago
- SketchySeaBeast 5y agoSome would argue VSCode is there as well. I know a lot of my coworkers swear by it.
- aliswe 5y agoBut its not an IDE /s
- throw1234651234 5y agoI personally don't like it at all. I use it to write Azure Cloud Functions, but I use WebStorm for Angular/React dev, even though I am used to Visual Studio for .NET.
- dmitriid 5y agoTried Visual Studio 22 Preview. It couldn't run a debugger because "property program isn't defined". Apparently you need to specify some launch.json file god knows where, and god knows why. VSCode kinda works (but also creates a launch.json file somewhere). Rider just works. If it creates something somewhere, I couldn't care less (as I couldn't care less for any other IntelliJ product which tend to just work). Also. Obligatory rant by Casey Muratori on Visual Studio: https://www.youtube.com/watch?v=GC-0tCy4P1U https://www.youtube.com/watch?v=GC-0tCy4P1U
- Dennip 5y agoWhy not the stable version (2019) instead of a literal preview...
- dmitriid 5y agoI'm on a Mac, so decided to give it a try. It's an interface overhaul, why wouldn't it be able to launch something though? I tried to install a previous version. It started installing, and then ... just failed. With no description of what failed, and how to deal with it. So eventually I gave up. WHat's launch.json and where is it described? And why can't it figure stuff automatically like Rider? And why does VSCode create a separate launch.json and why can't the two share the same one? So many questions, so few answers.
- mook 5y agoVisual Studio for Mac is a completely unrelated product that happens to share a name; when people say Visual Studio without any qualifiers they _probably_ don't mean the Mac version. Microsoft overall has a terrible naming sense, with occasional good accidents.
- plorkyeran 5y agoVisual Studio is Windows only. VS for Mac is an unrelated program which used to be named Xamarin Studio.
- rharb 5y ago
- barrenko 5y agoUgly bloated eye-sore. Pardon my language. Just rip off JetBrains already.
- onemoresoop 5y agoI use Visual Studio on a daily basis and I abhor it. It is hard to navigate without a mouse, things are shoved in small boxes and requires a lot of clicking around. But my coworkers love it so it must be a subjective thing, right? The amount of bugs make me hesitant to ever upgrade when I get a stable version. VS 2018 is riddled with UI bugs. One of them that is annoying me is the basic functionality for undo, text no longer focuses on the latest undo chunk and you don't know how far you got.
- GiorgioG 5y ago> Getting productive and happy in the .NET ecosystem has a learning curve similar to that of Eve Online. I'd be curious to know why you feel that way? I've been doing .NET development for ~20 years (since the original beta) so it's hard for me to see it through a newcomer's eyes. ASP.NET Core doesn't seem more complex to start with than any other web framework I've tried (most recently actix-web (Rust), Phoenix (Elixir), Django, etc.)
- Scarbutt 5y agoasp.net core is a clusterfuck of over-architecture and over-abstraction.
- hmrr 5y agoThis. I have to support it in production among other platforms. It’s painful to reverse engineer the stack every time something goes bang which is often and usually something utterly obscure. It also has a much higher amount of hands on work required to keep the plates spinning than any other platform I’ve used. To be clear I have .Net experience going back to the beta frameworks in the early 2000’s and have hand held some huge products on the platform from inception to maintenance phase architecturally and infrastructure wise. It’s been a bloody rough ride and I regret every moment of it and wish I’d picked another platform bet. I’ve had the entire stack rug pulled from underneath major projects multiple times and burned months in pointless rewrites due to tech changes and obsolescence. The majority of the open source ecosystem is broken or abandonware and the commercial bits are overpriced, with poor support and barely work. It’s hell. The only good bit has been being paid by the hour to unfuck stuff which has been profitable.
- jmnicolas 5y agoWhat would you recommend that is fast enough (ie not Ruby or Python)?
- hmrr 5y agoI’m hedging my bets on lots of small bits of well decoupled and well designed Go with micro frontends in JS sitting on top of Kubernetes. It sits in the niche area of being typed, quite fast, light weight, reliable, fast startup, decent tooling and concise enough to be able to build knowledge and retain it.
- city41 5y agoI was a C# dev from 2004 to 2010. It's a nice language and .NET is (was?) quite pleasant. So I often think about switching back to a C# job. But every time I realize I gotta wade through all of this stuff it really turns me off and I still haven't fully made the leap. Maybe one of these days. I do think understanding all this legacy and getting up to speed would be worth it for me.
- ducharmdev 5y agoAs a joke, I'd love to see someone create a landing page of a "new" language with some eye-catching name similar to Kotlin, except it's all C#. I could easily see that hitting the top page of HN.
- Guest42 5y agoCotlin?
- ducharmdev 5y agosCala
- tata71 5y agoCotTime
- tata71 5y agoCotNET
- jjtheblunt 5y agothat made me laugh out loud. excellent
- redhale 5y agoD♭
- kej 5y agoThat reminds me of the "Mojave Experiment" where Microsoft demoed the new version of Windows and after people said they liked it they revealed that it was just the same Windows Vista that people thought they didn't like. https://en.wikipedia.org/wiki/Mojave_Experiment https://en.wikipedia.org/wiki/Mojave_Experiment
- potta_coffee 5y agoI landed on a team that does .NET. They're using the latest dotnetcore stuff. I've worked in various frameworks in many different languages and I can say that from my perspective, the Microsoft ecosystem is the most nihilistic, un-fun, fiddly environment I've ever had to use. The guys that always try to sell it to me never seem to have much exposure to anything else. I can admit that there are different ways of thinking and different styles for different people and teams and that .NET is a valid choice, and lots of decent software is built with it. But I've chosen to stay away.
- aninteger 5y agoBut ".NET core" is "dead". The latest is .NET 5 or even .NET 6 (bleeding edge).
- potta_coffee 5y agoI left that team a couple of months ago but keeping all the different iterations of .NET separate is one of my gripes. The documentation is some of the worst I've ever seen and I simply have no patience for it when I have so many other tools that I can use to get the job done with less friction.
- COM2323 5y agoWhat is the exact opposite then? What is "fun" these days? :) Am I boring? :) I have done a lot of stuff in a lot of languages/frameworks, from electronics to desktop applications to websites and server stuff. Never cared that much about specific technology. It's fine if it gets stuff done is my motto, but I must admit that .NET is my go-to technology. Everything else I touch seems like a huge mess in terms of design, documentation, tools etc. I'm not saying that .NET is perfect, but at least someone spend some time on design before it's release and it has certain consistency that other projects rarely have.
- potta_coffee 5y agoNot that I need to have fun but .NET is the opposite of fun to me, in other words, painful. I'd rather not split hairs on what's right or wrong but the maximal OOP style of .NET's structure is just not for me. There's so much boilerplate that I don't need in other frameworks, and from what I've experienced, I'd need to buy in completely to the tooling and ecosystem to become productive, which means Visual Studio or similar IDE. In terms of functionality, the project I was last contributing to in .NET would have been much smaller and simpler in Go, Python or Javascript for the same set of features. I've built so many CRUD apps and APIs now that I can whip out these kinds of projects quickly with nothing more than a text editor. I just can't see any upsides for me to jump into .NET now. FWIW, I did try to give it a shot with an open mind, but shortly after that project I decided I'm not accepting any more .NET work.
- torginus 5y agoI just don't get why .NET is percieved as having a high learning curve - I mean it's probably non-trivial, but I hardly think getting into any other complex tech stack is easy. For example, I'm a newly minted C++ programmer as of 2 weeks ago - while the language is not that easy, my biggest struggle was getting everything to compile and link, and I felt like it's in a different class of difficulty. Another example, while node.js/Typescript is often seen as an easy language, I remember trying to set up webpack+scss+typescript+react+styled components + a zillion other made me very sympathetic towards Mr. Cobain's life choices. And another thing - I don't get the Microsoft is evil angle - I mean they are certainly no saints, but neither is any other FAANG company.
- bob1029 5y ago> I just don't get why .NET is percieved as having a high learning curve I feel like 99% of this is the historical perspective. If you dropped a totally new developer into a pure .NET 6 codebase w/ VS2022, I strongly suspect they would have a reasonable time of it. IMO, senior developers who stopped following tech news are the primary reason the community has to struggle with this perception today. There are shops where legacy .NET Framework 4.x solutions are being spun up today for no reason other than ignorance has taken hold. Arguably, the marketing disaster is still primarily Microsoft's fault, but I feel the community could do better with listening and adapting too.
- torginus 5y agoThat's understandable - I've just very recently had the 'privilege' of fixing something in a .net 4.5 project - everything, from the tooling, the testing, the baroque xml project format felt super complex, Visual Studio-centric and a huge downgrade from what I'm used to nowadays.
- ethbr0 5y agoMicrosoft has a bizarre habit of overcomplicating every@&$1ing thing in their ecosystems. I think because most of the features come out of customer request >> architecture plans. As a result, you end up with a billion different weird behind-the-scene links and requirements that didn't have to be that way and consume unnecessary cognitive load when working with it.