4 ms·
I've heard this a lot in the games industry -- "For each version, the programming was done from zero. We can’t stress this enough." That seems so wasteful and
by ChuckMcM 12y ago
I've heard this a lot in the games industry -- "For each version, the programming was done from zero. We can’t stress this enough."
That seems so wasteful and challenging, anyone from the industry care to comment on how a studio would get itself into a situation of effectively zero reuse of their code?
- sehugg 12y agoLet's say it's 2011 and you want to port your Flash game to iPhone. You can try packaging your Flash game using Adobe's tools, but it'll probably be very slow, and Apple might change their mind again about allowing Flash apps on the platform. There aren't very many well-supported C/C++ frameworks for iPhone yet -- you search the forums for each and only find unanswered questions. You're worried about it working well on the new iPad. So you do the safe thing everyone else is doing, Cocos2D and Objective C. You'll worry about porting later, if the game does well. Maybe you'll just pay someone else to do it.
- NickPollard 12y agoThe main issue is a lack of money/long-term survivability for most studios, which leads them to cut many corners in order to release the game before running out of cash. This means that code is written to ship the game out of the door, rather than for the future, so there often isn't time for proper engineering. Then if that game does OK they get to work on the next one, throw away all the hacks they did last time, and start again... It also doesn't help that due to the structure of the industry (e.g. work hours, low pay etc.) they have trouble retaining developers and instead replace them with fresh grads. A huge percentage of people I know left the industry before they hit 30 (myself included). This leads to a lack of experienced engineers.
- eropple 12y agoI'm going to preface this post with a note that, yes, there are surely good developers in game development, this is not a universal thing, etcetera etcetera. Ass properly covered, I'll be real: I'm never surprised to see this because "code reuse" is generally the sign of reasonably advanced developers and I don't know a single person in game development I would hire for a role outside of it. It's not just NIH--that's a problem but one slowly going away. It's more just a fundamental lack of understanding of software engineering and building Good Code. As time goes on I've seen gamedev acquaintances poorly reinvent most of the wheels that the rest of the world takes for granted--even something as simple as serialization for save data and network transport (but no schematic validation, because "schemas suck") was trumpeted to me as this Big Crazy Great Thing. Which contextually it may be, but I kind of feel like the state of the art for stuff not involving pointer munging is about a decade behind everybody else. So, code reuse? Gotta make good code first.
- alexnking 12y agoWell there's a difference between code reuse, and cross-platform code reuse. If you're porting a Laravel project to Rails or vice versa, you should be reusing logic, not code.
- pmelendez 12y agoI worked in the gaming industry for a couple of years and after I worked in the RTB industry and lately in the forex industry. I am not alone, and I have a lot of friends coming out of gaming that work very well in other industries. The problem is not whether or not game developers know how to reuse code but whether or not it makes sense or are allowed to reuse it. One big challenge when you are going to reuse code is not having a stable set of requirements (which in gaming is almost non existing even in the late stage of a project) and when you take that and join it with tight and unreasonable schedules you would have a huge mess as result. The state of the industry is very unhealthy in my opinion and I wouldn't be surprise if there is another dark age for videogames coming up.
- SimpleMinds 12y agoI agree with what you said with my limited experience. I hope it's anecdotal nature is good enough. I worked in a company that went from doing software gigs in general to be full mobile gaming company. Before it was quite standard Agile style company: Scrum, code reviews, TDD, cross-functional teams (front end devs knew how servers works in general), focus on quality over quantity (one dev, rotated weekly or biweekly, focusing on fixing bugs), separate concerns. After going full game-oriented, company hired couple of people from gaming industry into higher positions - tech leads, project managers etc. Over couple of months, people with many years of experience in those big companies dismantled what was standard for me, using combination of two arguments: - big names don't do it, so it must be wrong - it's a waste of time Before I quit, there were no longer code reviews (waste of time), all testing was to be handled by QA team (waste of valuable dev time), ship with issues (waste of time to fix minor bugs when can add features), single system responsibility (one dev to write code for client server protocols, one dev for UI, one dev for assets etc, that's gow big names do it). At one of the last talks with "industry veteran", when I mentioned those things - and how negative, in my opinion, those changes are, his response was "so you are saying that whole gaming industry dev practice is wrong". At that point I thought he's right and I sound full of crap, now I believe that yes, AAA companies are simply bad development practises shops. My guess as to why is because AAA is very strongly driven by deadlines and marketing, where you cannot simply delay release (Christmas shopping spree is coming). This idea I saw articulated on HN first and I agree with it.
- highCs 12y agoAlmost all the graphics, audio, net, event, ui, system calls and data structures are generally tied to the low level frameworks without any level of virtualization. Add to that that each framework has its own standard and way of doing games (event-base, component-base, etc.). The worse part I think is the game logic is generally enclosed in framework-specific objects like events in as3, components in unity, etc. Virtualizing that would be expensive, tricky and costy in terms of performance.
- jfoutz 12y agoI am genuinely surprised that a flash game is so tightly coupled to the underlying hardware. That's amazing.
- wtracy 12y agoThe problem is not that the Flash game is so tightly coupled to the hardware, it's that it is tightly coupled to the Flash runtime. (Mainly because Flash forces a certain structure on your code, but also because Flash's idiosyncracies are so bad that you have to bend over backwards to get good performance from it.)
- ChuckMcM 12y agoIn the way back times, when the Amiga was a hot machine, I hung out with folks who were games people and they were always trying get one more erg of power out of the machine because, as they put it, "Every cpu cycle spent on the game makes it that much better." Which was clearly true in the Amiga, and the PC/AT and Macintosh II, but for a modern machine with 4 cores and 8GB of memory and a GPU that fills a 1080p screen with triangles almost without thinking about it. It seems like 'bare metal' is suddenly a hindrance and 'moving to multiple platforms with minimal rewrite' would be the thing evolution would push into game studios. Where did that message get lost?
- sharpneli 12y agoThe message gets lost in performance. The difference between engine optimized for certain platform is simply massive. We're talking at in the worst case 10x the performance difference. Why is this? Let's take modern console game for PS4. It uses mantle like API where you can simply spam drawcalls like no tomorrow. Port that to DX11/OpenGL and you'll choke. Or move a simple OpenGL game from PC to mobile, it does nothing fancy and uses ES2.0 subset of OpenGL so it should work nicely? Not quite. All your scenes are built using effects that cause massive performance penalty in tile based renderers. Sure it works fine on Tegra K1 but everywhere else it's horrible. On the other hand there is a way of doing multiplatform development. It means using Unity (or other multiplatform engine), limiting yourself to a common subset and leaving the optimization part to be the headache of the engine developers. However even if you use Unity you have to manually consider the effects you are using on per platform basis.
- NDizzle 12y agoI'm going to paraphrase a friend of mine who is a great mobile developer. They could have used AIR on mobile to re-use the AS3 codebase. Alternately, they could have done c++ on cocos2d-x instead of objective c, so that would have been pc portable. They would just have to write it twice, in that case. However, if you are a group of AS3 devs jumping to mobile, they probably picked the best sounding thing at the time - which was cocos2d. Keep in mind android wasn't really a game platform in 2011, so choosing cocos2d in obj-c over c++ wasn't really a bad call.
- pjmlp 12y agoThe game industry grew up in the 80's where the only suitable language to write games on was Assembly and everything computer was completely different, even between revisions. Basic, C and Pascal were the Python and Ruby back then. So porting studios appeared, specializing in porting the games to specific platforms. The porting industry came to life. Fast forward 30 years, you still need to write quite hardware specific code if you wish to squeeze out every possible ms out of the machine, which opens the door for all kinds of shortcuts. This of course only matters when doing AAA games.