And maybe a skill issue but I was unable to jump out of the slime...
CSSQuake
81–90 of 125 posts
Re: CSSQuake
#82Earlier quoted context omitted.
Of course, but you'd think after 30 years the compute power should be enough to overcome any lack of optimization. It's a testament to the engineering that went into the original Quake engine.
Decades of optimizing a toaster to make better toast will not make the toaster any better at making meatloaf
It should be "Decades of inventions from toasters to IOT AI Smart Air Fryers will not make better toast than the original"
But I'd argue the IOT AI Smart Air Fryer should make really good toast. Which is what GP is saying.
Re: CSSQuake
#83Re: CSSQuake
#84Though this is impressive, I think this is something that should not be possible with a declarative styling language
Re: CSSQuake
#85Impressive. I guess this isn't only the renderer made to use CSS but also a full recreation of the engine and logic right? My guess is because a bunch of things do not behave like the original game, e.g. some buttons need to be shot instead of touched to activate, some secret doors open by touching them instead of being shot, etc.
Re: CSSQuake
#86This is an awesome achievement, but I can't help but notice that Quake ran smoother on my Pentium-133 PC in the 90s than it runs on my Mac M1 Pro...
Wait, did Quack run on Pentium-133? I had a Pentium MMX 233mhz and I always assumed it didn't ran well so I never bother to get it.
Re: CSSQuake
#87It seems like this CSS Quake needs JS to run…
Re: CSSQuake
#88Re: CSSQuake
#89This is an awesome achievement, but I can't help but notice that Quake ran smoother on my Pentium-133 PC in the 90s than it runs on my Mac M1 Pro...
Re: CSSQuake
#90This is an awesome achievement, but I can't help but notice that Quake ran smoother on my Pentium-133 PC in the 90s than it runs on my Mac M1 Pro...
Zero issues on Firefox + Linux. Gnome Web is stuttery and weird, though. Must be a WebKit/Safari thing.