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.
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.
CSS is a general rendering solution, not something built for rendering 3D games.
And no one has spent any time optimizing 3D transforms to make a game workable because no one would be able to justify the use of their time like that. It wouldn’t even give you brownie points ‘cause most people would just ask “why?”
Comments
This engine is not optimised for performance. It's using CSS, after all.
Yeah this is a case of “not the right tool for the job”.
It is awesome though.
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).
Is this you? https://www.timstoasters.com/
Toaster you say?
https://philip.greenspun.com/humor/eecs-difference-explained
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.
It'd be like if the IOT AI Smart Air Fryer had a constraint of only being allowed to use friction to create heat.
CSSQuake uses an intentionally-absurd rendering pipeline. It's not surprising that the result is sub-optimal.
(Though I agree that the meatloaf analogy is not very good.)
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.
I am on the ground. This is great.
Still, why css is as slow as it is given what tech like imgui can do is a little wild.
CSS is a general rendering solution, not something built for rendering 3D games.
And no one has spent any time optimizing 3D transforms to make a game workable because no one would be able to justify the use of their time like that. It wouldn’t even give you brownie points ‘cause most people would just ask “why?”
Id assume "a fun challenge" could be enough of a reason