Pete Batard wrote: > and it seems Microsoft can't stick to a naming convention anyway (For > instance, in latest WinUSB redistributables [1] MS replaced "amd64" for > "x64" for the x86_64 binaries)...
Well, they do have to worry about pressure from their partners. When AMD first proposed the 64-bit extensions, it made a certain amount of sense to call the architecture amd64. After all, Intel had ia64, and there was no guarantee at the beginning that amd64 would end up being the de facto standard. By the time Intel "borrowed" the concept and named it EM64T, the Windows build tree already had the amd64 name embedded throughout. I assume this irritates Intel every time they see it, and so they keep having guys in nice suits whisper in the ears of Microsoft management that "it would really be more fair and accurate if you dropped the amd64 name". That's gradually happening over time. -- Tim Roberts, t...@probo.com Providenza & Boekelheide, Inc. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ libusbx-devel mailing list libusbx-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libusbx-devel
