111–120 of 120 posts
Earlier quoted context omitted.
The only thing missing is the ergonomics of a real programming language.
I like the declarative nature of it. It makes it so easy to debug anything, with "simple" introspection tools. I feel that many horrors will be created when we introduce control flow to CSS. And this project kinda show how far you can go, still, if you really want it :D
This feels like one of those “because we can” projects that accidentally reveals where the platform is going. CSS 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…
at what point is CSS powerful enough to become a malware vector.
Is CSS that awesome? It's still a language designed for styling webpages with 30 year of added features. I'd argue something purpose built would be a much better tool for the potential usecases people try to use CSS for now. I guess I am asking, if modern CSS is so awesome, it's awesome compared to what exactly?
I'm asking the same question! No doubt the very loudly opinionated not-web-dev community, who have So Much To Say about web devs and web tech, have produced an uncontroversial, perfect layout system, styling system, and language to produce the replacement for this awful web tech. Where is it? What is it? Please provide (the better version of) a hyperlink to the docs.
So yes I will argue that Qt6 and GTK are better than flexboxes.
Because you asked for it, here's some documentation to a UI framework which I believe to work better than the web stack: https://doc.qt.io/qtforpython-6/PySide6/QtWidgets/index.html
CSS is /the/ spec to look at to understand how awful something designed by committee gets. In web specs closely rivaled by SVG. You can pick which one is uglier and you'll be right.
The fact that Claude is killing CSS officially means we need to switch back to IRC or something. AI is a parasite we cannot integrate but only avoid. (P.s. if you work in AI, stop, you are literally destructive to humanity.)
This feels like one of those “because we can” projects that accidentally reveals where the platform is going. CSS 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…
Creating 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…
The author links to th CSS x86 project: > Yes, Lyra Rebane build a x86 CPU completely in CSS, but that technique is simply not fast enough for handing the game loop. So the result is something that uses a lot of JavaScript.
not only do i think doom in css is possible, but both me and another css person were also planning on actually making it into reality
but it sort of feels demotivating to see js-powered css projects like this hit the frontpage, because if we do eventually make a css-only doom people will think its a repost or nothing special
edit: and to be clear, that demotivation is more of a problem of how the internet, virality, and news cycles work. the actual project here is still pretty cool!
While standalone CSS is not yet Turing complete, I worry about the new attack vector categories opened up by moving it towards that state. Already I believe attackers have a choice to spread the attack payload between CSS, HTML and JavaScript to evade current detectors and analysis at the network borders, and evade CSP's since we're well into undecidability territory, like using CSS attribute selectors if the CSP all…
> While standalone CSS is not yet Turing complete Looks like it is, though? https://news.ycombinator.com/item?id=47558097