4 ms·
ts is superset of js, so I wouldn't say you avoid it. It's like saying you run to avoid walking. On the web, I get that CSS is not straightforward, and HTML is
by frabia 2mo ago
ts is superset of js, so I wouldn't say you avoid it. It's like saying you run to avoid walking.
On the web, I get that CSS is not straightforward, and HTML is not the coolest technology, but by using the canvas you also lose a lot stuff that you need to rebuild from scratch: accessibility and interactivity, responsiveness, etc.
So the only argument that I'd buy is that it has lighter & more performant UIs, which I get it might, given that the canvas uses the GPU, but is it worth the effort? Like, is it THAT much better?
I get the argument of native apps though. I guess if you want to build one interface and serve it both as a web and native app, it could make sense.
Edit: thanks for the link - I'll look it up. Also I didn't mean to sound too annoying. I'm starting to see UIs built in Rust but I'm still struggling to see the hype.
- zionsati 2mo agoYeah all good. They're all good questions. My point around ts is people want strongly typed languages these days. The bigger problem with HTML/CSS is, when you're trying to do more sophisticated things (see the immediate drawing page on the demo), you'll find you need to use a canvas/HTML5. That then becomes a mini UI framework of its own... For simple webpages, HTML/CSS is probably still the best way to go. But I wouldn't say the same for webapps?