This is a good example[1] at 64k LOC removal. We removed built-in support for C# + WinRT interop on Windows and instead required users to use a source-generation tool (which is still the case today). This was a breaking change. We realized we had one chance to do this and took it.
I quite enjoyed both series. They are not similar (as you implicitly suggest).
Wayfarer bugged me at first because each book is a massive departure from the next (somewhat like Ender 1 and 2). As much as it pained me to leave the characters of the first book, the following books were more meaningful and stayed with me much longer.
This is all true. The only part that is potentially misleading is that the target doesn't need to be a blog. A blog is a fine target, however. The key activity is spending time to articulate a message with enough clarity that another person will understand what you meant and that they will conclude there is some value in it. There are lots of avenues for this.
It's not limited to this, but in the workplace I think of this as "write it down culture". People who write things down often have the most tested and credible ideas, with the first and most important judge being themselves.
It really does sound amazing. Would have needed this when you guys (hn) and reddit helped me figure out what a rogue Raspberry Pi was doing in our server closet
The bulleted list in the design point section is intended as a high-level summary. We may do another post later that is part-way between the bulleted list and the post as a whole. Perhaps that would be the last post in the series.
https://learn.microsoft.com/en-us/dotnet/csharp/language-ref...
reply