

Let’s look at a scenario where there’s an exploit that requires a change to an API. With JavaScript, the browser vendor can ship a fix to the API, and web devs update their code. With a plugin, the browser vendor ships a patch, then the plugin vendor needs to ship a patch, and then web devs need to update their code. Some plugin vendors will be slower than others, so the whole thing will see massive delays and end users are more likely to stick to insecure browser versions.
Plugin vendors are going to demand the same API surface as current web standards and perhaps more, so you’re not saving anything by using plugins, and you’re dramatically increasing the complexity of rolling out a fix.
I think the current web is a decent compromise. If you want your logic in something other than JavaScript, you have WebAssembly, but you don’t get access to nearly as many APIs and need to go through JavaScript. You can build your own abstraction in JavaScript however to hide that complexity from your users. The browser vendor retains the ability to fix things quickly, and devs get flexibility.
Are you really going to take it into the woods with just two seats, mediocre suspension (likely, given the limited payload and towing), and limited range? Just get a Polaris side-by-side or something, they’re built for that.
I get it, a cheap truck is appealing, but at this price target, it’s going to make a lot of compromises. It should do fine in plowed roads (might need sandbags in the back though), so it’ll probably be fine for around town use, which seems to be its target.