3 ms·
Nice, but "Fast" - compared to what?
by zerr 13y ago
Nice, but "Fast" - compared to what?
- shakiba 13y agoThanks! Fast enough for game development >= 60fps Check out http://piqnt.com/o/ http://piqnt.com/o/
- camus2 13y agoso you claim your engine maintains 60fps whatever the code is thrown at it right?
- shakiba 13y agoNot whatever, but it makes game dev as easy as web dev while still almost as fast as native development. See your CPU usage while playing.
- camus2 13y agoso you mean fast like RAD , not fast like SPEED,right ? because >=60fps highly depends on the machine one is running , and the browser one is using. Saying something is fast without benchmarks is stupid. speed is something relative. Nothing is fast or slow, but faster or slower than something else. So what is your framework faster than?
- seszett 13y agoFaster than SVG or DOM under certain conditions, obviously. Nobody is claiming that CutJS is "fast" in a somehow absolute way, I think most HN visitors are intelligent enough to understand that performance depends on the machine running the application and also on the complexity of the tasks that are running. Speed aside, CutJS seems like a nice canvas manipulation library, I'll have to give it a try.
- shakiba 13y agoNo, I didn't mean RAD by fast, I meant it makes development easier (than not using it) while it is still almost as "fast" as directly using Canvas and "fast" enough for game dev.
- deleted 13y ago[deleted]
- deleted 13y ago[deleted]
- IanCal 13y agoThat game judders and skips at times, I'm concerned if current "fast" HTML5 games are simple 2d games that perform badly. Even the asteroids game has perceptible little jumps. It's asteroids! It's one of the simplest to render games there is.