http://techland.time.com/2013/06/28/this-time-for-sure-altavista-to-die/
Sunday, June 30, 2013
Friday, June 28, 2013
Sunday, June 23, 2013
Saturday, June 22, 2013
Friday, June 21, 2013
Skynet, a Tor-powered botnet straight from Reddit
https://community.rapid7.com/community/infosec/blog/2012/12/06/skynet-a-tor-powered-botnet-straight-from-reddit
Thursday, June 20, 2013
Wednesday, June 19, 2013
Tuesday, June 18, 2013
Monday, June 17, 2013
Saturday, June 15, 2013
Go to statement considered harmful
Link to the (classic) article at the ACM. The abstract follows.
http://dl.acm.org/citation.cfm?id=1241518&coll=ACM&dl=ACM
http://dl.acm.org/citation.cfm?id=1241518&coll=ACM&dl=ACM
To many people, Dijkstra's
letter to the Editor of Communications of the A CM, published in March
1968, marks the true beginning of structured programming. That it
influenced the industry is clear, if for no other reason than for the
articles it spawned, ranging from "IF-THEN-ELSE Considered Harmful," to
"The Else Must Go, Too," to "Programming Considered Harmful."
In form and content, Dijkstra's letter is similar to his 1965 paper, which appears first in this collection. Description of the inverse relationship between a programmer's ability and the density of goto statements in his program is repeated, as is the emphasis on the limited ability of the human brain. Much of the discussion is somewhat theoretical in nature, and the typical COBOL programmer will hunger for some coding examples so that he can see why goto statements make program logic harder to understand.
Echoing his 1965 paper, the last few paragraphs underscore once again why the subject of structured programming stayed out of the mainstream of the data processing industry for so long. As Dijkstra points out, goto statements were a subject of discussion among academicians as far back as 1959. But even today, people whom Dijkstra acknowledges --- names like Wirth, Hoare, Strachey, and Landin --- are not well known to business-oriented or scientificoriented programmers, so it should be no surprise that their ideas have languished for so many years.
In form and content, Dijkstra's letter is similar to his 1965 paper, which appears first in this collection. Description of the inverse relationship between a programmer's ability and the density of goto statements in his program is repeated, as is the emphasis on the limited ability of the human brain. Much of the discussion is somewhat theoretical in nature, and the typical COBOL programmer will hunger for some coding examples so that he can see why goto statements make program logic harder to understand.
Echoing his 1965 paper, the last few paragraphs underscore once again why the subject of structured programming stayed out of the mainstream of the data processing industry for so long. As Dijkstra points out, goto statements were a subject of discussion among academicians as far back as 1959. But even today, people whom Dijkstra acknowledges --- names like Wirth, Hoare, Strachey, and Landin --- are not well known to business-oriented or scientificoriented programmers, so it should be no surprise that their ideas have languished for so many years.
Friday, June 14, 2013
Thursday, June 13, 2013
Wednesday, June 12, 2013
Sunday, June 09, 2013
Friday, June 07, 2013
Thursday, June 06, 2013
Sunday, June 02, 2013
CPU speed vs efficiency
I have been tasked with finding a lower power consuming solution while preserving performance.
The chart below is sorted by Total CPU performance but there are also other factors such as can your application use 4 CPU's or will it just be limited to one or two while the rest go unused.
We are currently using an i5-650 that is 73 watts for 2 core at 3.2 GHz. I quick look shows the i3-3225 at 55 watts for what is a slight performance gain of 2 cores at 3.3 Ghz.
I found it interesting that there was such a strong relationship between lower CPU speeds and more efficient operation. I can't help but feel this is more then physics at work but more organizational mandates and a side effect of the way their requirements are put together.
This is across all Intel CPU's after 2006 or so up to the current ones shipped.
Speed is (GHz * Cores) / 21 , the fasted being the i7-3970X 6 cores at 3.5 GHz.
Subscribe to:
Posts (Atom)