The people who come along later to scale to those millions of users your site attracted might.
Is there any (standard) technology stack that has proven to be unscalable?
Nobody really gives a damn what you built your site in (why I chose asp.net).
11–20 of 136 posts
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#12The people who come along later to scale to those millions of users your site attracted might.
Is there any (standard) technology stack that has proven to be unscalable?
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#13Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#14The 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
However, Joel Spolsky is a tool. Everyone I know and respect thinks he's a tool. He is a prime example of being successful because of being lucky, rather than being good. Do not quote Joel, he can't form a valid argument for a topic without circling back on himself to save his life.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#15Earlier quoted context omitted.
Is there any (standard) technology stack that has proven to be unscalable?
I recall twitter originally being written in something that proved unscalable, so they had to switch. Can't remember what it was though.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#16The 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…
Yes there are crappy c# developers. I've also seen some bad ass c#.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#17Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#18Earlier quoted context omitted.
Is there any (standard) technology stack that has proven to be unscalable?
I recall twitter originally being written in something that proved unscalable, so they had to switch. Can't remember what it was though.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#19Earlier 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.
Repeat after me, if your app doesn't scale it is YOUR fault, not a language, platform or framework. Scalability is about design and implementation, not what tools you use.
Re: Nobody really gives a damn what you built your site in (why I chose asp.net).
#20The people who come along later to scale to those millions of users your site attracted might.
It costs a ton upfront, and it's likely to kill your nascent company, but if you ever make it big, you'll save a tiny bit of money in the long run!