> JS and TS brought so much happiness to me for years. But I found it extremely difficult to constantly have to "decide" between X and Y.

At least for me it was never a decision once I found TS, TS always got chosen. My spicy opinion in the JS space is that Typescript is better in every single way over Javascript, it is a superior language. Typescript IMO should be merged into Javascript, how anyone develops with just JS anymore (especially larger projects) baffles me.

TS has a lot of DNA from the failed ES4 attempt.

I think we need something quite a bit more radical than Typescript.

We have "use strict" and I think we need to add "use types" too.

In that mode, we need to disallow the more dynamic parts of JS. They add TONS of typing headaches resulting in poorly-typed projects and they hurt performance too.

This could allow for a much more simple type system and allow a path forward where things like type coercion aren't a thing.

Couldn't agree more. I want to see a "mostly pure" occurence type system with refinement types and HKTs on a SUBSET of ECMA.

Ignoring virtual dom, the number one thing that kept me in react was normalized event handling across every conceivable type of browser that the web could throw at you. Is that no longer a thing in 2021 or do all libraries handle it?

This is one of many things that were true when React was first created and is now no longer needed. I feel like half of React’s codebase is just reimplementing features that are now browser native.

It seems like they have painted themselves into a weird spot by drifting so far from web standards because the path back doesn’t seem that obvious from the outside at least.

I think I might try Golang, I would love to just code again. I'll look into Svelte as well.

Golang also has a rich ecosystem of external community libraries but

1) the standard library is often enough to get work done (http server, sql, etc)

2) external libraries often would simply sit atop the standard library which is easier to standardise and swap things around

3) the language is quite bare and simple, I was weirded out by the "for" in Go but I now like it. Need to map, filter, or increment counters? Use "for".

4) No need to hesitate between 5 linters or testing libraries, "go" does it so again it's standardised.

As for Svelte, I'm not loving it as much as Go but for frontend, it's just the most "JS/TS" of all without added layer of magic. There is still some, but it's graspable.

The truth about Svelte post of Rich Harris is very much in point about Svelte. It gets out of your way and feels like HTML/JS/CSS + a few thought out features. You can use a lot of libraries without a wrapper for svelte.

https://gist.github.com/Rich-Harris/0f910048478c2a6505d1c321...

I hope it gets adoption, I would like to work with it. I like React as well and use it but Svelte straight forward in so many situations that I just enden coding instead of thinking about X different ways to solve a problem and that is where I see similarities with Go.

same here, backend fully golang, no nodejs|expressjs|whatever-js