CSSQuake • Hacker News Board

Re: CSSQuake

#101

Post by culi » Sun, Jun 21, 2026, 12:36 AM UTC

libria wrote: post #82

culi wrote: post #66

Earlier quoted context omitted.

Decades of optimizing a toaster to make better toast will not make the toaster any better at making meatloaf

Is this the right analogy? The product is the same, the appliance is different. 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.

I stand by my analogy.

Both a toaster and an oven might benefit from improved electronics but in the end—whether its a toaster from the 60s or a toaster from 3008—you are still using a toaster to make a meatloaf.

CSS is not remotely comparable to a game engine. It's not even a programming language.

Re: CSSQuake

#102

Post by bitwize » Sun, Jun 21, 2026, 12:48 AM UTC

DanielHB wrote: post #58

jedberg wrote: post #42

This 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.

I ran it on a Pentium 60. If you stuck to 320x200 it ran fine.

Re: CSSQuake

#103

Post by amatecha » Sun, Jun 21, 2026, 12:57 AM UTC

jedberg wrote: post #42

This 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...

Err, strange, what browser? I'm using Firefox on a ThinkPad from 2018 running Linux, and cssquake was running at a smooth 60fps just now (and at 1080p resolution vs the 320x240 or 320x200 someone would likely be running on a P133)

Re: CSSQuake

#104

Post by amatecha » Sun, Jun 21, 2026, 1:00 AM UTC

sgt wrote: post #22

Very cool. I wonder what the limitations are? I see the dog I shot is floating in the air. Is that maybe a CSS thing or is it fixable?

Damn, always gotta deal with these accursed z-index issues with CSS ;)

Re: CSSQuake

#105

Post by amatecha » Sun, Jun 21, 2026, 1:02 AM UTC

boredemployee wrote: post #54

I still play quake (world) to this day. I just can't quit it.

Hell yeah, I still see it as the optimal arena FPS. The sequels add too much IMO. Quake 1 (QuakeWorld) was such a raw competitive arena shooter that is just pure action, no weird extra mechanics. Pick up items, get some health, shoot people. Q2/Q3 are totally fine too, but I feel like QW really just nailed everything.

Re: CSSQuake

#106

Post by billfor » Sun, Jun 21, 2026, 1:37 AM UTC

culi wrote: post #66

jedberg wrote: post #61

Earlier 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

We haven't had a toaster that makes better toast since 1997 (Sunbeam radiant control).

Re: CSSQuake

#107

Post by qmr » Sun, Jun 21, 2026, 1:37 AM UTC

culi wrote: post #66

jedberg wrote: post #61

Earlier 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