http://www.visualstudio.com/en-us/products/visual-studio-com... returns a 404.
Try this: http://www.visualstudio.com/en-us/products/visual-studio-com...
[deleted]
Microsoft takes .NET open source and cross-platform
761–770 of 937 posts
Re: Microsoft takes .NET open source and cross-platform
#762http://www.visualstudio.com/en-us/products/visual-studio-com... returns a 404.
Try this: http://www.visualstudio.com/en-us/products/visual-studio-com...
Hardware requirements: 20 GB of available hard disk space
Since we are here, could someone please explain me how is it that it takes so much space?
Re: Microsoft takes .NET open source and cross-platform
#763This demonstrates the importance of documentation in the framework wars. What could Microsoft possibly gain from open-sourcing .NET? They already have a few thousand great developers working on their jeweled prize, designed to lure developers to the brand as resolutely, and immutably, as possible. .NET going open source is Microsoft admitting that, despite its best efforts, developers still want to know whats going o…
To be fair, the source code for most of the core .NET libraries has been freely available under a "reference source license" for a very long time now. You could look behind the curtain, you just can't modify or redistribute.
So it was not really 'open' then, was it? More like "sources available for reading only" ..
Re: Microsoft takes .NET open source and cross-platform
#764Earlier quoted context omitted.
That might have been difficult, given that .NET is only 12 years old.
Oh aren't you so smug. I was at the 2000 PDC when they announced C#. We are now just shy of 2015. My 15 is more accurate than your 12.
Announcing occurs at vaporware stage. Realeasing is what makes it real. So do your math again.
Re: Microsoft takes .NET open source and cross-platform
#765I 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…
Until people understand the power and assistance that VS really gives you, it will mostly fall on deaf ears I think. The massive reduction in cognitive load w/ VS2013+ ReSharper is just astounding to me. Yet I've met, work with, and read opinions from people who claim it's a slow piece of crap dinosaur that does nothing but hinder development. You'll pry their Vim and Sublime from their cold, dead, brute-forcing hands.
Re: Microsoft takes .NET open source and cross-platform
#766Earlier quoted context omitted.
[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.
I'm a fan of C#, although I prefer F#; however I have to agree, I think the choice of for generic definitions was a real mistake, it can be so hard to parse. The side effect of this is that first-class functions (Func ) are chronically underused by C# programmers. Annoyingly F# brought them along for the ride too, although you rarely have to explicitly write them.
What would you have used for generic arguments? I think they work fine, and make use of Func often.
Re: Microsoft takes .NET open source and cross-platform
#767It is really a big news, I'm a .Net guy over couple of years. When i started with .Net i thought why i have to buy everything for development ? Now the day have changed and we found Microsoft in the open source community race. Thank you Microsoft.
Visual Studio is awesome, specially debugging when it is in Symbol server debugging.
Though i hate the thing 'Not Responding' and your OS is freeze. When your solution growing with 50+ project, it took 4-5min to open and by any chance if you click the solution it will hang.
Re: Microsoft takes .NET open source and cross-platform
#768Earlier quoted context omitted.
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…
async/await is HUGE. It opens an almost frictionless asynchronous pathway from your code all the way down to asynchronous capabilities of the underlying platform. Which was always the problem with leveraging async/overlapped IO: It was too complex and it turned your application logic inside-out because everything had to be performed in callbacks. async/await takes that on directly: You get everything executed in call…
Tasks are pretty awesome and just about as convenient as Go-routines. Now if we could just get typed channels in .Net >:]
Re: Microsoft takes .NET open source and cross-platform
#769Earlier quoted context omitted.
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…
async/await is HUGE. It opens an almost frictionless asynchronous pathway from your code all the way down to asynchronous capabilities of the underlying platform. Which was always the problem with leveraging async/overlapped IO: It was too complex and it turned your application logic inside-out because everything had to be performed in callbacks. async/await takes that on directly: You get everything executed in call…
Could you please contrast async/await implementation with Future in Java?
From the usability standpoint I see that they are more or less similar. However since you state that async/await exploits the asynchronous capabilities of the underlying platform I'm really curious to know how is this different from the way the way Future is implemented in a JVM.
Re: Microsoft takes .NET open source and cross-platform
#770Earlier quoted context omitted.
Silicon Valley is all OSS/Java. ElasticSearch, Hadoop, Cassandra, HBase, HDFS (mixed with C). Newer infrastructure for big-data are either Java, Scala, Clojure (one or two tools). Some of the startups also use Java (not all). I rarely see C#. So yes, C# is not catching up yet. Sorry, Eclipse + Ecosystems (that include plugins/integrations and whatnot) = beats VS any day (with or without pants). And if you have money,…
.NET is big in enterprise too, not just desktop.
People keep saying that Microsoft/.NET is "big" in enterprise but I have not seen real data.
If by "enterprise" you meant WalMart bought ten thousands license of Windows 7 OS for their workstation then sure...
But let me offer a different point of view: SAP, IBM, Tibco, Oracle, Salesforce (not too big yet but they are entrenched), NetSuite (same level with Salesforce), Workday. Mostly Java...