I do believe there is value in understanding the fundamentals of how the computer executes code by learning C as it is a nice balance without going to the level of Assembly. I don’t think I would be as good of a programmer as I am today without having learnt C as my first language but the way the school teaches it is important.

That said, that’s in the context of a role of a software engineer with a CS degree, if you’re just a regular developer writing web apps or plan on only ever using frameworks then yea, you probably don’t need that kind of knowledge. Even then, I’d argue knowing these details would help you resolve issues with the framework if you ever encounter them.

It doesn’t necessarily mean you have to use C to make products but it certainly is useful to get a feel of how it works.

Yea I wasn’t a fan of it initially coming from C++ and C# but it is growing on me. There’s a lot of neat concepts. I just wish it’d allow me to put curly braces on the next line.

The JVM isn’t free. It was a simple data collection device that interfaces with a sensor which ideally doesn’t need maintenance as long as possible. Something light written in C is more than enough.

Battery life is a reason. I’ve had clients come to me complaining their solution from another vendor didn’t last very long. Turns out it was running Java on an embedded device.

I found SourceTree to be especially bad at this. For the inexperienced, I think Fork is a lot better. It also helps that you can inspect the commands that were executed by it.

Haven’t dabbled with them yet but I’ve heard of Avalonia and Compose.

I’m not too familiar with slinr or fybe but DearImGui seems like an odd one out here.

And it’s so good that Kotlin adopted them too in their journey to fix Java.

Funny you list both C# and Typescript because the lead architect of C# also worked on Typescript.