Sonic and Sega Retro Message Board: Rolken - Viewing Profile - Sonic and Sega Retro Message Board

Sofox, the solution to broken commits is to not use a single branch on which everyone has commit access. Get the team (if it exists) on git[hub] and use pull requests. You can't expect a bunch of mostly new programmers to produce top notch code. (Where is the code going anyway? I don't see a working repo link anywhere.)

If anyone involved lives in/near San Francisco, I can direct you to lots and lots of local resources for getting up to speed with basic stuff like editors and git.

But really, how are you going to make this a successful project if even the project leader won't/can't devote time to it? Life is busy, everyone has busy lives, that's life.

edit: Also, here's a talk on building communities around open source game dev that was pretty great and seems relevant.

This particular rocket fell over on the launch pad when a soft breeze rolled by.

But if you're interested in game tech, Fabien Sanglard regularly posts great game engine analyses and discourses, which could be an interesting place to start learning about it.

With the given information, the answer is "it depends." Implementation matters a lot; "keep a sql connection open across local ethernet and check whether the notification table is empty every 5 seconds" may have invisible resource impact, while "re-run a script every 5 seconds that opens a new sql connection across the Internet and checks all of the users to see if their information has changed" could bring your server to its knees and blow your attack surface wide open. You also have to be careful about race conditions.

Hey, whatever. I'm not here to "peer pressure" anyone into using particular technologies; I don't give a shit what you use. I was simply offering advice and context, as was requested. (And I guess nobody noticed that I pointed out the mass assignment issue on the first page.)

PHP is simply not the language actual experts and professionals choose for new projects in 2012. If that doesn't bother you, great. PHP might not flex your expertise but it won't kill you. Knock yourself out, have fun. If it does bother you, maybe you should ask yourself why it bothers you and figure out what you want out of programming. I personally love exploring new technologies built on fresh ideas, and getting paid handsomely for it is the icing on the cake.

Either way, arguing about it is pretty goofy.

There's no purpose other than the overt one: to offer tone and guidelines on what leads to a successful project, as someone who has run and participated in successful projects, including specifically running a successful Sonic fan community. I'm an outsider here, so I have no idea what's going on with S2HD internally.