5 ms·
Coming from a gamedev perspective, I've personally decided to draw the line at the following for my projects: * Using your platform's graphics/sound/input/etc.
by bitwize 7y ago
Coming from a gamedev perspective, I've personally decided to draw the line at the following for my projects:
* Using your platform's graphics/sound/input/etc. APIs, or wrappers like SDL, is not cheating
* Using a third-party engine is cheating
Other programmers may draw the line elsewhere and that's fine. I think for me it's a question of, using a library to achieve <hard task> is fine, but using a framework puts on me the burden of understanding and then extending someone else's half-completed program. And when that someone else made a decision that I wouldn't have made that fucks with my workflow, it also puts on me the burden of, is it okay to go in and change it or implement a low-level hackaround? Or is that cheating, and should I do everything in the framework's own terms?
- tybit 7y agoAt first I thought the “libraries, not frameworks” mantra* was silly for drawing an arbitrary line in the sand. Over time it’s lined up well with my experiences though. * e.g http://tomasp.net/blog/2015/library-frameworks/ http://tomasp.net/blog/2015/library-frameworks/
- stjohnswarts 7y agoThis is my experience with web stack work.
- nrb 7y agoI don’t think players care about the architectural purity of your product. Some baseline of performance is sufficient as long as you can deliver the proper experience, which is really the only thing they’re seeking in your game. If that same experience can be delivered MUCH more quickly and easier why would someone deny themselves and their users those benefits? I understand there is nuance in this decision but it feels dangerous as a hard and fast rule. I think especially so when team size > 1-2 and common understanding becomes important.
- CapsAdmin 7y agoThis is very true if you want to make a game, but that's not always what a "gamedev" wants. I used to think I wanted to make games, but I really just enjoy making game systems and game engine related things.
- clarry 7y ago> I don’t think players care about the architectural purity of your product. But we can kinda see how the "quick and easy" approach with modern engines is leading to lots and lots of sloppy games with leaky seams. I always appreciate it when a gamedev writes their own engine, and IME these tend to come out as the more polished games. Doing your own engine would also enable open sourcing it, which is something gamers can be quite grateful for 10-20 years down the road.
- reificator 7y ago> I always appreciate it when a gamedev writes their own engine, and IME these tend to come out as the more polished games. Of the ones that finish perhaps.
- swalls 7y agoWell, they kinda do, sometimes at least. This is a slightly weird case, but Unity has gotten a bad rap recently for being host to a million shovelware and asset flip games due to its low barrier to entry, so much so that some people avoid things made in Unity entirely.
- meheleventyone 7y agoHow many people though? If you're going to let this sort of rumor inform technical decisions then you need to quantify it. There are after all quite a lot of other odd but unpopular reasons people won't buy a game.
- bitwize 7y ago> I don’t think players care about the architectural purity of your product. I care. Plus, I open-source my games, so I expect players to appreciate them at one level and other coders to appreciate them at another.
- Can_Not 7y ago> Using a third-party engine is cheating No, using an already existing engine is called delivering a product in a predictable timeframe. Valid reasons to not use a specific engine for a specific project are plentiful, even if all engines get ruled out, but "cheating" is nonsense.