Live data from Hacker News

C# is the past, the present and the future

blog.filipekberg.se

41–50 of 57 posts

Re: C# is the past, the present and the future

#41
post #36

This article has a great title. Would have been nice if there was a bit more content to it; maybe we wouldn't have ended up with a bunch of hostile comments with spelling mistakes. So let's give it a go. An opinionated past, present, and future for C#: The past: .NET emerged seemingly in 2002/2003 with a feature set similar to Java. This was pre-generics, and all code written in C# in this era is alien and involves a…

> which Sun had sewed the crap out of them for Speaking of spelling mistakes...

Oops. I wonder if that makes me guilty of libel or slander.

Re: C# is the past, the present and the future

#44

"I am a Software Engineer working with various techniques such as C#, WPF, WCF, ASP.NET MVC, ASP.NET and much more" "I spend most of my days working with the latest technologies from Microsoft." "In the darkest alley-ways we still have the people not wanting to touch C# with a pitch-fork because it’s behind Microsoft" In my opinion he lacks enough neutrality to make that statements(how he know MS tech is so great if…

One problem with your statement is that C# is not only "Microsoft tech". C# is an ECMA language for crying out loud.

Re: C# is the past, the present and the future

#45
post #9

The article is very scarce on content. This could have been a tweet. Also, saying "C# was here to stay from the beginning, we love it in the present and we will use it more and more in the future." wouldn't convince many people. In my view, the future of C# is hanging in the balance. Microsoft has lost significant mind share, and I am not sure if Windows is a good platform anymore to write new apps.

I have to agree, it occurred to me the other day that my almost one year old daughter might never have a Windows computer, in the same sense that people 10 years younger than me simply never had an MS-DOS one, except this time Microsoft didn't build the next platform.

Totally dude. Because C# only runs on Windows. You can't use it to build apps for the iPhone, Android, OS X or Linux at all. Nope.

Re: C# is the past, the present and the future

#46
post #31

Earlier quoted context omitted.

There are real companies out there making real money off Mono. So it's not a toy reserved for weekend tinkering. Enough companies trust Mono to use it in production.

That's news to me. Not that I disbelieve. Really interested. Can you point me to some use cases? Why do they not just use Windows?

Mostly on mobile I would guess. Xamarin has a showcase on their site: http://xamarin.com/apps .

Also every game made in Unity is using Mono, which is _a lot_ of games. The Playstation Vita and Wii U uses Mono as well for third party development.

Re: C# is the past, the present and the future

#47
From my limited perspective, C# hasn't changed much apart from syntactic sugar (less typing!) since generics were added in v2.0. This is similar to all the stuff Microsoft throws into their C++ compiler to make COM more user-friendly.

Most of the additions have been to the CLR, where Microsoft has earned a reputation for changing behavior in the 'green' bits (meaning: supposedly unmodified) when updates are installed. Also, Windows 8 brings the new WinRT; it's impossible to know how long either runtime will be 'the one true way' (see Silverlight).

It's hard to get behind a software development tech created by a company that makes its money selling new versions of operating systems and development tools (the cool stuff always requiring the latest versions, of course!). Microsoft is always moving the cheese.

Re: C# is the past, the present and the future

#48
post #45

Earlier quoted context omitted.

I have to agree, it occurred to me the other day that my almost one year old daughter might never have a Windows computer, in the same sense that people 10 years younger than me simply never had an MS-DOS one, except this time Microsoft didn't build the next platform.

Totally dude. Because C# only runs on Windows. You can't use it to build apps for the iPhone, Android, OS X or Linux at all. Nope.

Mono is an option for the current generation to learn one less language. Outside of Windows it's not the default language for anything except Unity3d so curious kids who grow up with tablets might not have much reason to learn it.

Re: C# is the past, the present and the future

#49
post #45

Earlier quoted context omitted.

Totally dude. Because C# only runs on Windows. You can't use it to build apps for the iPhone, Android, OS X or Linux at all. Nope.

Mono is an option for the current generation to learn one less language. Outside of Windows it's not the default language for anything except Unity3d so curious kids who grow up with tablets might not have much reason to learn it.

So, nobody should learn a language unless it's the "default language" for a platform? What is Python, Ruby or PHP the default language of? Should anybody be learning Perl, Haskell or Objective-C in your opinion?

Re: C# is the past, the present and the future

#50
post #10

C# and .NET were designed to sell Microsoft Windows Servers, C# = Microsoft and any side project like Mono can be shut down any time. Microsoft did not become what it is by embracing open and free technologies unless it was to "extend and extinguish them", if you dont pay for a product one way or another there is no reason for Microsoft to support that product. C# is a good language but definetly not the future.

Microsoft has been making some decent moves into open and free as of late. The biggest thing lately, that I can think of, was their open sourcing of the entire asp.net stack:

http://aspnet.codeplex.com/

http://aspnetwebstack.codeplex.com/

Post reply on HN