Jump to content

  • Log In with Google      Sign In   
  • Create Account


#ActualDaaark

Posted 01 November 2012 - 09:22 AM

be patient Posted Image

Years are passing.

It was obvious from the outside that XNA came from a small, mismanaged team, who didn't have a lot to work with. It was someone's pet project, and the company never really fully got behind it. People at MS have said that there were lots of politics, and a lot of their programming product teams were not co-operating with each other. It shows.

The Creator's Club subscription model was poorly thought out, and ass backwards. A lot of people in the MS customer support didn't even know what it was. Payments were constantly late, and numbers were missing. Game reviews relied on other gamers testing out and reviewing them before they could go up, because no one could bother hiring staff.

XNA got bastardized every time the marketing guys wanted to push something different on us. They added Zune support, wrote a bunch of stuff about programming for it, and then got us excited to all go out and buy Zune HDs. Then they quickly yanked the Zunes from the market and killed support for them in XNA. Way to pull the rug out from everyone. Anyone who spent time, money, and effort trying to do a good ZuneHD game got burned badly.

Then when Windows Phone 7 came out, they changed up the API again, and the 360 suffered for it. "Hey guys, remember those things the Xbox 360 GPU could do really fast in hardware? We dropped support for it so the API fit in better with WP7. Here's a new slow way to do it in software".

Then the team all got re-assigned to different projects, and stopped talking about XNA like it never existed.

So why be patient and why even bother?

When XNA existed, no one at MS knew what it was, why it existed, or where it was going. It was all reactionary, and the users got jerked around constantly. Years have passed, and MS still has nothing but bullshit answers to hand out. They only ever used XNA to treat like guinea pigs to test all their half baked ideas. I know the API team members cared about it, but the company as a whole didn't.

Go and use a stable API that knows what it wants to be and where it's going. Use an API that exists for the purpose of making software, and not product pitching.

#1Daaark

Posted 01 November 2012 - 09:20 AM

be patient Posted Image

Years are passing.

It was obvious from the outside that XNA came from a small, mismanaged team, who didn't have a lot to work with. It was someone's pet project, and the company never really fully got behind it. People at MS have said that there were lots of politics, and a lot of their programming product teams were not co-operating with each other. It shows.

The Creator's Club subscription model was poorly thought out, and ass backwards. A lot of people in the MS customer support didn't even know what it was. Payments were constantly late, and numbers were missing. Game reviews relied on other gamers testing out and reviewing them before they could go up, because no one could bother hiring staff.

XNA got bastardized every time the marketing guys wanted to push something different on us. They added Zune support, wrote a bunch of stuff about programming for it, and then got us excited to all go out and buy Zune HDs. Then they quickly yanked the Zunes from the market and killed support for them in XNA. Way to pull the rug out from everyone. Anyone who spent time, money, and effort trying to do a good ZuneHD game got burned badly.

Then when Windows Phone 7 came out, they changed up the API again, and the 360 suffered for it. "Hey guys, remember those things the Xbox 360 GPU could do really fast in hardware? We dropped support for it so the API fit in better with WP7. Here's a new slow way to do it in software".

Then the team all got re-assigned to different projects, and stopped talking about XNA like it never existed.

So why be patient and why even bother?

When XNA existed, no one at MS knew what it was, why it existed, or where it was going. It was all reactionary, and the users got jerked around constantly. Years have passed, and MS still has nothing but bullshit answers to hand out. They only ever used XNA to treat like guinea pigs to test all their half baked ideas.

Go and use a stable API that knows what it wants to be and where it's going. Use an API that exists for the purpose of making software, and not product pitching.

PARTNERS