Inside the PlayStation Suite SDK
New submitter Serapth writes "Sony recently released the PlayStation Suite SDK to open beta. Using PSS, people are able to write games for various PlayStation certified devices in a C#/Mono based environment. This post takes a look at what's included in the SDK, which, surprisingly, is quite a bit."
...but I'm guessing "respect for the customer" was one of the things left out.
I heard Sony was determined to forge a coherent, integrated strategy, but now I see that their phones (some of which are PS certified) are all Android based, but the PSS is mono/dotNet based. What's going on there?
Can anyone be a developer?
We can't provide detailed information at this stage, but we are now making the necessary preparations to allow developers to smoothly move through the contract stage. We will post information on this website as it becomes available.
...it's probably never going to make you a penny developing for these devices.
There was a time that I worked for a video game publishing company and Sony's testing software had ZERO ZIP ZILTCH documentation. Specifically I worked on the online department. Microsoft had its Network Emulator for Windows Toolkit (NEWT) and Sony had its equivalent. It was backwards, awkward, and for a period time didn't event work (this was also around the time of the Sony network being hacked so we couldn't even release our titles if we wanted to). Figuring out how to hook their software up to our PS3s, let alone monitoring, was a GOD-DAMNED-NIGHTMARE.
People dreaded being assigned to work on the PS3 for version reasons just like this (among some others).
No PS3 support. Only one device (PS Vita) that has a chance to be ever used by anyone.
Windows-only release based on Mono (and loudly proclaimed announcement that not even OSX will be supported).
Proprietary language controlled by a major competitor (yes, it is proprietary -- C and C++ are open, C# is proprietary).
2D only.
Free (in either meaning of the word) applications and games are not allowed.
Sony reserves the right to prevent anyone from using it after beta.
Everyone who will be allowed by Sony to use it after beta, has to pay Sony.
That's like Nokia and Sony had a baby.
Contrary to the popular belief, there indeed is no God.
The same thing could be said about most open source software, you would have a better chance of making money if the end result was exclusively offered in a market place.
If you made a game using PSS and it was published the only scenario I can think of where there would be no pennies involved would be as a result of zero sales.
xperia play, sony's tablets, and a bunch of se phones, recognize them all.
general android deployment would be a big plus though, now the biggest selling point is the built in libs and the ability to target vita.
world was created 5 seconds before this post as it is.
Sony are infamous for being crap and dev support. A friend who has worked on a number of game projects says that they hate dealing with Sony. When they hit an issue developing for Xbox, they email MS and get a reply, often with a code snippet/workaround and by the end of day, On the other hand, they have to chase Sony over and over and eventually, weeks later get an email saying 'Look in the documentation'.
I want a list of atrocities done in your name - Recoil
Sure, but ask your average consumer what they are and you'll just get a funny look. Contrast that reaction to the fact that iPhone and Android are now household names in most 1st world countries and you start to see why developing software for them is pointless.
..... It will be removed without contemplation.
Bitch please.
They dug their grave, and now it's time to lie in it.
[Qt's system of signals and slots] does not belong in the language standard. There is nothing wrong with it being handled by a preprocessor, it just should not be in the language.
"Likewise, C++'s system of templates and classes does not belong in the language standard. There is nothing wrong with it being handled by Cfront, it just should not be in the C language." Would you agree with this as well?
If a general-purpose macro mechanism could be made (C++ already has two, C preprocessor and templates) so slots/signals can be implemented on top of it, that macro mechanism can be allowed in the language.
When Qt was first created, C++ compilers were defective; templates were not reliable across different brands.