I'm finding the very concept, and separation, of frontend + backend thinking has changed fundamentally in the past few years. There used to be a silly perceptio

I'm finding the very concept, and separation, of frontend + backend thinking has changed fundamentally in the past few years. There used to be a silly perception of frontend work as being somehow less-serious than the "real programming" you do on a backend. I'm sure you've found more and more in your react w/ gql work how little that applies now. Treating a browser like some kind of thin presentation layer there purely server-rendered html is very limiting. We've also seen a major trend in recognizing the importance of strict(er) types with the excitement around TypeScript. Functional programming is also seeing widespread adoption. The language that is best suited for including the browser as a target, taking advantage of an excellent type system, and applying functional programming concepts is without a doubt Rust. It has the steepest learning curve, but once you get the hang of a few concepts, you'll be amazed that you're writing a systems-level compiled language with perf comparable to C, because a lot of code is more readable than JS. People go on a lot about the performance because it's impressive, but that doesn't even break my top 10 reasons to use rust. Everything is so safe and thorough, it's one of few languages where I write non-trivial changes that actually work the first time I run them.