walsufnir on 11 January 2014
Cobretti2 said: I think this comment sums it up nicely on that site:
@peasoup IMO the key takeaway from this article isn't that the hardware underperforms, it's that a) Third parties are in the shit because they can't port easily to it while supporting the other systems and b) Nintendo needs better SDK tooling.
To work with Nintendo I think you have to Work With Nintendo in a way that's asking a lot of developers, both logistically and philosophically. Unity is an attempt to meet a lot of indies half-way, but for the rest of us wanting to adapt existing native tools to the platform, there are some real acrobatics to be done. For and my tiny team, we pull most of our income from other sources so it's more a labor of love than anything else that we choose to focus on the Wii U (tbh the weirdness of the platform actually makes it more fun for us), but I can fully understand why 3rd party giants like EA and Ubisoft don't really see the point. Also, a pet peeve of mine: Indies complaining about the weak CPU on a system when they are typically otherwise used to working with far worse CPUs on mobile, that they barely ever even attempt to or even CAN max out. Most devs simply have not earned the right to complain about the Wii U's horsepower. |
All excuses and explanations don't change _anything_ on the situation.