4 ms·
C# is probably my favorite language, although to be honest I don't have much experience with Ruby, Python, or Coffeescript. However, coding in C# (especially po
by InclinedPlane 14y ago
C# is probably my favorite language, although to be honest I don't have much experience with Ruby, Python, or Coffeescript. However, coding in C# (especially post v3.5) always feels like easy mode. You've got type safety but you've also got enormous flexibility with lambda expressions, extension methods, and so much other good stuff. And then the IDE becomes a real force multiplier instead of just a crutch to keep you from falling down as it can be with Java and other less savory languages, for example.
It'll be exciting to see how this affects the C# ecosystem.
Although it's even more interesting what this says about Microsoft's plans for the future of the CLR. It seems as though MS might be coming to the conclusion that it was a failed experiment, which is interesting given the success of other VM systems such as the JVM. It'll be interesting to see whether or not this move helps advance C# adoption outside of the windows platform.
- moreshoes 14y ago> C# is probably my favorite language, although to be honest I don't have much experience with Ruby, Python, or Coffeescript. http://i.imgur.com/iWBOL.gif http://i.imgur.com/iWBOL.gif
- duiker101 14y agoThis is not reddit/4chan/9gag or whatever, please avoid posting if you don't have any constructive thing to say. Also please read the guidelines http://ycombinator.com/newsguidelines.html http://ycombinator.com/newsguidelines.html
- moreshoes 14y agoNothing about this comment, short of your preference of C# over languages (and non-languages) you don't have any experience with, makes any sense at all. It's wild speculation based on a StackExchange question speculating on something that isn't even implied by a linked job listing. Microsoft has not, nor will they, come to the conclusion that the CLR was a failed experiment. As for the actual job listing, it has precious little consequence for anything or anyone, save for possible application speedups for certain use cases on certain architectures a few years down the road.
- orf 14y agoWhat exactly is wrong with the CLR? I agree with the first post - Python is my favorite language and I do love a bit of ruby now and again but I have to say that C# is pretty damn awesome when coming from an interpreted language background. Stuff like async/await, function blocks, lambdas and visual studio (which is hands down the best IDE I have used) is really cool.
- moreshoes 14y agoWhere did I write that anything was wrong with it? I was referring to the original comment, which speculates wildly based on nothing and its mother.
- InclinedPlane 14y ago> Microsoft has not, nor will they, come to the conclusion that the CLR was a failed experiment. It's easy to say that now, but time has a funny way of winkling out deeply seated truths that we try to shy away from. Trust me, I like the CLR, I used to work in DevDiv, it's close to my heart. However, one has to wonder if something is missing or not quite right. The CLR was originally a grand strategic play. It was intended to be everywhere, in Windows, in browsers, in game consoles, in phones, everywhere. And not just present everywhere but also underpinning all of these important products. A lot of the big projects to convert native code to managed code, such as in Windows, foundered and failed. Other than Microsoft.com most of the rest of Microsoft compiles their products to native code. Meanwhile, Windows has released its own "runtime" (WinRT) and windows mobile development is migrating toward native development as well. Not to mention the failure of silverlight to gain traction. The niche the CLR serves today is vastly diminished from the vision even 5 years ago. Also, they've tried to break out of their niche by making sweeping improvements to the CLR such as adding dynamic language support and such-like but they still seem to be stuck in the same rut as ever. Maybe the CLR will stick around forever, but given the trends it's looking increasingly likely that in, say, 10 years the CLR will be a bit like vb6. Still supported by default in every windows release but no longer fully embraced by the current tool chain.
- 14y ago
- RyanZAG 14y agoIs it just me who doesn't really like VS.net IDE? I like C#, but I would probably prefer to use something like netbeans or eclipse over VS.net. Mostly it's just how difficult and annoying it is to fix up a failed build. If you are trying to build something and it's failing because of strange 32bit vs 64bit incompatible libraries or any similar style of technical issues, you're left completely on your own with strange and vague build errors. On the pythin/java/ruby side this stuff is in fairly obvious config files and generally just seems to work. I can't be the only one who has run into this kind of stuff? Also, the docs/code completion just doesn't seem to work as nicely as in Java where everything has nice big easy to read document blurbs on every function. For example, Bitmap.create<ctrl+shift> and eclipse gives me an awesome popup with all the different versions and a big documentation window from JavaDoc about how exactly to use the function and when/when not to use it. With VS.net, I'm always having to go read up on MSDN pages in a browser which are poorly written. Just me?
- pjmlp 14y agoMost developers end up installing ReSharper or VisualAssist.
- roflc0ptic 14y agoI'm a junior developer who's been working with C#/.net/VS for about six months with very little guidance, so maybe take this with a grain of salt, but in my experience Visual Studio is regularly an impediment. We had a single with our setup project that took us a week+ of man-hours to resolve, stemming from someone opening a project up in VS 2010 instead of 2008, and then committing the changes. Almost every time I check out a project some of the assembly references are messed up. There are always more errors when I check out code than when I last checked in the project. It regularly takes me about half an hour to go from "Hm, let me fire up this project" to "okay, I'm at the breakpoint". In an environment where I'm working on like five projects, this seems nuts to me. Coming from python and php, the syntax highlighting is pretty sweet (but then, using the python REPL, I hardly needed it. It's sort of like "look at this problem you didn't have before that we solved!"), and I'm starting to understand why people like static typing, as it reduces certain classes of errors. I think I want to go back to python and Vim or Notepad++, though.
- silverbax88 14y agoI've worked with Java, C#, Ruby, Python and just about everything else at some point. C# is hands-down my favorite. I always describe it as Microsoft stole Java and then fixed all of the nonsense that made Java hard to work with.
- pjmlp 14y agoFor me it is just Delphi with a C like syntax and lots of FP goodness. :)