as react-native dev, storybook feels like pilling a bunch of cards, you don't want to have to mess around with your base configuration, it's the worst. I've looked into alternatives multiple times, the closest I got is react-cosmos.

Is this basically the same idea that react native works? by sending and receiving JSON into the JS thread? but instead of a thread you just use a server, right?

10min later someone else posts another article from some random news website also using paywalls, so according to you now I have to subscribe again for this new website that has a minimum plan of 1..2 months, or maybe do I check for the annual subscription of $50 so I'm done with this website?

Your logic is so brilliant, I'm amazed.

that is not a fair characterization at all

laughs in tmux

not sure nothing happens when I get close to someone. Using Firefox 69 Dev edition on a desktop without webcam but with mic

just like any other side project: "Oh, that's easy to build" fast foward 10 weeks "Shit, this is harder than I expected"

First of all, it's hacker news, not a general news site. And while the width of breadth of the type of news you'd find on here is larger than just coding and other hackery, it's still at least usually based in technology. Like batteries. Still, the official guidelines say anything "a hacker might find interesting" and we seem to be a environmentally-minded bunch, so maybe it would fly.

Second, it's based on use submissions. You think we should know something interesting about the AU fires? Submit a good article about it I guess. If I and others learn something interesting, it'll get voted up. That's how it works.

It’s Monash University, not a news website, so doesn’t seem odd to me.

It's not a matter of "just learn WebAssembly", nobody (with some exceptions to those working on tooling) is going to learn raw WebAssembly, it just won't happen.

I would suggest that Blazor (C#) and Yew (Rust) are probably two of the most usable frameworks currently. There are some commercial libraries for Blazor and even some open source, but more is needed. There are ongoing and breaking changes that will be painful if you start adopting now.

Beyond all of this, is the fact that you still are interacting with the DOM via a transport layer that will generally not be great for a lot of use cases, you might do well with a canvas and animation frame events, but that won't have good accessibility.

Even then we're talking about native applications for portable devices, which likely won't see a good WASM story for a few years and in the case of Apple, if ever.

I'm not saying that WASM isn't cool... it really is, and you can do some very cool things with it as a target both browser and in dedicated runtimes... it's just not ready/baked for application targets (yet), and you shouldn't be betting a startup, or long-lived application on it just yet.