5 ms·

This is how we get there. HTML5 is pretty fresh and it's games like this that let us understand it's capabilities and to improve upon them. I mean, this is a mi

by kerno 14y ago

This is how we get there. HTML5 is pretty fresh and it's games like this that let us understand it's capabilities and to improve upon them. I mean, this is a mini MMO implemented in HTML5. That's a pretty big step forward from Pacman in HTML5 already.

jader201 14y ago
Yeah, I definitely agree that this is a big step from anything I've seen thus far. This was more to kick off a discussion about "are we there yet?", and if not, what is still missing? I mean, I know what I think is missing, but I've not tried building HTML5 games to understand if HTML5 is the bottleneck, or if other dependencies are the bottleneck.
- MrScruff 14y ago
  Perhaps what's missing is a good reason for choosing HTML5 over traditional technologies when you're investing in a new project. Pros: Runtime is very widely available Cons: Relatively poor performance Monetization strategy is not clear Browser differences increase cost of development
  - jiggy2011 14y ago
    You also have to mess with Javascript on some level, even if you are compiling down from something else. People who are professional game developers have invested a lot in C++ , have a lot of experience in that area and tend to see Javascript as something for developing websites with. So on top of the other problems you have persuade them that it's something worth spending the time to get proficient in.
    - pifflesnort 14y ago
      If you're coming from a deep machine and C++ understanding, it's not that JavaScript is tough to become proficient in, but rather, that you of all people have every reason to fully comprehend why it's such an awful implementation choice for this proposed purpose. It's not as if the PC or mobile game market is suffering for lack of cross-platform browser-based compatibility, so why switch to a suboptimal tool?
    - sixothree 14y ago
      Do you still have to deal with all of the DOM stuff in html5/javascript?
      - jiggy2011 14y ago
        Yes and no. It's all still there of course. I imagine though if you want to build a game you don't use DOM elements for sprites etc. You just create a giant <canvas> element that you draw to as you would draw to a frame buffer in DirectX etc. You could use DOM elements for the UI though I guess.
        joshuacc 14y ago
        Yep. If you examine the source of this game that's exactly how they handle the game itself.
undershirt 14y ago
Here is a link to html5 pacman if you're interested. It was DMCA'd on github, but it's here now: http://pacman.shaunew.com/ http://pacman.shaunew.com/ It's broken on chrome now for some reason, but works in IE9, Firefox, Safari and Wii-U.

by kerno 14y ago

jader201 14y ago

Yeah, I definitely agree that this is a big step from anything I've seen thus far. This was more to kick off a discussion about "are we there yet?", and if not, what is still missing? I mean, I know what I think is missing, but I've not tried building HTML5 games to understand if HTML5 is the bottleneck, or if other dependencies are the bottleneck.

MrScruff 14y ago
Perhaps what's missing is a good reason for choosing HTML5 over traditional technologies when you're investing in a new project. Pros: Runtime is very widely available Cons: Relatively poor performance Monetization strategy is not clear Browser differences increase cost of development
- jiggy2011 14y ago
  You also have to mess with Javascript on some level, even if you are compiling down from something else. People who are professional game developers have invested a lot in C++ , have a lot of experience in that area and tend to see Javascript as something for developing websites with. So on top of the other problems you have persuade them that it's something worth spending the time to get proficient in.
  - pifflesnort 14y ago
    If you're coming from a deep machine and C++ understanding, it's not that JavaScript is tough to become proficient in, but rather, that you of all people have every reason to fully comprehend why it's such an awful implementation choice for this proposed purpose. It's not as if the PC or mobile game market is suffering for lack of cross-platform browser-based compatibility, so why switch to a suboptimal tool?
  - sixothree 14y ago
    Do you still have to deal with all of the DOM stuff in html5/javascript?
    - jiggy2011 14y ago
      Yes and no. It's all still there of course. I imagine though if you want to build a game you don't use DOM elements for sprites etc. You just create a giant <canvas> element that you draw to as you would draw to a frame buffer in DirectX etc. You could use DOM elements for the UI though I guess.
      - joshuacc 14y ago
        Yep. If you examine the source of this game that's exactly how they handle the game itself.

undershirt 14y ago

Here is a link to html5 pacman if you're interested. It was DMCA'd on github, but it's here now: http://pacman.shaunew.com/ http://pacman.shaunew.com/ It's broken on chrome now for some reason, but works in IE9, Firefox, Safari and Wii-U.