EDN Admin
Well-known member
I caught up with Erik Meijer recently to see what was on his mind (wish we could do this more often as his mind is typically full of very interesting things at any given time!). Erik had just read an article - http://architects.dzone.com/articles/every-programmer-should-know" target="_blank Every Programmer Should Know These Latency Numbers - and it got him thinking...
Here, Erik discusses his perspective on latency. We also discuss native relativity, energy efficient programming (what does that mean?) and nutrition labels for software <img src=http://ecn.channel9.msdn.com/o9/content/images/emoticons/emotion-1.gif?v=c9 alt=Smiley />. As usual, this is classic C9: the conversation just happens and its all captured in audio and video. Whiteboarding included. Twists and turns, too. Always a real pleasure to get the chance to geek out with Erik. Thank you, Dr. Meijer! And remember, energy can neither be created nor destroyed, but moved from state to state and place to place. It should be fairly obvious how this relates to the energy required to compute your code in this age of clouds and battery-powered personal computers (aka phones...). How much energy does your code use? How could type systems help here (could they?)? Tune in. Think. <img src="http://m.webtrends.com/dcs1wotjh10000w0irc493s0e_6x1g/njs.gif?dcssip=channel9.msdn.com&dcsuri=http://channel9.msdn.com/Feeds/RSS&WT.dl=0&WT.entryid=Entry:RSSView:977093358d444f29b7f7a097014653e8
View the full article
Here, Erik discusses his perspective on latency. We also discuss native relativity, energy efficient programming (what does that mean?) and nutrition labels for software <img src=http://ecn.channel9.msdn.com/o9/content/images/emoticons/emotion-1.gif?v=c9 alt=Smiley />. As usual, this is classic C9: the conversation just happens and its all captured in audio and video. Whiteboarding included. Twists and turns, too. Always a real pleasure to get the chance to geek out with Erik. Thank you, Dr. Meijer! And remember, energy can neither be created nor destroyed, but moved from state to state and place to place. It should be fairly obvious how this relates to the energy required to compute your code in this age of clouds and battery-powered personal computers (aka phones...). How much energy does your code use? How could type systems help here (could they?)? Tune in. Think. <img src="http://m.webtrends.com/dcs1wotjh10000w0irc493s0e_6x1g/njs.gif?dcssip=channel9.msdn.com&dcsuri=http://channel9.msdn.com/Feeds/RSS&WT.dl=0&WT.entryid=Entry:RSSView:977093358d444f29b7f7a097014653e8
View the full article
