TomV1971
It was really fun to read the forums and see how, day by day, they managed to get closer. Since it wasn’t really crucial IP to begin with, we were rooting for the little guys to see how close they would get, secure in the knowledge that our algorithm was solid. :-)
The final exploit that granted them access was due to a supplier who replaced an earlier validated random generator with something not quite as random, which enabled replay attacks.
Even though the system encodes silences noise free (so improve compression), it deliberately inserts noise because otherwise people think the line is dead.
Intel graciously paid for trees to brighten up the street and has a nice street sign saying so. (It doesn’t say why they did.)
This one is not directly related to silicon production, but the QA that came after.
There is little upside in screwing over millions of existing customers.
So that part is not something that’s specific to Apple.
For example: a soft delete may be just a stronger version of public vs private settings. The whole software infrastructure still assumes a link exists and doesn’t need to cover cases where it really isn’t there. I could see how that makes maintaining indexes etc easier.
Flipping a flag and then filtering out results down the line based on the delete setting is probably much easier than actively removing them from an index.
And if deleting is rare (it probably is), then the performance and resource impact should be minimal.
That’s something that’s not only useful for pure graphics.
So it is (or was?) not a straight substitute for CUDA.
Looks like I’ll be forced into human to human interaction.
Yeah...
Nothing fancy, but a surprisingly big room at a prime location.
I don’t care at all if a photograph from a photographer whom I’ve never heard of is a composite, but today I learned about the location of the moon North Pole, moon libration, and moon roll, and that’s really cool.
Microcode can be loaded by the BIOS.
I’ve written RTL that speculatively fetches data from memory in order to avoid bubbles in a pipeline. Not a CPU, but the concept is exactly the same.
If somebody had assigned me to a CPU project without guidance from a security architect and ask me to speculate reads, I’d probably have done the same as Intel.
The chance that the same guy did both CPUs is small. It’s just that it’s not an unreasonable way of doing thing if you’re not familiar with these kind of attack.
And I know from experience that what looks ridiculous and petty for an outsider is suddenly much less so when it impacts you personally.
And it’s great progress if people at least realize that they are, or would be in the same situation as that Berkeley neighborhood.
Until it happens to impact me personally.
I’m not proud of it, but I haven’t seen anyone who doesn’t react the same way. Nobody like to give up good things that they already have (especially if they paid $1M+ for it.)
It happened to me, and just like it happens to virtually everybody in the same situation.
But now think if you happen to live on just that one plot of land in the street, right next to the development, that will now be in the shadow of the new building.
Would you be happy about it?
I wouldn’t, and neither would you.
The $700 1080 Ti has almost the same performance as the Titan Xp, so why not compare those?
It changes conclusions considerably...
Two times, I accepted the counteroffer and stayed (for a while.) It didn’t have any adverse impact. I’m still at the company of the second counteroffer.
My experience is that big companies are typically quite rational about the whole thing. No hard feelings or anything, just business.
OoO is much more expensive to implement than simply scheduling a different warp to hide latency.