.Net

Garbage Collection and Pointers

So, Richard Hale Shaw is helping us move away from C++ and in his latest posting on the subject he explains how “veteran C++ programmers” don’t like to manage memory themselves; hmm. I’d quite like to see his sample data. Especially as he then goes on to define “veteran C++ programmers” as people who don’t like to manage memory themselves… *“But veteran C++ developers testify that - without taking special precautions - you’ll invariably introduce more programming errors by managing memory yourself:

Disappointing .Net Sockets article in MSDN Magazine this month

There’s a rather disappointing article on .Net sockets in this month’s MSDN magazine. Updated 5th May 2023 to fix broken links The title of the piece is “Get Closer to the Wire with High-Performance Sockets in .NET” which nicely over-hypes the content. How, exactly, am I getting closer to the wire by placing a managed layer between my code and the wire? The summary box is a little more honest; describing the article as covering “basic socket programming” and “factors in creating socket-based servers” which it does…