Live data from Hacker News

Source code of ASP.NET

github.com

31–40 of 104 posts

Re: Source code of ASP.NET

#31
post #23
post #5

Earlier quoted context omitted.

Too little? Biggest change for ASP.NET from release of ASP.NET! "Too much of pain" was the first (and last) thing I said when trying to configure ruby on ubuntu. Or tried to download some app and run it.

I think Hudo's point is that experience with technologies is subjective. I loathe Windows after having been comfortable in terminal, and I loathe Eclipse after having been comfortable in VS.

I've gotten apps working on .net and ubuntu -- configuration was a drag in both, but it works, and isn't the entire basis for loving or hating a platform. So what I'm saying is I agree with your comment.

The catch here (and point) is why should you have to switch from VS at all? If it's a real source code editor shouldn't it handle Java, Clojure, Haskell, Python, Ruby, JavaScript, etc all just fine? Some of the oldest and free editors do and do it well. I realize MS has an agenda (perhaps) or they've de-prioritized any of these features into oblivion -- but who are they serving, I certainly didn't feel it was me even after giving them a lot of $ for VS.

Re: Source code of ASP.NET

#32
post #30
post #17

Earlier quoted context omitted.

I don't understand the thinking behind phrases like "too little, too late" about a company whose tooling will likely span the entire careers of a number of generations of developers.

I say that a lot and I feel like .NET is loosing relevance. Embracing open source and making Linux a first-class citizen in the eco system would be the only way for .NET to increase adoption or stay technologically relevant, and unfortunately its happening too slow.

Too slow for what? Are you suggesting that .NET technology is traveling on a steady path towards becoming irrelevant?

Re: Source code of ASP.NET

#33
post #5

Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.

Too little? Biggest change for ASP.NET from release of ASP.NET! "Too much of pain" was the first (and last) thing I said when trying to configure ruby on ubuntu. Or tried to download some app and run it.

Really?

`sudo apt-get install ruby` was too much for you?

You just make yourself sound dumb when you say shit like that.

Re: Source code of ASP.NET

#34

Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.

This just in, people who aren't impressed by the .NET stack still aren't and continue to not use it.

I don't think some of them even use their preferred development stacks, they are too busy telling you how they don't use .NET.

Re: Source code of ASP.NET

#35
post #25
post #22

Earlier quoted context omitted.

Yeah, I noticed that too. It would seem that my co-worker who thinks MVC is a fad is at odds with MS themselves.

ASP.NET MVC is no longer a fad - a lot of the job openings I'm seeing are asking for it.

Id say its safe to say webforms is dead. The only job openings for it now are legacy systems.

Re: Source code of ASP.NET

#36

Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.

And what is impressive? Still rocking that LAMP stack, mate?

Re: Source code of ASP.NET

#37
post #30
post #17

Earlier quoted context omitted.

I don't understand the thinking behind phrases like "too little, too late" about a company whose tooling will likely span the entire careers of a number of generations of developers.

I say that a lot and I feel like .NET is loosing relevance. Embracing open source and making Linux a first-class citizen in the eco system would be the only way for .NET to increase adoption or stay technologically relevant, and unfortunately its happening too slow.

How is .NET losing relevance?

You can make mobile apps with Xamarin, and apps for any desktop OS thanks to Mono.

You can make high-quality 2D/3D games with Unity

You can make high-performance web applications with ASP.NET + IIS.

Re: Source code of ASP.NET

#38
post #30

Earlier quoted context omitted.

I say that a lot and I feel like .NET is loosing relevance. Embracing open source and making Linux a first-class citizen in the eco system would be the only way for .NET to increase adoption or stay technologically relevant, and unfortunately its happening too slow.

Too slow for what? Are you suggesting that .NET technology is traveling on a steady path towards becoming irrelevant?

Yes. Most users of .NET is in the enterprise (as opposed to tech and startups) and Java has positioned itself as the go-to platform for big data analytics and processing.

I think this comes down to clinging to an antiquated product model. A lot of the technologies that are seeing rapid adoption are open source and driven by transparent communities. In some cases companies back them (e.g. cloudera, datastax, 10gen, typesafe).

Re: Source code of ASP.NET

#39
post #37
post #30

Earlier quoted context omitted.

I say that a lot and I feel like .NET is loosing relevance. Embracing open source and making Linux a first-class citizen in the eco system would be the only way for .NET to increase adoption or stay technologically relevant, and unfortunately its happening too slow.

How is .NET losing relevance? You can make mobile apps with Xamarin, and apps for any desktop OS thanks to Mono. You can make high-quality 2D/3D games with Unity You can make high-performance web applications with ASP.NET + IIS.

Sure you can, but the technology of the future is not being built or run on windows stacks. You find it everywhere in the enterprise, yet almost every big new tech company that has come up in the last 10 years all rely primarily on open source technology.

Re: Source code of ASP.NET

#40

Too little, too late (imo). I'll think about it again once they have visual studio and all the good things running on *.nix. It's too much of a pain to get anything to work with a .net project, and then deploy on anything other than IIS.

I believe one of the big changes in ASP.NET vNext is the ability to deploy outside of IIS.

Other types of projects, notably WebAPI, have been able to easily deploy outside of IIS for years. I actually just converted two WebAPI projects to self-hosting. It took about a day, which is not bad considering that includes time to learn what I was doing and reworking an existing deployment process.

Post reply on HN