Hacker News Reader

Comment by Freedom2 | Hacker News Reader

This is great! I've had a bit of a play around and the code examples are nice and easy to follow. Definitely liking it more than the JSX route that a lot of modern frameworks are taking these days - this way is much cleaner and easier to read.

View on HN

I’m struggling to see how this is cleaner and easier to read than JSX.

JSX resembles web technologies, it “smells and looks like” HTML and JavaScript. It’s easy to pick up and read. If you know HTML and JavaScript, onboarding to React isn’t bad.

However, this framework looks like an abomination for real world usage. It’s in WASM, written in Rust (!?). It doesn’t resemble any sort of web technology other than the tag names. How do you onboard a frontend team to this?

Perhaps to rust-aceans, this makes sense. Is there something I’m not seeing here?

I think that whole point is to not resemble Javascript. I kinda like it, in my experience current state of JS is layers and layers of tools stitched together over language that was designed for much simpler times. Compared to other stacks I worked with it's often unstable, slow and poorly documented. I tend to avoid doing fronted if I can.

Fresh and different look at this topic is something I would very much like to see. Of course for people working with front end today may have different perspective.

It still targets the browser though, so you still get all the complexities anyway, just without well supported syntax. Idk man I like Rust but this doesn't seem like the right way here.

I agree with you. I don't think anyone who has spent enough time with React/Vue.js would want to switch to something like this. I cannot imagine what the code would like when you have a lot more components and nesting.

I would write frontend code like this if I really want to punish myself.

Reply on news.ycombinator.com