Earlier quoted context omitted.
Is there any (standard) technology stack that has proven to be unscalable?
Yes. The one you started out with is always unscalable.
Can you please explain that?
Nobody really gives a damn what you built your site in (why I chose asp.net).
21–30 of 136 posts
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#22Earlier quoted context omitted.
You almost always have to rewrite your whole system anyway to scale to millions of users. It doesn't matter whether it's PHP, Python, C++, or ASP.NET; it'll have to be rewritten. The real problem is the flip-side of something that the OP mentioned as an advantage: ASP.NET coders tend to be cheaper, less experienced, and hence less likely to know about some critical detail that'll boost adoption, whether it's usabilit…
To me this sounds like my friends who didn't want to go to UT because it 'was too big'. The awesome thing about too big is that if you look hard enough you are almost assured of finding someone like you. Yes there are crappy c# developers. I've also seen some bad ass c#.
Right, "biasing your talent pool" doesn't mean that everyone in that talent pool sucks. There are certainly some very talented C#/.NET devs.
The problem is that when you go to hire, you have very little information about just how badass a prospective dev is, unless you've worked with them before. So if you take a random dev out of the C# pool, chances are he'll be worse than a random dev in the Python pool.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#23The people who come along later to scale to those millions of users your site attracted might.
You almost always have to rewrite your whole system anyway to scale to millions of users. It doesn't matter whether it's PHP, Python, C++, or ASP.NET; it'll have to be rewritten. The real problem is the flip-side of something that the OP mentioned as an advantage: ASP.NET coders tend to be cheaper, less experienced, and hence less likely to know about some critical detail that'll boost adoption, whether it's usabilit…
I'm curious how you conclude that ASP.NET developers suck ... there's a lot of shit programmers in all languages out there, that's why everyone's looking hard to find the rockstars/ninjas/whatevers.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#24> It’s not about the quality of the talent. It’s a simple supply and demand question.
Uh oh. "Programmers are a commodity" again.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#25Earlier quoted context omitted.
Yes. The one you started out with is always unscalable.
Can you please explain that?
When you start out, you're designing your site in hopes that someone other than your mom is going to use it. Usually, all you need is an app server and a database. I you get successful, that won't cut it. You usually need to start adding more and more pieces and rethink some technology decisions you made originally.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#26The people who come along later to scale to those millions of users your site attracted might.
You almost always have to rewrite your whole system anyway to scale to millions of users. It doesn't matter whether it's PHP, Python, C++, or ASP.NET; it'll have to be rewritten. The real problem is the flip-side of something that the OP mentioned as an advantage: ASP.NET coders tend to be cheaper, less experienced, and hence less likely to know about some critical detail that'll boost adoption, whether it's usabilit…
Not if you use http://helma.org (SSJS), it has a build in ORM that caches results. 1 machine 2 GB ram serves 30 million hits per month.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#27The people who come along later to scale to those millions of users your site attracted might.
This is what I don't get. ASP.NET scales pretty well as Joel opines. Why do people think .NET is bad just because it feels enterprise-y? More: http://www.youtube.com/watch?v=NWHfY_lvKIQ
My beef with ASP.NET is that it makes it disturbingly easy to write code that doesn't scale well and then is ridiculously hard to scale after the fact.
It really is all about the initial design not the language. ASP.NET just makes it too easy to go with bad design and library choices, not to mention the tons of examples of bad design that newbies might accidentally follow at the beginning.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#28Earlier quoted context omitted.
You almost always have to rewrite your whole system anyway to scale to millions of users. It doesn't matter whether it's PHP, Python, C++, or ASP.NET; it'll have to be rewritten. The real problem is the flip-side of something that the OP mentioned as an advantage: ASP.NET coders tend to be cheaper, less experienced, and hence less likely to know about some critical detail that'll boost adoption, whether it's usabilit…
I'm curious how you conclude that ASP.NET developers suck ... there's a lot of shit programmers in all languages out there, that's why everyone's looking hard to find the rockstars/ninjas/whatevers.
You're looking for developers who have faced the problems that a typical web startup is likely to have faced as it grows and gains users. It is naturally easier to find those developers if you write it in a language that those current hot web startups frequently use.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#29Whatever you chose - is it really a good plan to write an article that amounts to "my startup was written by somebody who's new to coding in general. And the whole point is to flip it" ?
(Yes, I believe "exit strategy" is a fancy word for "built to flip".)
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#30Although I agree with the point that customers don't give a shit about the technology stack, did it seem to anyone else that he may be a little self-conscious about his choice of choosing ASP.NET? Read every single point. They all mention why he chose ASP.NET.
Edit: why the downvotes? I'm not saying that ASP.NET is a bad language. I'm just saying that his title doesn't agree with what he wrote.