@RyanCarniato@philthistweet I'm joking of course, but also kinda not.
I think it's not as hopeless as everyone thinks. Just treat it like an incremental migration. Add legacy support for the classic web, but ship a brand new browser that can run Rust or Go or Zig directly if it finds it.
It could happen
@RyanCarniato@philthistweet 100% this.
It would be cool if someone reinvented the entire web platform so we could use a "better" language.
I'd trust @RyanCarniato with that task. 👀
@amanuelodicho@solid_js@reactjs At this point I am a Solid evangelist, I love to recommend it to anyone who still uses React.
This post is interesting to me, because you seem genuinely smart, so there must be a gap to fill here. As someone getting more into open source lately, it feels like an opportunity.
@dogwith1eye if (cond) {
render(<p>hello world</p>)
}
this is how it was explained. Meaning render is an impure function... meaning impure stateful updates are being sugared away.
Not saying that necessarily makes it BAD, but it may evoke some aversion to the more functional-minded...
@trueadm@jadengis You MAY win me over if you say there's no fake JS and you can guarantee all new or lesser known JS syntax is never going to break inside the compiler...and also that you have human readable Errors that are never EVER cryptic...and a dev mode that serves readable code...lol
@piq9117 It's funny, but unironically would make me want to work with you.
My two cents - gotta put out the energy you wanna get back from your next employer
@TotherAlistair Before I can try to change your mind, I think I need to understand your claim better.
Knee-jerk reaction: code quality matters to AI the exact same way it matters to humans. If it gets bad, it confuses the AI, makes it slower, and more prone to bugs, just like human teams.