| Date: | August 13, 2007 / year-entry #295 |
| Tags: | history |
| Orig Link: | https://blogs.msdn.microsoft.com/oldnewthing/20070813-00/?p=25613 |
| Comments: | 11 |
| Summary: | Based on the feedback from my last CLR week, I think one CLR week a year is about right, Welcome to CLR Week 2007. I'll kick off the week with something not actually technical, but which might be puzzling to the newcomers: Why is the blog's subtitle "Not actually a .NET blog"? When I started,... |
Based on the feedback from my last CLR week, I think one CLR week a year is about right, Welcome to CLR Week 2007. I'll kick off the week with something not actually technical, but which might be puzzling to the newcomers: Why is the blog's subtitle "Not actually a .NET blog"? When I started, the blog hosting site for Microsoft technical bloggers was blogs.gotdotnet.com, and this site was consequently located at blogs.gotdotnet.com/oldnewthing. (The old address still works. Blog backward compatibility, I guess.) It was the .NET folks like Brad Abrams and Chris Brumme who started the big wave of Microsoft blogging in 2003, and when they set me up, they set me up with what they had. I chose the subtitle, therefore, because the name gotdotnet.com implied that all the blogs would be .NET-related, but mine wasn't. The blog moved to weblogs.asp.net and then to blogs.msdn.com, so the .NET assumption no longer applied, but I kept the tag line anyway. (If you want something technical for the start of CLR Week, may I recommend this puzzle from Eric Gunnerson on how overloaded functions are resolved in derived classes and this bonus puzzle from Neal Horowitz. Or, if you're more historically-bent, A Brief History of DateTime and A Brief History of DateTime Follow-up.) |
Comments (11)
Comments are closed. |
Ah, that explains it.
Until recently the favicon for blogs.msdn.com was a little .NET logo, so I always assumed it came from that…
"Welcome to CLR Week 2007."
woohoo!
The old url still works? That’s the trouble with you guys, layering on backward compatibility hack after backward compatibility hack. That’s why this blog is limited to one post a day! When will M$$$$ wake up and realize they need to start fresh! If a link breaks, call up the linker and tell him to fix his site!
This post is a good example of how features get implemented in Windows…and stay around long after they no longer make sense.
To be fair, us unix weenies struggle with backwards compatibility too. Why else would select(2) still be around? Or horror-upon-horrors, SysV IPC?
I’ll grant SysV IPC was a bad idea, but there were similar IPC systems around in the world. Maybe it was more a bad vision (I hesitate to say "implementation") of some of those other systems.
OTOH, select is easier to use than poll when you’re just doing something trivial. Consider a terminal / console application. You only have to worry about file descriptors up to 2. But select is loss for a server app where they can go up to a bazillion.
I just wish I didn’t still run into C runtimes where fileno field of a FILE is a char.
@Slashdot Guy
1 post per day of what? There are 2 posts today, and I can post multiple comments per day. So I don’t see how that fits. The 1 post per day thing typically done by Raymond is I think more choice than "limit"
tsrblke: You should adjust your sarcasm detector, sir. It seems to be malfunctioning.
See, "Slashdot Guy", that’s an interesting statement, because the links in old posts (which were on weblogs.asp.net originally) to other old posts (that were likewise on weblogs.asp.net) actually *don’t* work. :-P I believe weblogs.asp.net changed their archived-post URL scheme at some point, or maybe they just removed all the old posts when everybody moved to blogs.msdn.com. Either way.
I’m sure it’d be a PITA to go back and fix all those links, though, so Raymond: don’t bother. If it’s even possible. (It’s not too difficult to look the posts up here manually, based on date.)
Unfortunately, weblogs.asp.net no longer works.
Cool URIs don’t change.