Earlier quoted context omitted.
Everytime I see someone talking about "unlimited" something my spider sense ticks off. Except for Google, Amazon and some other big guys, most of companies will worry about lots of things before what you mentioned become a problem. Also, AWS, Azure and AppHarbor have takem the license problem out of the way.
AWS doesn't really take the license problem away -- it just rolls the cost into the price of the instance, which is significantly higher for Windows.
6 Months with C#
51–60 of 84 posts
Re: 6 Months with C#
#52Overall though, Microsoft is trying to move to an "ecosystem" platform. Exampes are Nuget powering their closed/open-source ecosystem for projects and Azure server templates. Even their latest ASP.NET MVC 4 is pushing several open source libraries onto their default project template. They truly see they couldn't win the web battle with WPF/Silverlight as their only options, so they are going for a different angle here in the last year. Additionally, a lot of interesting things are coming out of Microsoft and its employees, such as the open-sourced SignalR which is actively being updated and may become a standard for C# webapps.
I realize C#/.NET is not the go-to language for small web-apps yet, primarily due to licensing, but give it time. I say if you are on the fence, and are interested at all in C#, give it a shot! There are many free options for development IDE's and hosting provided by Microsoft. For example, you can use Visual Studio Express and host up to ten websites for free on Azure.
Re: 6 Months with C#
#53Earlier quoted context omitted.
I'm a huge fan of Miguel and the rest of the Xamarin crew, and I'd love to see a universal implementation of the CLR take dominance. I think maybe 5 years ago the CLR had a real chance to win in the battle of multi-language runtimes, but at this point I think the war is going to the JVM. (Chalk that up to yet another short-sighted decision by Microsoft.) The problem is that Java (the language) completely dominates th…
I agree with what you're saying, but without a proper implementation outside of Windows, the CLR is currently a place where great languages go to die. Mono is functional, but is basically unsupported (for everything but mobile).
No, F# is completely supported by MS. And that's the problem with the alternative languages on the JVM. Decision makers are wary of anything that isn't officially supported by Oracle. There are other problems with languages like Scala and Clojure that have nothing to do with official support, but that's another story.
The mono story is an interesting one. At first people thought it would allow cheap deployments of ASP.NET on Linux servers, but it's really carved out a niche for itself on the linux desktop, in gaming (Unity, Sony's dev kits), and now mobile. What's funny is the JVM is completely irrelevant on mobile, compared to .NET/Mono. Just now Oracle is pulling their heads out of their asses and trying to get the JVM to work on iOS.
Re: 6 Months with C#
#54Microsoft is trying too hard to make C# answer to every single technology trend, adding dynamic type, asynchronous methods, etc. In most cases you wind up with a working but much worse alternative to the real thing. For example, here's how you create an anonymous function that returns a string in C#: (new Func (() => { return "foo"; }))(); That's pretty awful and as a result you rarely see anyone doing stuff like tha…
Re: 6 Months with C#
#55Microsoft is trying too hard to make C# answer to every single technology trend, adding dynamic type, asynchronous methods, etc. In most cases you wind up with a working but much worse alternative to the real thing. For example, here's how you create an anonymous function that returns a string in C#: (new Func (() => { return "foo"; }))(); That's pretty awful and as a result you rarely see anyone doing stuff like tha…
()=>"foo"
?Re: 6 Months with C#
#56Microsoft is trying too hard to make C# answer to every single technology trend, adding dynamic type, asynchronous methods, etc. In most cases you wind up with a working but much worse alternative to the real thing. For example, here's how you create an anonymous function that returns a string in C#: (new Func (() => { return "foo"; }))(); That's pretty awful and as a result you rarely see anyone doing stuff like tha…
eh? How about ()=>"foo" ?
Re: 6 Months with C#
#57Earlier quoted context omitted.
Why are all people assuming Windows is gui only? You can script practically anything using powershell and multi server management using powershell remoting. System center + ad group policy is light years ahead anything else.
Because almost no one actually does that, despite it existing, and tools and documentation for it on the net are very sparse.
Re: 6 Months with C#
#58Earlier quoted context omitted.
I've been a fan of Mono for a long time; unfortunately, we've had a lot of trouble trying to scale it in production. Our application was originally built for .NET (on Windows). It was successfully ported to Mono, but we continue to have strange problems (machine load average going to 50+ and becoming unresponsive, etc.) which we believe are related to the Mono GC. After spending a good amount of effort trying to fix…
I'm a huge fan of Miguel and the rest of the Xamarin crew, and I'd love to see a universal implementation of the CLR take dominance. I think maybe 5 years ago the CLR had a real chance to win in the battle of multi-language runtimes, but at this point I think the war is going to the JVM. (Chalk that up to yet another short-sighted decision by Microsoft.) The problem is that Java (the language) completely dominates th…
I think that's pretty much wrong.
Despite Microsoft shipping F# support in their main IDE, pretty much no one uses it. Can you name one popular library which switched from C# to F#?
Compare that to e. g. Scala: Huge amount of adoption compared to F#, despite _not_ shipping with any IDE by default. One of the most popular Java web frameworks switched from Java to Scala recently.
Even the F# “elite” is aware of it and complaining about how Scala has a a lot higher adoption (and a larger ecosystem and more developers, libraries, conferences, user groups, support, ...), so I'm a bit surprised by your statement.
Re: 6 Months with C#
#59Earlier quoted context omitted.
AWS doesn't really take the license problem away -- it just rolls the cost into the price of the instance, which is significantly higher for Windows.
And will only become a problem when you reach a huge scale. If by that time it is still a problem then maybe your problem is not having a good enough business model.
Re: 6 Months with C#
#60Earlier quoted context omitted.
I agree with what you're saying, but without a proper implementation outside of Windows, the CLR is currently a place where great languages go to die. Mono is functional, but is basically unsupported (for everything but mobile).
the CLR is currently a place where great languages go to die No, F# is completely supported by MS. And that's the problem with the alternative languages on the JVM. Decision makers are wary of anything that isn't officially supported by Oracle. There are other problems with languages like Scala and Clojure that have nothing to do with official support, but that's another story. The mono story is an interesting one. A…
You're right that the JVM itself is irrelevant on mobile, but via Android the Java ecosystem still plays a role.