40 ms·
Good post. It's funny, because C# has been ubiquitous for a long, long time - just not in cool areas like the startup scene. I was a C# web dev for years before
by untog 12y ago
Good post. It's funny, because C# has been ubiquitous for a long, long time - just not in cool areas like the startup scene. I was a C# web dev for years before moving onto using Node or Ruby as a backend in order to be able to work on more interesting projects.
I look forward to a future where C# is more ubiquitous, because, as the post states, this will largely come at the expense of Java, which has always felt like C# Only Not Quite So Good. Cross-platform these days means a lot of mobile work, and if we can write our server backends, iOS Apps and Android apps in one language that's a big win.
- serve_yay 12y agoI used C# for a long time before moving on as well. Mostly web stuff, but also desktop software and services (Windows equivalent of a daemon). I always really liked the language, and the libraries are mostly pretty good, but it being tied to Windows and especially IIS was always a real problem. But I think .NET has also long suffered from a more anemic ecosystem than other platforms have. Things like a package manager have just recently come around. Things like tooling and educational resources seem more spotty than for other platforms. (Although some of the for-pay .NET tools are really, really nice.) So, I too would like to see it used in more interesting ways than line-of-business desktop/web apps. But I wonder how the above things will play out. I'm really glad it's not so tied down to Windows anymore. But maybe there are other issues to resolve, now.
- tracker1 12y agoI'm just hoping that the stability and ease of deployment approaches what it is on windows for server-side apps. Also, I wonder where VS will wind up with all of this. If I could use VS on OSX or Linux that would be my preference at this point. I'd looked into mono (mod-mono/fcgi) a number of times, and it was always painful, with some performance/stability issues, and in the end worth the server license to just not deal with it. For the past few years, I've been doing more node work than .Net and loving it. That said, I wouldn't mind doing some pieces in C#/.Net because it has a lot of niceties as well. It's generally the "enterprise" tooling, and excessive use of design patterns that has made it more painful in practice. Good times indeed.