etep

12 ms·

61.
by etep 12y ago
Can't find Palo Alto...
62.
by etep 12y ago
This: Git is so amazingly simple to use that APress, a single publisher, needs to have three different books on how to use it. It’s so simple that Atlassian and GitHub both felt a need to write their own online tutorials to try to clarify t
63.
by etep 12y ago
Where does the memory capture come from?
64.
by etep 12y ago
I would like to see stats beyond those provided by top. For example, memory bandwidth (broken into read and write bandwidth). IO bandwidth. CPU cache hit rates. Instructions per cycle. Energy consumption. AFAIK there is no really nice way t
65.
by etep 12y ago
Gate count is not the issue - the issue is L1 timing. For clocks at 2 GHz plus, there can be very few stages of logic in between flops. Just decoding an address to a one hot wire (necessary to access the memory bank) takes up a good chunk o
66.
by etep 12y ago
Wow. Am currently reading "The Mockingbird Next Door" by Marja Mills. Brifely, Marja gained unprecedented access to the private life of Nelle Harper Lee. It is extremely interesting, and I am quite surprised at this turn of events
67.
by etep 12y ago
Version number is micro, this is a macro question, to wit, the following: When I converted a perl script to python and saved 50% LOC I didn't know which version of which I was using. Am only vaguely aware of the Python 2.x vs. 3 issues
68.
FPGA tic-tac-toe(instructables.com)
2 points by etep 12y ago|0 comments
69.
Computing's energy problem and what we can do about it(isscc.org)
2 points by etep 12y ago|0 comments
70.
by etep 12y ago
A link to the ISSCC keynote by Mark Horowitz, curator of cpudb. IMO worth a listening to for most anyone interested in CPU performance related issues. http://isscc.org/media/2014/plenary/Mark_Horowitz/New
71.
by etep 12y ago
So basically e-commerce sites are charging me more?
72.
by etep 12y ago
Obviously, but I edited my comment. My inner pedant jumps for joy.
73.
by etep 12y ago
I'm not sure if this is meant to contradict my comment somehow, but I think we are saying the same thing -- read differently, it sounds like you might be suggesting they don't even need the new data. Whether on VMS, or notice to m
74.
by etep 12y ago
I hope the U.S. Navy incorporates this into their nautical charts, but, sadly, I doubt they will. I wonder if this data would have prevented the 2004 undersea collision of the USS San Francisco. see, e.g., http://en.wikipedia.org
75.
by etep 12y ago
I never knew about this place, but now I'm certain I will be getting in the water there soon.
76.
by etep 12y ago
So you're saying there is a self referential satire of the religion of lisp + emacs. That is good ;)
77.
by etep 12y ago
This is not a half baked study. The right comparison is being made, namely performance versus energy. Further, they attempt normalized comparisons, here quoting: To factor out the impact of technology, present technology-independent power b
78.
Computing's Energy Problem and What We Can Do About It(player.vimeo.com)
1 points by etep 12y ago|0 comments
79.
by etep 12y ago
I disagree. The writing is excellent: pragmatic and insightful at the same time. In fact, your quote is a great example of its high quality. I don't need, nor do I like, the heavy handed style of some authors. Eloquent JS is eloquent b
80.
by etep 12y ago
wow, that is awesome
81.
To understand how jealousy works, take a look at your dog(washingtonpost.com)
2 points by etep 12y ago|0 comments
82.
by etep 12y ago
> The password quality is just adequate, but I think the idea has potential to be very secure. The op makes no broad claims. I think your insights are helpful, but I would change your wording from "Congratulations" to "unf
83.
by etep 12y ago
The author of the paper follows this quote with a rant against the referees for scientific journals and conferences. Perhaps I should have quoted that. There must be a reason why Lamport, Knuth, etc. don't write in this style. But, the
84.
by etep 12y ago
Usually statements such as "This paper has some serious significance both scientific and historical." (quoted from the article) are a flag of the exact opposite. I would need more context from a more trusted source to inform my ow
85.
by etep 12y ago
The number one thing to know here: In most programming languages, each statement is implicitly sequenced, unless told otherwise (e.g. pthreads, or openmp) In a hardware description language, each statement is concurrent with all others, unl
86.
by etep 12y ago
A good point, and I would agree that Haskell is a good candidate for HDL. The following project nicely captures what I think of as a good direction (except for dependence on the JVM which is cross platform torture): https://chise
87.
by etep 12y ago
In a general purpose language, every line of code is implicitly sequenced, until told otherwise (e.g. for each in parallel, do...) In a hardware description language, every line of code is executed in parallel, unless explicitly sequenced.
88.
by etep 12y ago
So this would be limited by main memory bandwidth, if implemented correctly, but I doubt it even is limited by that right now (i.e. because it is apparently single threaded, and one core typically won't be able to saturate main men ban
89.
by etep 12y ago
How I Became a Famous Novelist by Steve Hely
90.
Airdog: first action sports auto follow drone(airdog.com)
5 points by etep 12y ago|0 comments

More ›