11–20 of 54 posts
Earlier quoted context omitted.
Thanks! Fast enough for game development >= 60fps Check out http://piqnt.com/o/
so you claim your engine maintains 60fps whatever the code is thrown at it right?
Earlier quoted context omitted.
so you claim your engine maintains 60fps whatever the code is thrown at it right?
Not 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.
Earlier quoted context omitted.
Not 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.
so 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?
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.
Earlier quoted context omitted.
Not 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.
so 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?
Earlier quoted context omitted.
so 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?
Faster 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.
>new concept called pinning introduced instead of styling It's just a scene graph.
Pinning is about positioning variables, not graph structure.
Also, it looks like the pinwheel demo has an error. I suggest you add one of the more advanced demos along with source code on the intro page. Just looking at the first few demos I felt it reimplemented stuff that's already possible with CSS, but it looks like it's capable of much more (the last few demos)
Why not WebGL-based?
Why not WebGL-based?