I hate to say it, but Windows is much more productive than MacOS for the usually tasks you perform on an OS (with GUI, both have CLIs, but I'm not talking about them). I'm using both at work all day long switching between them. When reflecting why, I think it comes down to windows management and the file explorer (vs finder).
Yes, quite an oversight ... as Vue has it all: Adoption, maturity, ecosystem, features, DX and speed (with upcoming Vapor mode even on par with Svelte and Solid).
It's quite an oversight of the author did not to include Vue. Vue has it all and is as of now in terms of DX, features, ecosystem and performance (with upcoming Vue Vapor mode basically the same as Solid and Vue) the best choice.
No OP, but I've also used Angular, React, Vue, Solid and Svelte in real world projects and my default choice is Vue, because it's on par with Solid and Svelte (and with Vue Vapor those three are basically the same) but with the larger ecosystem (vuerouter, vueuse, nuxt, nuxt-ui, primevue, nuxt-content, ...). I must also say that React was by far the most unpleasant and unproductive to use.
The most infuriating thing is that people still believe that you need isomorphic rendering (Next, Sveltekit, Nuxt) to have a fast, interactive and SEO friendly apps.
It can. DX is pretty much the same for backend and CLI stuff using VS Code on Mac, Linux and Windows. I'm working daily on C# backend and CLI stuff on a Mac (those are the dev machines at my employer). DX is on par with Go and Rust (at least dotnet CLI, LSP, Debugger, I can't speak for the profiler as I've never used it). I like the Rust tooling most, but dotnet CLI is not far behind.
Language and std lib wise, C# sits in the sweet spot.
After reading the long Github thread, I think you're right. It's probably just as simple as "what is the easiest way to copy our TS code 1:1 to a faster language". And this case Go wins due to its simplicity.
Thanks for the link. I'm not fully convinced by Anders answer. C# has records, first class functions, structs, span. Much control and I'd say more than Go. I'd even say C# is much closer to TS than Go is. You can use records for the data structures. The only little annoyance is that you need to write the functions as static methods. So an argument for easy translation would lead to C#. Also, C# has advantages over Go, e.g. null safety.
Sure, AOT is not as mature in C# but is this reason enough to be a show stopper? It seems there're other reasons Anders don't want to address publicly. Maybe as simple reasons as "Go is 10 times easier to pick up than C#" and "language features don't matter when the project matters". Those would indeed hurt the image of C# and Anders obviously don't want that.