Oregon legalized marijuana on Tuesday. Microsoft open sources .NET today. They say miracles come in 3. What's next?
Microsoft takes .NET open source and cross-platform
471–480 of 937 posts
Re: Microsoft takes .NET open source and cross-platform
#472Earlier quoted context omitted.
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
- Stacker - Netscape - SCO And many others besides. Companies have reputations just like people do (that's why we call them 'incorporated') and just like you can lose your trust in a person you can lose your trust in a corporation. This is not about Microsoft just doing 'stupid stuff sometimes' it is about institutionalized criminal behavior sanctioned at the highest level of one of the largest software companies in…
Software patents, including Stacker's, are far more destructive to innovation than anything Microsoft could ever do on its own.
SCO, well... OK, there's no way to spin that as anything but evil.
Re: Microsoft takes .NET open source and cross-platform
#473I feel like the last couple years I've been cheerleading for MS and telling people how much they've changed, how open things are becoming, and how awesome the development experience is. It's fallen on deaf ears or met with resistance, but today's announcements are really gonna drive the point home. Developers need to start looking more seriously at C#/.Net. The Scotts (Hanselman/Guthrie), Miguel De Icaza and so many…
> Developers need to start looking more seriously at C#/.Net. I don't think they need to. They might if they have some particular need in it, but there are way more interesting things to learn if you are interested in something new, like Rust of example.
Re: Microsoft takes .NET open source and cross-platform
#474I am, of course, happy to see it. But, let's not get too excited about what good Open Source citizens Microsoft have become. Let's let their actions going forward determine that.
Re: Microsoft takes .NET open source and cross-platform
#475Re: Microsoft takes .NET open source and cross-platform
#476It'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…
The process to open source .NET would have almost certainly started before Nadella became CEO. There's no way they decided to release the source and have it ready within 9 months.
Re: Microsoft takes .NET open source and cross-platform
#477Earlier quoted context omitted.
"C# is one of the best languages out there for generic enterprise work and app development" - i see you have great tools if cs is soooo good.
For enterprise work I'd actually agree that nothing beats C#. I also love Haskell, but let's be honest - it won't get me hired, or at least not here in Bulgaria.
Re: Microsoft takes .NET open source and cross-platform
#478Earlier quoted context omitted.
> I'm not sure Best Buy reflects that poorly on Microsoft. Best buy didn't enter into it, you probably did not fully read the link. This was about Romania, not about the USA. > Again, doesn't reflect that poorly on Microsoft. It does, because IV is best described as a patent troll in a nice suit. > Is a software sales company supposed to not sell software? That's what they do. How does that reflect poorly on them? Be…
1. A Microsoft distributor != Microsoft. 2. Every major tech company is involved with IV, so stop shitting on just Microsoft. Go troll and derail someone else's comments. 3. That's called selling. I'm not going to argue with a nutjob anymore. I'm happy you're happy, and your original comment wasn't offensive. What is offensive is people like you (including you) constantly pulling this shit. Just ignore it. Just move…
Ah ok, that explains it. 'Nutjob', 'Asshole', when arguments fail resort to namecalling. I've got nothing against you, but I have my personal reasons for disliking Microsoft, I don't know what it is you want from me but you seem to be taking this a bit too personal. Try not to associate too much with your favorite brands, lest someone would start to think you have a stake in this.
Note that I'm here with my full name and rep out in the open whereas you're the HN equivalent of an anonymous coward.
Pot, Kettle, etc.
Re: Microsoft takes .NET open source and cross-platform
#479Earlier quoted context omitted.
You find C# harder than this? trait SeqLike[+A, +Repr] extends Any with IterableLike[A, Repr] with GenSeqLike[A, Repr] with Parallelizable[A, ParSeq[A]] { self => or def :+[B >: A, That](elem: B)(implicit bf: CanBuildFrom[Repr, B, That]): That
[SerializableAttribute] [ComVisibleAttribute(false)] public class Dictionary : IDictionary , ICollection >, IDictionary, ICollection, IReadOnlyDictionary , IReadOnlyCollection >, IEnumerable >, IEnumerable, ISerializable, IDeserializationCallback Both languages can be difficult to decipher. I do find that Scala's syntax is much more flexible, which can lead to more stumbling when trying to read code.
Re: Microsoft takes .NET open source and cross-platform
#480Earlier quoted context omitted.
>At the end of the day, this is a huge inner-framework anti-pattern over the same procedural syscalls that every other language handles procedurally. No, you have a tiny, very simple type that allows for type safe IO. It also happens to make haskell a more powerful imperative language than most imperative languages, as IO actions are first class and can be passed around and manipulated like anything else. >So, basica…
To be fair, understanding I/O in Haskell takes quite a bit of mental gymnastics. :) The I/O monad modifies the Universe that contains the set of all functions that comprise your program (if I even understand the concept correctly).
That sounds rather complicated. My way of thinking of it is simpler than that. a -> IO b is just a function from a to b that can do some I/O. Nothing more complicated than that.