System instability and security issues are just fun! That is all I'm hearing. At this point I think we should have some sort of vetoing power on when a new kid comes in and says "I'll write it in C". He should give very convincing arguments on why he can't use a higher level, safer language. Too many people are allowed to "write it in C because it's fun" and here we are.

Kinda like riding a fixed-gear bike. To some, the sheer simplicity is a joy of its own. To others, little besides literal tooth-pulling even compares.

I feel it gives a fresh taste of freedom and simplicity. Like, comparatively no magic involved.

It is alot easier to reason about performance. The code does somewhat translate to the machine instructions you anticipate.

But the greatest advantage is all the fancy pants idioms you don't feel compelled to use.

I don't find it fun at all. I want to focus on what I want my program to do, not on how the computer does it, as long as its doing it reasonably efficiently. I want a successful compile to give me a decent amount of confidence that my program is correct, and is free of some classes of bugs.

Life is too short to waste time tracking down double frees, out-of-bounds writes, memory leaks, and weird concurrency issues.

Real-mode assembly is even more fun. I highly recommend something like http://www.sizecoding.org/wiki/Getting_Started if you're into that sort of thing.