Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Did the Microsoft Stack Kill MySpace?

highscalability.com

Post reply on HN
Print view View original

41–50 of 206 posts

Re: Did the Microsoft Stack Kill MySpace?

#41

Post by lallysingh »

chaz wrote: post #16
mikeryan wrote: post #10

Its funny I don't know (can't think of one) of a high traffic site that "died" due to technical failures (particularly scaling failures). Twitter had massive problems during its growth phase, Reddit has had similar problems. Does anyone have an example of a site that got "killed" by technical issues? I'm really curious. Bad products tend to die or get replaced by superior offerings. Thats the nature of business. Not…

Friendster: http://highscalability.com/blog/2007/11/13/friendster-lost-l... VB: Can you tell me a bit about what you learned in your time at Friendster? JS: For me, it basically came down to failed execution on the technology side — we had millions of Friendster members begging us to get the site working faster so they could log in and spend hours social networking with their friends. I remember coming in to the offi…

To be fair to the rest of the industry, a single glance at the front page shows size of the TRANSITIVE CLOSURE of your social network.

Why would you do that?

This is bread & butter algorithm analysis. Don't put O(n^2) analyses on your most-loaded page.

Re: Did the Microsoft Stack Kill MySpace?

#42

Post by sajidnizami »

recoiledsnake wrote: post #35
sajidnizami wrote: post #32

Earlier quoted context omitted.

I too work with sites hitting high visitor count but I have to agree there with the article. Most .Net people I've interviewed think page load speed doesn't matter. They write code to satisfy the requirement and are quite good at it, but it ends there. Remember when people used ASP.Net web forms and it was hard to get rid of viewstate in the rendered page, and only the people who knew internals of platform well could…

>Most .Net people I've interviewed think page load speed doesn't matter. Have you informed them that you work with a high traffic site? Most intranet sites are not high traffic, so if they're spending time pre-optimizing for speed instead of features/development time, they're actually wasting the company's money. And what has viewstate got to do with SEO? You lost me. For SEO friendly URLs, all you need a is URL Rewr…

Something like this: http://stackoverflow.com/questions/1185984/is-viewstate-bad-...

Yes I talk to them that we have a high traffic site and we lose them because they don't know about building them. Besides you won't find many Microsoft stack sites dealing with scaling issues. I personally looked up Stackoverflow scaling case studies to design my solutions later.

Back in 2005/6 URL rewriting was still pretty difficult. I started out back then. I converted to MVC completely when 1.0 version came out specifically to address the SEO concerns.

But I guess our discussion is swinging to technical side :)

Re: Did the Microsoft Stack Kill MySpace?

#43

Post by billpaetzke »

jdavid wrote: post #30

I worked at MySpace on the MDP ( MySpace Developer Platform ) team. My team, MySpaceID, was the one that implemented Oauth 1, 2, 2.0a and all of the external REST libraries. We worked closely with the activity streams team and the OpenSocial Team. We also launched the MySpace JSL or MySpace Connect. We were the 1st to do a popup login flow for OpenID and several other cool things MySpace was doing to catch Facebook.…

By the way, if there's any MySpacers reading that got laid off or looking to jump ship...

I'm a developer at Leads360 in El Segundo, CA. We're hiring right now. I've already interviewed several MySpacers and have extended offers to a few. We hope to get more :)

Email me your resume, if interested: bpaetzke@leads360.com

Re: Did the Microsoft Stack Kill MySpace?

#44

Post by SpikeGronim »

brown9-2 wrote: post #37
jdavid wrote: post #30

I worked at MySpace on the MDP ( MySpace Developer Platform ) team. My team, MySpaceID, was the one that implemented Oauth 1, 2, 2.0a and all of the external REST libraries. We worked closely with the activity streams team and the OpenSocial Team. We also launched the MySpace JSL or MySpace Connect. We were the 1st to do a popup login flow for OpenID and several other cool things MySpace was doing to catch Facebook.…

Once the free parking was pulled from MySpace, 50% of every team was laid off and all of the momentum was pulled from the company. Can you explain what you mean by "free parking" here?

I believe that he's referring to the deal where Google paid MySpace for ad impressions. When that fell through MySpace lost a lot of revenue. http://www.dailyfinance.com/story/media/myspace-in-trouble-o...

Re: Did the Microsoft Stack Kill MySpace?

#45

Post by famousactress »

dandelany wrote: post #27

