3 ms·

>And what about those people that use the beta (e.g., me) and see the bugs and glitches as a result of your incompetence? This line discredited the whole artic

>And what about those people that use the beta (e.g., me) and see the bugs and glitches as a result of your incompetence? This line discredited the whole article for me. Firstly, you're writing a video game inside a browser. This is like making a space ship that does surgery. You've got two complex systems working together of course there will be bugs. Also why on earth would you expect the browser to play the game exactly the same over the course of time. Every update to iOS or android introduces new bugs into the system. I don't understand where you come of saying that an update should never break anything ever. Canvas is massively different across browsers. Its your job to figure out the difference and account for it. The spec isn't even finalized yet. I honestly expected the author to touch on some important issues like the fact that your game is naturally open source. But this seems more like a frustrated developer expecting too much from a platform.

fiblye 15y ago
Honestly, people "stealing" my source code isn't that much of a worry for me. People already have ten million dollar games cracked and distributed before they're released, and honestly, I don't think somebody taking my code would change much. If they try redistributing it, I still have legal rights to it whether or not they got uncompiled code. My biggest problem is that you can have a completely working project that's literally broken overnight with a silent update. Operating system updates generally require the user to knowingly upgrade and there's always the implied risk of something strange happening. Developers can easily publicly announce incompatibilities with certain OS updates on their download page to warn new users, while an HTML5 game requires you to test every single release of every browser ever, and since everybody uses a slightly different version of a slightly different browser, it only takes one glitch for one person for your entire market to be scared off. I never said I didn't anticipate things going wrong, but that when things do go wrong, it can completely out of control in the browser world. My development of games in HTML5/Javascript has been 98% pure bliss, but the thought of a single dangerous bug making it past the testing phase gives me nightmares. I knew what I was getting into and it was primarily a test of "can I do it?", but it doesn't mean I can't complain. ;)
azakai 15y ago
> I honestly expected the author to touch on some important issues like the fact that your game is naturally open source. Small correction, your source is readable, but it isn't "open source" - "open source" means available under and open source license (which your code is not, unless you actually do that). Your source also doesn't need to be readable - you can obfuscate it, to the point where it is as readable as native binaries - disassembleable in theory, but only by experts.

fiblye 15y ago

Honestly, people "stealing" my source code isn't that much of a worry for me. People already have ten million dollar games cracked and distributed before they're released, and honestly, I don't think somebody taking my code would change much. If they try redistributing it, I still have legal rights to it whether or not they got uncompiled code. My biggest problem is that you can have a completely working project that's literally broken overnight with a silent update. Operating system updates generally require the user to knowingly upgrade and there's always the implied risk of something strange happening. Developers can easily publicly announce incompatibilities with certain OS updates on their download page to warn new users, while an HTML5 game requires you to test every single release of every browser ever, and since everybody uses a slightly different version of a slightly different browser, it only takes one glitch for one person for your entire market to be scared off. I never said I didn't anticipate things going wrong, but that when things do go wrong, it can completely out of control in the browser world. My development of games in HTML5/Javascript has been 98% pure bliss, but the thought of a single dangerous bug making it past the testing phase gives me nightmares. I knew what I was getting into and it was primarily a test of "can I do it?", but it doesn't mean I can't complain. ;)

azakai 15y ago

> I honestly expected the author to touch on some important issues like the fact that your game is naturally open source. Small correction, your source is readable, but it isn't "open source" - "open source" means available under and open source license (which your code is not, unless you actually do that). Your source also doesn't need to be readable - you can obfuscate it, to the point where it is as readable as native binaries - disassembleable in theory, but only by experts.