Hi, everyone. The Microsoft Developer Tools and Services folks have been kind enough to give my blog a new home. The new site has a mobile-friendly design, and redirections have been put into place¹ so that links to the old site will come here.²
The Developer Tools and Services folks also created a really nice graphic for me, which I’ve put at the top of the home page, though you don’t get the full effect unless you’re on a large screen. Sorry.
I’m still trying to figure out the new site, so don’t be surprised if there are things that look weird. In particular the formatting of most posts is messed up. I’m working to fix them in my copious spare time, but it will take a while to update over 5000 articles. I’m working backwards, so the oldest posts will be the last to be updated.
The new site doesn’t give me as many customization opportunities as the old site did, so my SVG and CSS magic diagrams may not come out right. I’ll work with the blog hosting folks to see how much of it I can get working again, but my first goal is to fix the worst of the formatting issues.
One thing you’ll probably notice is that comments from the old site were not carried forward. Sorry.
If you have other questions about the blog migration, you can check the Developer Blogs FAQ to see if they’re answered there.
If you have questions about the new blog site that are not answered in the FAQ, you can ask them here and I’ll try to find answers to them.
¹ Redirections for posts from February and March of this year haven’t yet been set up. Thanks for your patience.
² This blog has moved so many times, you can probably get some sort of frequent-traveler reward for going to a really old link and redirecting through multiple sites before finally landing here.
It should not have taken me four minutes to figure out how to post here again.
Now I am tasked with revising our Visual Studio toolbar yet again. I only did that last year. Because Microsoft no longer has stable APIs. They want to blame developers for their own ineptitute. "Asychonous loading?" The VS team thinks that will solve their problem? VS is dog slow. "Asyncrhonous loading" will not solve their problem. VS 4.x will...
And BTW Ramond -- and I know this might be heresy... I personally have always belived that Windows has a better design that of Unix/Linux. Partially, because I dont want some stupid clone of an operating system from the seventies. My problems with Windows are the following: the unfortunate accident of the VMS pathnames. The unforunate accident of drive letters. Through an accident of history, it doesn't fit with the C language. Also, Control-C should...
I know this is quite an old post now but it seems the most appropriate one to reply to. Your posts used to show up regularly on time, practically every day (it was 3pm for me except on days between DST transitions (as in, my DST transition has happened this year, yours hasn't, or vice versa)).
But since the move, they don't seem to be showing up at the same time. Have you lost the...
Scheduling is not working. Even automated posting is not working. (The XML-RPC endpoint accepts the post but does not publish it.) Must be done manually. The server folks are investigating.
Comments used to auto-close 2 weeks after a post was posted; if this comment is submitted successfully, then it seems that’s no longer the case.
Well, one bonus is that I’ve lost the (Copy 1) from my account.
Also, I just have to say it. The new site is slow – much slower than the old site ever was. It is unbelievable how long pages take to open – we are talking 5-15 seconds. Yes, I submitted this as feedback already, but this just cannot be said enough times. The “upgrade” has been a strict downgrade so far.
Just timed the refresh of this very page to make it painfully easy to understand what it is I am talking about. The refresh took 7.8 seconds. And even after that there was quite a bit of activity in the status bar (using Chrome, no plugins). Anything longer than 2 seconds is unacceptable, and completely out-of-this-world unbelievable for the type of content we have on this page and its amount (utterly miniscule).
The loss of comments to all previous posts is catastrophic.
I have been a reader of this blog since its inception and the knowledge I got from it was enormous. But the majority of the knowledge actually came from comments, not from posts! In terms of knowledge, the value of this blog has been roughly: 20% in the posts from Raymond, 20% in the comments from Raymond where he was answering comments of others, and...
Login with MSFT account works, with Google account does not. So I may not be myself today… Anyway, I wish the RSS feed would consistently include the entire post; makes it a lot easier for quick skimming a bunch at a time. It’s gotten spotty since the Grand Move.
I have no idea how many moves I’ve followed, but I’ve been reading here a long, long time….
A new comment to help debug the site behaviour.
This is precisely why people hate Microsoft, if you choose to understand it.
Lately, I've been picturing myself interviewing you, like James Lipton on "Inside the Actors Studio"... because you're such a facinating person, and I have so many questions to ask you. [One of my core functions is to understand the NT loader without reference to source code.] But also, I feel the need to explain to you why even the highest thinkers hate...
"Now I learn that all my past comments here--from over a deade ago--are lost. This is why people hate Microsoft. Need I explain this further?"
No, no it's quite clear that you won't try and understand the reasons behind actions since it's much easier to simply "hate Microsoft".
Why bother understanding the problems behind GetVersion (and why guidance has been for decades to not do version checks but instead check to see if the...
The reasons behind loss of comments were "we have to somehow map old accounts into new ones and we don't want to add means to do that". Compared to the effect of the loss of comments - a huge loss of value, because on this particular blog, as well as on several other MSDN blogs, comments carried something like 80% of the value - this is just pathetic. At the very least, there should be...