Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
nickpsecurity
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
4511 ms
·
10861.
▲
by
nickpsecurity
12y ago
Thanks for that awesome article! Interestingly, he used the same example I've been using in INFOSEC discussions online: Burroughs B5000. It was simply brilliant and still better at the core than anything I use today. Let me explain. Th
10862.
▲
by
nickpsecurity
12y ago
Software is their main skill. Yet, Google and Facebook have both been doing custom hardware for datacenters for years now. They're also funding academic R&D on chip design and such. Such companies needs also created an ecosystem of
10863.
▲
by
nickpsecurity
12y ago
Fighting the laws of physics is a great comparison. Every chip designer trying to create the illusion of a sequential (or multicore) machine with a specific memory model fights the laws of physics. So do people building bridges, designing p
10864.
▲
by
nickpsecurity
12y ago
In startup mode, I expect companies to do whatever works. Google's initial decisions were correct. Later, they dedicated expensive teams to inventing brand new solutions for about every aspect of their operation. That's when my cr
10865.
▲
by
nickpsecurity
12y ago
True. I always expect this. Yet, Google doesn't fit that profile because they weren't just buying something that works: they were investing countless sums into geniuses and their projects trying to invent new things. It's at
10866.
▲
by
nickpsecurity
12y ago
I've edited my comment to give him that credit. I understand the CAP theorem applies to many things. The reason I tied NoSQL in is that it's often cited as the reason people traded away strong consistency. Yet, there were strongly
10867.
▲
by
nickpsecurity
12y ago
Yeah we do. My only guess is it's two things: (a) our industry is horrendous at communicating previous generation's wisdom in a usable way; (b) a social phenomenon. Quick example of the first are industry pro's locking up the
10868.
▲
by
nickpsecurity
12y ago
Good thinking, you two! The link shows that the black magic (spindle control, etc) is in a dedicated chip controlled by another chip. The "black box" controlling the "black box." I thought they'd be on the same chip
10869.
▲
by
nickpsecurity
12y ago
One thing that bothers me about the article is that it shows a recurring problem: IT not knowing what it knows. The NoSQL movement didn't notice that NonStop Architecture scaled linearly to thousands of cores with strong-consistency, f
10870.
▲
by
nickpsecurity
12y ago
Yeah, that's what he said. So, that makes two of you saying this is industry standard for cost-cutting and increasing yield. I'd probably do the same if I made chips. We do it in security engineering for high assurance stuff for s
10871.
▲
by
nickpsecurity
12y ago
The firmware on the device is a black box that controls a more complex black box in an undocumented way and where errors can break it. You don't JUST swap the firmware out. Even so, he may have meant it in the context of the onboard
10872.
▲
by
nickpsecurity
12y ago
A hardware engineer told me in discussions on chip subversion that BS like this is common in SOC's, too. He said they're so expensive to develop that vendors often include the functionality of all their chips in one design. Then,
10873.
▲
by
nickpsecurity
12y ago
The article is looking at it all wrong. To solve a problem, start by looking at those that already solved it. Then, see if you can apply that. Mainframes have long had ridiculously high utilization and throughput. Secret is their I/O a