ssp

19 ms·

181.
by ssp 16y ago
Dabrowski and Munson weren't able to reproduce the old 50- or 100-millisecond rule of thumb in what sounds to me like a poorly-controlled experiment It sounds rather poorly-controlled to me too. They mention that they didn't account for t
182.
Can ARM Kill Intel?(electronicsweekly.com)
48 points by ssp 16y ago|59 comments
183.
by ssp 16y ago
Notice the dropdown menu when he types in the address: it says "Broadway 2.0".
184.
by ssp 16y ago
That's pretty clever. It can be tempting in such a situation to immediately go for the big guns (patricia trees or whatever), but often a simple hack like that gives a lot more bang for the buck.
185.
by ssp 16y ago
The word hacker never meant "good programmer", it meant "good programmer from the culture around MIT". I doubt Brian Kernighan or Dennis Ritchie or Doug McIlroy ever refer to themselves or their peers as "hackers". But even the MIT meaning
186.
by ssp 16y ago
Maybe the problem is simply that no one knows what "hacker values" actually are,.
187.
The Intel 80376 -- a Legacy-Free i386 (with a Twist)(pagetable.com)
9 points by ssp 16y ago|0 comments
188.
by ssp 16y ago
I bet you could sell music sampled at some ridiculous rate to audiophiles. How about "Copelab Music Company"?
189.
by ssp 16y ago
A lot of the classic Unix security advice is pretty outdated. For example the idea that someone getting "root" access is worse than someone gaining "ssp" access. Everything interesting is already readable and writable by ssp. The only new
190.
by ssp 16y ago
Tom Duff himself writes about it here: http://doc.cat-v.org/bell_labs/duffs_device In particular, The device is legal dpANS C. I cannot quote chapter and verse, but Larry Rosler, who was chairman of the language subcommittee (I
191.
by ssp 16y ago
Summary of that article: Metcalfe's law assumes that when you add a new person to a network, he will communicate equally with everybody, so that he contributes 1 unit of value per existing node, leading to O(n^2) growth. But that is wrong.
192.
by ssp 16y ago
It's not a bad idea. In fact, why not take it a step further and make a stand-alone client that only executes the byte code? It would be different from Java for two reasons: (a) The bytecode format could be much simpler if it weren't tied
193.
Rob Pike: Notes on Programming in C(lysator.liu.se)
122 points by ssp 16y ago|111 comments
194.
by ssp 16y ago
Fixing bugs versus writing new code, well, one might quibble with that in some scenarios. Spolsky actually makes that point himself in another article: http://www.joelonsoftware.com/articles/fog0000000014.html
195.
by ssp 16y ago
Instead of picking the fastest lane, it would in principle be faster to distribute all your items across all the lanes. That way, you minimize the time from you are first in line until you are checked out. Consider the problem of optimizing
196.
Intel and Achronix Get Engaged(codingrelic.geekhold.com)
1 points by ssp 16y ago|0 comments
197.
by ssp 16y ago
I'm not alone on this. No, you're not. I remember looking at stackoverflow once and there was some sort of New here? Read this wall of text to get started! to which I responded Awesome! Maybe I'll read that when I have looked at the la
198.
by ssp 16y ago
A bit of a tangent, but would something like source control (git, hg) be useful to lawyers? If they are cutting and pasting from older documents all the time, it seems like it would.
199.
by ssp 16y ago
But this is a company being sold. It's an exit.
200.
by ssp 16y ago
I'm not sure I get it. From the perspective of the investors, the 300 million sale seems better. Are they not trying to maximize the return on their money?
201.
by ssp 16y ago
Putting the extra silicon on the chip is effectively free. If you need that silicon to actually work, then it's not free. Floor-sweeping is necessary because the more stuff you put on a chip, the more likely it is to have defects. That re
202.
by ssp 16y ago
(Lies, damn lies and benchmarks, but A8 gets ~2000 MIPS, A9 ~2500 MIPS and singlecore 1st gen Atom gets ~3300 MIPS) Measured how, and at what frequencies? Also ARMs are really starved for bandwidth. Has that improved with the Cortex A9?
203.
by ssp 16y ago
The technical advantages of ARM aren't _that_ great. True - see also this: http://codingrelic.geekhold.com/2010/08/x86-vs-arm-mobile-cp... However, if x86 has neither a process or a compatibility advantage, then even a tiny technical di
204.
by ssp 16y ago
Indeed - they are not dying anytime soon. See also this: http://codingrelic.geekhold.com/2010/08/x86-vs-arm-mobile-cp... for why ARM's technical advantages may be overblown.
205.
by ssp 16y ago
The tagline from Innovator's Dilemma is that well-managed companies can get into trouble when they are being disrupted. The reason is that it's normally good business to get rid of low-margin products and focus your resources on the one
206.
by ssp 16y ago
For non-hygienic macros, it's essentially the variable capture problem. For hygienic macros, I don't know of a good argument that they are inherently more difficult to understand separately from their invocation than a function. (I'm not pe
207.
by ssp 16y ago
The argument is that macros have non-local effects; they interact with the code in which they are applied. This means that the macro definition and the code surrounding the macro invocation can't necessarily be understood in isolation. This
208.
by ssp 16y ago
The reason I mentioned a GPL project specifically is that that would be competing directly with the BSD project for the hearts and minds of the open source community. For some people I think that would be harder to swallow than say Microsof
209.
by ssp 16y ago
How carefully have you thought about that? Are you fine with someone integrating your code into a GPL project that competes with you, and potentially out -competes your project?
210.
by ssp 16y ago
This is true. One of the distinguishing characteristics of geeks is that they like abstraction; most people don't.

More ›