".Net programmers are largely Enterprise programmers whom are not constitutionally constructed to create large scalable websites at a startup pace." This is such BS, I can't even read it without physically cringing. I work for a ~400-person business that stands up .NET websites at breakneck speed, and we do it well. People who blame their problems on technical infrastructure decisions almost ALWAYS do so because it's…

.Net programmers are largely Enterprise programmers whom are not constitutionally constructed to create large scalable websites at a startup pace.

For the record, I think it's irrelevant.. but absolutely I think it's true. It doesn't mean .NET isn't capable, or that lots of .NET programmers aren't capable...

Just that .NET is way more popular in the enterprise than on the web, and that the work that gets done at most of those enterprise shops wouldn't fly on large sites.

It may be popular to pretend that the .NET camp (and to a slightly lesser extent, the Java Enterprise one) doesn't bend this way statistically, but they do.

Re: Did the Microsoft Stack Kill MySpace?

#46

Post by eru »

brown9-2 wrote: post #37
jdavid wrote: post #30

I worked at MySpace on the MDP ( MySpace Developer Platform ) team. My team, MySpaceID, was the one that implemented Oauth 1, 2, 2.0a and all of the external REST libraries. We worked closely with the activity streams team and the OpenSocial Team. We also launched the MySpace JSL or MySpace Connect. We were the 1st to do a popup login flow for OpenID and several other cool things MySpace was doing to catch Facebook.…

Once the free parking was pulled from MySpace, 50% of every team was laid off and all of the momentum was pulled from the company. Can you explain what you mean by "free parking" here?

I guess it comes from Monopoly?

Re: Did the Microsoft Stack Kill MySpace?

#47

Post by pixelbath »

recoiledsnake wrote: post #35
sajidnizami wrote: post #32

Earlier quoted context omitted.

I too work with sites hitting high visitor count but I have to agree there with the article. Most .Net people I've interviewed think page load speed doesn't matter. They write code to satisfy the requirement and are quite good at it, but it ends there. Remember when people used ASP.Net web forms and it was hard to get rid of viewstate in the rendered page, and only the people who knew internals of platform well could…

>Most .Net people I've interviewed think page load speed doesn't matter. Have you informed them that you work with a high traffic site? Most intranet sites are not high traffic, so if they're spending time pre-optimizing for speed instead of features/development time, they're actually wasting the company's money. And what has viewstate got to do with SEO? You lost me. For SEO friendly URLs, all you need a is URL Rewr…

SEOs prefer to have the "relevant content" as high on the page as possible. Since viewstate is just a large blob, many SEOs assume it decreases relevancy. I've never seen results that confirm this assumption.

Edit: See sajidnizami's post for the relevant StackOverflow question. Though, this still doesn't make sense to me logically. Why would a search engine disregard a (reasonably) longer page?

Re: Did the Microsoft Stack Kill MySpace?

#49

Post by kenjackson »

sajidnizami wrote: post #32
dandelany wrote: post #27

".Net programmers are largely Enterprise programmers whom are not constitutionally constructed to create large scalable websites at a startup pace." This is such BS, I can't even read it without physically cringing. I work for a ~400-person business that stands up .NET websites at breakneck speed, and we do it well. People who blame their problems on technical infrastructure decisions almost ALWAYS do so because it's…

I too work with sites hitting high visitor count but I have to agree there with the article. Most .Net people I've interviewed think page load speed doesn't matter. They write code to satisfy the requirement and are quite good at it, but it ends there. Remember when people used ASP.Net web forms and it was hard to get rid of viewstate in the rendered page, and only the people who knew internals of platform well could…

I too work with sites hitting high visitor count but I have to agree there with the article. Most .Net people I've interviewed think page load speed doesn't matter.

I find this shocking and somewhat unbelievable. My wife, who isn't a tech person at all thinks that page load speed matters (she just called so I asked her) -- and sites gmail as an example of a page that takes too long to load (I think that "loading..." indicator actually brings their load time to the forefront, although it really isn't that long).

I just have trouble seeing a .NET developer saying "for high volume sites page load speed doesn't matter", when most people who aren't in the tech industry would concede that it does.

Re: Did the Microsoft Stack Kill MySpace?

#50

Post by rchauhan »

Michiel wrote: post #4

tl;dr: No

I don't think its as much about the technology platform, as it is about following good development practices, and having a leadership that understands the value of following those practices. Good leadership can make poor technology competitive while poor leadership can screw up a good technology platform.
Post reply on HN