3 ms·
Although this document is old the thing that strikes me reading it is how utterly irrelevant and cryptic it is/was. Perhaps the closed nature of Microsoft's tec
by jsz0 17y ago
Although this document is old the thing that strikes me reading it is how utterly irrelevant and cryptic it is/was. Perhaps the closed nature of Microsoft's technologies makes it harder to understand but isn't that the problem? I don't know why I might want my Federation server to talk to my extranet server through passport via Yukon calls, based on the BizTalk platform, and highly integrated with the CLR but only for a 3 month trial period if my Office license is up to date. Assuming of course my Trident version is new enough to support my VS Forms. I'll have to check my MSMQ in MMC first though.
- jodrellblank 17y agoIt's an internal memo, not a Microsoft HOWTO - it's not trying to explain to you what the jargon means. You can't take competing technologies and tell me they have any fewer awkward acronyms, buzzwords, competing technologies, license limitations, interconnectivity and so on.
- jsz0 17y agoThat's true. I understand that angle of it. I just think Microsoft should be asking themselves what can we do to improve the experience of 90% of our users instead of spending all our time worrying about how to improve the amount of money we make from the 10% of our most profitable users which is, I think, what all this jargon adds up to. It seems like with Windows 7 they have taken the 90% approach more so than in recent years which is certainly a good thing.