Hacker News Reader

Comment by winter_blue | Hacker News Reader

It's so slow.. According to hackermom the 14Mhz Amiga could do this at 25 fps, any idea why this is so slow on modern computers?

View on HN

Because it's running in canvas? In other words, it's running within abstraction layer upon abstraction layer, with various other abstraction layers involved to help make sense of the fact that there are too many abstraction layers.

The amiga code was probably pretty close to talking to the graphics driver directly. Canvas is cool, but in terms of performance it's never really going to compete with native code, or even with flash for that matter since flash can remove some complexity by only building for a single, predictable, optimized environment.

"Graphics driver" still sounds too complex. The code was probably poking bytes to the memory segment mapped directly to the display - just like in DOS days, where each byte of the 0xA000 segment represented a pixel when using a VGA 320x200 resolution, 256 colors palette.

> it's running within abstraction layer upon abstraction layer, with various other abstraction layers involved to help make sense of the fact that there are too many abstraction layers.

"Every problem can be solved by adding another layer of abstraction--Except for the problem of having too many layers of abstraction"--Alan Perlis

That's why everyone is embracing GPU powered graphics.

Not in Chrome it isn't!

It's not slow on modern computers. It's slow on these environments that weren't made to execute code quickly, much less do any pixel manipulation. How many orders of magnitude more instructions is it to set a pixel on an Amiga, versus setting it via JavaScript?

It's just as fast in Opera!

Reply on news.ycombinator.com