CSS is DOOMed
51–60 of 120 posts
Re: CSS is DOOMed
#52Re: CSS is DOOMed
#53CSS started as purely declarative styling, but between things like conditionals, math functions, and now these rendering tricks, it’s slowly creeping into “programmable system” territory. Not because it’s the right tool for it, but because browsers are becoming the real runtime. The interesting question isn’t “can Doom run in CSS”, it’s how much logic we’ll keep pushing into layers that were never meant to handle it.
Re: CSS is DOOMed
#54Re: CSS is DOOMed
#55Re: CSS is DOOMed
#56Re: CSS is DOOMed
#57But where can I try it out in my browser? EDIT: https://cssdoom.wtf/
Re: CSS is DOOMed
#58But where can I try it out in my browser? EDIT: https://cssdoom.wtf/
Works smoothly in Firefox. But the default key mapping is busted: fire at Alt means that it opens and closes the menu in Firefox with each press. Also, Alt + left arrow ends the game and goes back in history. Interestingly, it was more choppy in Chromium. I could not find a key for moving sideways ("strafing"). All in all, quite mind-boggling.
Re: CSS is DOOMed
#59Creating 3D scenes with CSS has always been possible[0], but like this project, it's required JavaScript for interactivity. But there's a lot more CSS features now. While in the past, Turing completeness in CSS required humans to click on checkboxes, now CSS can emulate an entire CPU without JavaScript or requiring user interaction.[1] So I wonder if DOOM could be purely CSS too, in real time. [0]: https://keithclark…
Re: CSS is DOOMed
#60In 2006, Ars Technica published an April Fool's article[0] declaring that the perennially-forthcoming Duke Nukem Forever would finally see the light of day... as... a browser game ! Ho ho, how droll. Crazy to see how far we've come. [0]: https://arstechnica.com/gaming/2006/04/forever/
Quake Live did come out as a browser NaCl game a year or so later.