571–580 of 937 posts
Earlier quoted context omitted.
LINQ is _the_ only reason I tolerate .net
You mean C#? Let's keep those separate shall we? Linq makes C# much better, especially compared to java. It's a whole different story in F# though.
I'm a Haskell enthusiast, but it's not so good at Windows support, or libraries. I've been thinking F# might be just the ticket.
Earlier quoted context omitted.
What languages have you got experience with that you feel C# is the best language you have worked with? And what makes it such a good language for you?
Generics, Partial Classes, awesome Reflection API, Lambda syntax, LINQ, C/C++ compatibility, async/await, concurrency primitives, etc. I have worked with prettier languages, for instance I have picked up Haskell recently, I have also worked with faster languages, C was my forte for many years and I have worked with languages in the GSD category like Ruby and Python. C# is appealing not because of some feature that it…
Earlier quoted context omitted.
F# is elegant but ultimately held back by its lack of higher kinded types.
Held back from what? I mean, I'd love it even more if it had higher kinded types, but it's a pretty great language as is.
Just as Go is fine without generics, F# is fine without HKTs.
It's a sad realization for those coming from a language that does support HKTs. Still a great language.
Earlier quoted context omitted.
Too little, too late IMHO. Also MS has always come across as very opportunistic, giving the impression they will drop support for this if it serves them better.
What company is not opportunistic? They are by definition.
It's funny how Nadella has moved the needle more for developers in 9 months than Ballmer did in the last decade or so, and all that without running around like a madman too. Pretty good. I'll never switch back to MS for what they've done in the past but it is nice to see them try hard to become a nicer player in the software eco-system. Google and Apple need some other party to keep them sharp, it might as well be MS…
Seeing comments like this “I'll never switch back to MS for what they've done in the past” always reminds me of this post from Hanselman http://www.hanselman.com/blog/MicrosoftKilledMyPappy.aspx
He has so completely missed the deadly point that he's accidentally echoed it in his own post: Tons of people feel that Microsoft killed their Pappy.
Nadella's actions tell me one thing: the free software movement has threatened their bottom line.
This is not the time to back down, it's not the time to forgive and forget.
This is the time to review the Halloween Documents!
Earlier quoted context omitted.
I like Hanselman's blog a lot, but I found that post pretty disappointing. The reason there are a lot of people running around saying "Microsoft killed my pappy!" is because Microsoft actually did kill a lot of people's pappies, back in the day. When someone comes into town and shoots your pappy, it's not something you forget or forgive easily. The burden is on Microsoft to prove that they're not the same company as…
At this point there is literally nothing Microsoft can do to win these people over. They've done everything they could do short of porting the Windows UI to Linux (and even then... this and Powershell brings it pretty close). They're a huge contributor to open source, they support Linux pretty heavily on Azure, they open sourced their .NET as seen here, they listened to their customers on Windows 10, they're doing gr…
When a behavior gets institutionalized, it is likely to repeat more often than not. It requires exceptional evidence and time before for trust to be regained.
A person rises up in a typical institution by following and embracing its institutional patterns. When they have their back to the wall how unlikely are they to fall back on their old patterns, heck they neednt even have their back on the wall. Now if someone gets get screwed over by them, no ones more to blame than themselves. As they say, "fool me once ..."
It is entirely possible that someone else does similar damage to your business in an unethical way, but if one goes to a repeat offender and gets treated that way, the shame is on him / her.
Earlier quoted context omitted.
It's from the standard collections library, the most-used code in any language. It is in fact representative of the vast majority of code you use. The fact that it wasn't immediately clear to you that a lot of your code DOES use this code is probably the strongest argument I could make.
You have inferred more about me than you are entitled, and even if you were right, your argument is still poor. Have you read the c# stdlib? It is in no way any better. Stdlibs are always more complex than the code that builds on them, and that is by design. The same code that I use for a oneliner has to be robust enough to apply to play, akka, spark, finagle, etc. That is the primary reason why StdLib documentation…
This is huge. A few months ago, we decided to write a big new software component at $work, basically a service layer that is going to accumulate lots of business logic. We discussed several programming languages, and thought that a statically typed language might be a good fit (we mostly did perl and python so far). C# was dismissed pretty quickly, because .Net was closed source, and Mono had the reputation of being…
Earlier quoted context omitted.
This is a fairly weak and circumstantial list, in my opinion. Also, name a player that isn't equally or more abusive? If you mention Apple, Google, or Amazon, I'm going to disagree.
> This is a fairly weak and circumstantial list, in my opinion. That's fine by me. I think they should really wise up and start to play nice. If IBM could do it then Microsoft can too. > Also, name a player that isn't equally or more abusive? Why, does that excuse them? > If you mention Apple, Google, or Amazon, I'm going to disagree. I would agree with that myself, so I won't be naming those.