WASM is not so supported, but it's not like a major technology right now.
If you need complex UIs, separate backend and frontend and write the latter in something well supported (like, i dunno... JS)
"The days of crappy NPM packages are over" said no one ever, and no one will ever say.
TS is never going to catch up with Go performances, and the lack of IPC and true concurrency actually is very bad for backend services that need to handle stuff.
I think the OP wants to use Go for stuff that isn't supposed to do with.
esbuild is a bit unfair example because Go is really great fit for this kind of job, it does a lot of I/O, it allocates a lot, and then it just dies. evanw even tried to use Rust at first but it was slower than Go version.
You can define "take over" in different ways to change the answer. Put yourself into the position of some big customer. Will you change your usage profile to get really cheap electricity, or not? Solar will or won't take over the customer you're thinking of.
Many people don't grasp how cheap solar is becoming. We're close to the point where solar+batteries becomes the cheapest way to provide nighttime power in a few regions, which astonishes me. And the prices of both solar and batteries still drop quickly.
Exactly. We need something to generate baseload instead of coal and natural gas. Nuclear, geothermal, and hydro are our best options.
The other major issue to address with solar: the mining of materials, manufacturing and distribution of solar panels absolutely requires fossil fuels. There has never been a solar panel or wind turbine created without it - not even as a demonstration, let alone the decades it would take to build out the infrastructure. If solar "took over", it would only do last another 20-25 years without a viable supply chain.
Put another way: the sun and the wind are renewable, but solar panels and wind turbines are certainly not. And without a viable path to a carbon-free supply chain, we'd be on borrowed time. As such, it's more accurate to think of "renewables" as fossil fuel extenders, allowing us to burn carbon and spread the energy return out over a couple decades.
Ha I forgot about that. TOML is pretty awful too. It's fine as long as you only need 1 level of nesting. As soon as you need to go deeper than that you end up with [[weird syntax]] that is very not obvious. I would say it's less obvious than YAML and YAML is already pretty unintuitive.
Addendum: no spam no adv, i suggest the web dev, css and js online courses from Jonas Schmedtmann, i learned from his courses and he's absolutely a nice teacher.
WASM is not so supported, but it's not like a major technology right now.
If you need complex UIs, separate backend and frontend and write the latter in something well supported (like, i dunno... JS)
"The days of crappy NPM packages are over" said no one ever, and no one will ever say.
TS is never going to catch up with Go performances, and the lack of IPC and true concurrency actually is very bad for backend services that need to handle stuff.
I think the OP wants to use Go for stuff that isn't supposed to do with.