For high level programming, is the value of simplicity really that important, realistically? I'm talking about manifestos like the [grug brained developer](https://grugbrain.dev/) and [harmful.cat-v.org](http://harmful.cat-v.org/software/java) where most rants point at Go as a better alternative. From my personal experience, Go is very nice to develop in exactly because of the focus on simplicity, but I'm struggling to find a realistic use for Go. Want to build a web-stack? Modern tools like Next.js, web workers, supabase etc. makes this process very easy, even though you have to write JS/TS which does not value simplicity as highly. New tech like Blazor and LiveWire lets you ditch the API pattern altogether when all you want to ship is a website. These techniques can reduce complexity in terms of how much code you need to write and maintain by ditching the frontend-backend bridge, but might introduce more complexity overall by having to use, say, C# for Blazor which is ever-growing with complexity and over-engineering. So, is it worth still sticking to Go and go with the good old fashion backend API + frontend pattern in your opinion?

When it comes to low level programming and simplicity, I struggle to find use cases for Go since we are often looking for real-time and highest performance (which Go compiler prefers speed over optimization). However, I think I'm starting to prefer C over Rust after writing a little C and previously a lot more Rust. Because I simply don't see the benefit of kinda-but-not-really-guaranteed safety with a lot of added complexity and cognitive load over the simplicity of Go or C for general purpose development. I.e. development where safety isn't a priority, because then I think Ada would be a better fit with stronger safety guarantees, no?

And sorry if it's controversial. I'm not looking to start a flame war, but I'm genuinely interested in learning different opinions on the matter.