Would that be better or worse for webdev? I don't know. But I like to ponder.
CSS is DOOMed
71–80 of 120 posts
Re: CSS is DOOMed
#72[flagged]
We detached this comment from https://news.ycombinator.com/item?id= and marked it off topic.
Re: CSS is DOOMed
#73Its incredible how far concepts like CSS can be pushed. But sometimes I wonder what if CSS would be just JavaScript i.e both concept are merged. Would that be better or worse for webdev? I don't know. But I like to ponder.
Re: CSS is DOOMed
#74So impressive! Bonus, you can wall hack by just deleting a div ahah
Even better, since everything is well organized, you can add `opacity: 0.7` to `.wall` specifically, and get something that looks almost exactly like how old school wallhacks looked like.
Re: CSS is DOOMed
#75Re: CSS is DOOMed
#76Earlier quoted context omitted.
Even better, since everything is well organized, you can add `opacity: 0.7` to `.wall` specifically, and get something that looks almost exactly like how old school wallhacks looked like.
Is that a Doom reference? What’s a wall hack? How did it look?
Re: CSS is DOOMed
#77> "I used Claude to create an approximate version of the game loop in JavaScript based on the original DOOM source" This is the real horror here, Uncanny-Valley gameplay Doom. It's like those Doom maps where people tried to recreate the game levels from memory, but still made a few mistakes and got some details wrong. This is like that, but for the gameplay rather than the level layouts. It's different enough to be w…
Re: CSS is DOOMed
#78In recent years CSS has become closer to a full programming language through experimental features, for example in 2025 they added if statements and some math functions like modulo https://www.simplethread.com/new-and-upcoming-css-features-i...
The only thing missing is the ergonomics of a real programming language.
And this project kinda show how far you can go, still, if you really want it :D
Re: CSS is DOOMed
#79Re: CSS is DOOMed
#80Its incredible how far concepts like CSS can be pushed. But sometimes I wonder what if CSS would be just JavaScript i.e both concept are merged. Would that be better or worse for webdev? I don't know. But I like to ponder.
I think it would be too easy to create an uncontrollable cascade of function calls, causing terrible performance. IMO, it's best to keep concerns separated. Perhaps the current JS/DOM interface is a bit cumbersome, but it gets a lot done. What is your reason for merging?
Good question, I personally think that seperating by concerns is good. But when problems arise like boundaries that get crossed or compilers implementing language features into css like Sass, maybe it proves that those things are actually not two concerns but one.
Lately I am using Catch2 (a c++ testing framework) and wanted to benchmark some code. My first instinct was looking for a benchmark framework. But to my surprise Catch2 does also have a benchmarking framework included!.
Most people would argue that a testing framework should not include a benchmarking framework. But using it myself it showed me that both concerns of benchmarking for performance regressions and testing are similar.
Similar enough that I would prefer both of them together.
Most people, me included, are asking: "Should this be split into more?" But seldom, we ask: "Should this be merge into one?"