Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> for good performance, Firefox should be avoided

Oh well.

Then again, the demo is only usable for those with existing assets.



> for good performance, Firefox should be avoided

Can't, for privacy reasons.


Can, use Waterfox instead.


He was referring to chrome


It's a joke


FWIW, I just tried it on Firefox and it seems work just fine.


I wonder what’s wrong with Firefox? What is the bottleneck? The JavaScript engine? I’m guessing the thing is compiled to wasm anyway.


The bottleneck is webgl. I'm not sure why exactly but firefox is pretty well known to have significantly worse webgl performance than can be achieved with chrome.


"I'm not sure why exactly"

I would guess because the GPU world is messy and full of broken drivers full of hacks and workarounds, so it is rather a miracle that FF works so good, with the few engineers they have left.

(If you are on a chrome based browser, open chrome://gpu to get a glimpse into the work they have been doing just for your GPU and plattform)


Which is why sadly Web 3D never took off beyond ecommerce and visualisation tooling, with game studios rather focusing on streaming.

While on native games the engine can workaround the driver issues, Web 3D APIs are at the mercy of the browser sandbox, where studios don't have access to possible workarounds due to lack of feedback on API performance.


It’s RA2. If we could run it on a P2, then surely we can run it in a modern browser even on pure CPU?


Exactly what I was thinking.

Minimum specs: Memory: 4GB (8GB recommended)

The original ran on 128 MB or even less.


32MB under Win95


Probably even with pure software rendering in WebAssembly, most likely.




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

Search: