Hacker News new | past | comments | ask | show | jobs | submit login

It's mainly the lack of a javascript JIT.

You can get a JIT for 32-bit x86 and ARM. You can get a JIT for 64-bit x86, ARM, and PowerPC.

In the modern world, no JIT means no web.

Right after that problem, those old PowerPC machines face a lack of RAM and a lack of well-accelerated 3D. It was typical to have 64 to 256 megabytes of RAM, with an upper limit of 1.5 gigabytes. There might have been a 3D accelerator, but it couldn't work in full resolution/color fast enough to keep up with modern compositing needs.

For us older people, these are all silly big numbers for reading web pages. Wasteful frameworks and advertising have bloated up the web, requiring us to follow the crowd in buying faster hardware just to get the performance we had two decades ago.




Not just the web, year or so ago tried importing a dxf file (old autodesk export/import format) on a newer CAD program. Used up 2gb of ram and then died. Opened it in an old moldy gerber viewer, displayed instantly. Turned out it had about 10000 elements. If I deleted half then the CAD program would display it after a while. Far as I could tell each element in the dxf was consuming about 300-500k of RAM.

Reminds me of the Tom Waits song: What's he building in there.


Also, modern JavaScript is little-endian and PowerPC is big-endian.




Consider applying for YC's Spring batch! Applications are open till Feb 11.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: