Posted By: CRPietschmann | Oct 28th, 2005 @ 9:54 AM
page 2 of 2
Comments: 30 | Views: 22334
TommyCarlier
TommyCarlier
I want my scalps!
The terms 'big endian' and 'little endian' come from the time when America was still ruled by the native Americans. There was a discussion between the 2 endians (a tall one, and a short one) that worked on a new wireless communication protocol: BIN/DRUM (binary over drum). They couldn't decide whether they should first send the least significant byte, or the most significant byte. So they both developed their own system, known as 'big endian' and 'little endian'.
DevilsRejection
DevilsRejection
addicted to rss
Scoble, if you could expand on the show notes a little bit more. Instead of just a brief paragraph about what is going on, maybe throw in a link or two to content relevant towards that video.

Also, to WHOEVER you interview. In the shownotes can you include a link to their blog?

There are certain videos where they present new technologies though do not give scenarios, which makes it hard to understand how to utilize the technology.

The most recent video which I can remember with that problem, is the Windows Workflow Foundation one, where it seemed really interesting and innovative though I couldn’t put my finger on how to use it with my own solutions.  So when interviewing it would be great if one of the examples could be a more scenario specific one.

Thanks

Shmuel

Larsenal
Larsenal
ready to give an answer
Shmuelpro wrote:

There are certain videos where they present new technologies though do not give scenarios, which makes it hard to understand how to utilize the technology.

The most recent video which I can remember with that problem, is the Windows Workflow Foundation one, where it seemed really interesting and innovative though I couldn’t put my finger on how to use it with my own solutions.  So when interviewing it would be great if one of the examples could be a more scenario specific one.

Thanks

Shmuel



Good point.  I agree.
page 2 of 2
Comments: 30 | Views: 22334
Microsoft Communities