FUTURE POSTS
- Partial writes, IO_Uring and safety - about one day from now
- Configuration values & Escape hatches - 4 days from now
- What happens when a sparse file allocation fails? - 6 days from now
- NTFS has an emergency stash of disk space - 8 days from now
- Challenge: Giving file system developer ulcer - 11 days from now
And 4 more posts are pending...
There are posts all the way to Feb 17, 2025
Comments
Not sure I get the joke, but...
Are you somehow implying that BizTalk and Agile do not go together? gasp! Or is it framework-itis again?
You got that. :-)
The name doesn't quite roll off the tongue... Microsoft ESB Guidance June 2007 Community Release, Microsoft ESB Guidance June 2007 Community Release, Microsoft ESB Guidance June 2007 Community Release.... say that three times fast. You don't feel so agile now, do you?
I also find it ironic that they feel the need to inject the word Community into an already long title. Does insisting on a community make it so? Or is it meant to imply that most releases aren't meant for "the community", but this one is? Just call it "beta" and be done with it. That's the Web 2.0 way of implying "community", although leave it to Microsoft to invent/rebrand their own euphemisms... "Shared Source", "Community Technology Preview", "Rich Interactive Applications" instead of "Rich Internet Applications", etc. At least they dropped the "Technology Preview" part.
heh :)
Comment preview