5 ms·
Blowing up the backend and a 50ms freeze is comparing apples with oranges. If you have code that freezes the backend for 50ms you're unlikely to notice it. And
by wereHamster 5y ago
Blowing up the backend and a 50ms freeze is comparing apples with oranges.
If you have code that freezes the backend for 50ms you're unlikely to notice it. And if the code running in the browser blows up you're going to notice just like in the backend case.
Also, JS is not the only language that runs in the browser. You have TypeScript, as well as any language that compiles to wasm. If you want one that's not bad, it's up to you to pick one.
- globnomulous 5y agoTypeScript doesn't run in the browser.
- deleted 5y ago[deleted]
- globnomulous 5y agoAnd WASM isn't meant to replace JavaScript. Last time I checked, its use was discouraged for general-purpose web development. It's meant to be invoked in JavaScript, not the one tool used when writing an entire web app. If you want to write code that runs in a browser, JavaScript really is your only option.