[rvdginste]

> We are not just experiencing the demise of PC magazines, but also the demise of printed press and of major old news outlets.

I have the impression that nowadays most people no longer want to invest the time to read in-depth articles or books on a topic. Myself, I recently read a couple of technical books and came to the conclusion that a good technical book is still worth it. It explores a topic in a structured way and in-depth, and the information in a technical book is supposed to have been reviewed. If you read good technical blogs, you can pick up a couple of things here and there, but I think it will never be as efficient as reading a good technical book on a specific topic.

[Rapzid]

I agree. People wanting to learn C# are told to watch YouTube entertainer videos and read the Microsoft docs haha.

C# In a Nutshell still is worth it's weight IMHO.

[rvdginste]

That one is on my to-read list. Only hear good things about that book. And I see that C# 12 in a nutshell is just released.

[Rapzid]

Definitely recommend it. The difference in detail and insight on the HttpClient information between the book and the Microsoft docs is a good case study.

The docs are often limited to autogenerated API with some surface level remarks.

[beacon294]

Which books did you find worth it lately?

[rvdginste]

I am a .NET developer. I recently read "Concurrency in C# cookbook, 2nd ed" and found that one very interesting and clear. I mainly wanted a decent explanation on async-await, and the book has that. But aside from async-await, the book also explains other mechanisms for concurrency in modern .NET.

I am also reading Pro ASP.NET Core 7. I am not new to ASP.NET Core, but was surprised to learn some new things from the book.