You'd think so, given the run around from Amazon that I've experienced thus far. I pre-ordered the book in May. So, when it was finally shipping, I expected to receive a copy a few days later. No emergencies.

However, like a few others, I got an e-mail from Amazon that my order had been back-ordered till October! Figuring that it was a mistake, I waited about a week before following up. Still back-ordered when I checked yesterday, yet the web page for the book lists it as, in stock, with immediate shipment!

Frustrated, I wrote Amazon to check on the status.

Response:

First, please allow me to extend my most sincere apologies for any frustration this matter has caused.

Sometimes unexpected fluctuations in supply can add time to our original availability estimate. We have learned that "3D Programming for Windows (Pro - Developer)" is now back-ordered, and our supplier has not been able to let us know exactly when they expect to have more in stock.

Please understand that the availability and shipping time frames listed on our web site are estimates, not guarantees. While we do our best to adhere to these estimates, our inventory is constantly changing based on information we receive directly from our suppliers.

If all of the items in your order are listed online as "In Stock," this indicates that we have at least one of each item on hand.

Depending on which shipping method you choose, your order could be packaged, prepared and shipped out in as little as a few hours.

What? (Wow, they could work on the helpfulness their canned responses!)

My response to that e-mail was a bit more terse, asking for something a bit more 'precise' and helpful.

Response:

I have reviewed our previous correspondence with you, and I offer my sincere apologies for any misunderstanding thus far.

"3D Programming for Windows (Pro - Developer)" has proven to be a very popular item.

We have many customer orders for this item, and we've just begun receiving copies from our suppliers. We are filling orders as quickly as we can on a first-come, first-served basis.

Further, I have checked your order and can confirm that we are currently preparing it for shipment.

I have investigated your order and determined that the estimated shipment and delivery dates displayed in Your Account was incorrect. Please accept our sincere apologies for this error.

It appears that we will be able to ship your package earlier than the date estimated on our web site, and we expect your order will arrive within two business days of the ship date.

What have I learned now? That I should expect my order as my book is being boxed right now. Also, good news for Charles is that the book has proven to be a very popular item.

Amazon's web site for my order this morning:

Yay! Delivery in a month and a half! Progress. [slap].

At this point I hope it's just a database update error, because I'd hate to know that the helpful customer service person lied to me.

By the way, BookPool currently has the book listed as In-Stock for $2 less than Amazon.

(And I know that others have had luck canceling and reordering. I prefer not to at this point as my price for the book is $3 less than what they're selling it for now.)

Posted by Aaron at 7:42 AM | Permalink | Comments (2)

If you were worried about the performance of a new application you were creating, would you pick WPF? What if it was critical that the application be fast? Would you pick WPF? I think Microsoft is overselling the performance of WPF still. I was hoping that WPF in .NET 3.5 would contain some nice perf enhancements, but nothing much seems to be listed (and I'd expect that they would).

I don't want to buy a new machine to make a marginally "better" application faster. That's true of nearly everyone, especially businesses/enterprises.

Pablo suggests WPF for an application that requires: "Fastest possible 2d grid control."

I personally think that's the wrong way to go. WPF isn't ready for super fast applications. The reality of most developer's days is that they don't have time to "evaluate" technology options much; maybe time to decide should they use a flat button or a 3D button, but they just need to get their work done. Microsoft absolutely needs to provide better prescriptive guidance in these cases that aren't self serving to a particular product/team whenever possible. (In this case, the developer was already committed to C# it seemed, so they had already picked a Microsoft platform).

What do you think? Comment here, or on Pablo's site.

Posted by Aaron at 8:50 PM | Permalink | Comments (1)