Intel microcode license updated to permit redistribution
1–10 of 41 posts
Re: Intel microcode license updated to permit redistribution
#2I had a quick Google and couldn't find any published benchmarks yet. Does anyone know of one so far?
Re: Intel microcode license updated to permit redistribution
#3Can anyone with background in law in some of EU member states share their take on enforceability of the DeWitt clause[0]?
I know it popped up quite a few times here, but very few commented on it in the context of EU.
Re: Intel microcode license updated to permit redistribution
#4I had a quick Google and couldn't find any published benchmarks yet. Does anyone know of one so far?
According to a German news article [0], Intel published benchmarks themselves [1].
[0]: https://heise.de/-4144515
[1]: https://www.intel.com/content/www/us/en/architecture-and-tec...
Re: Intel microcode license updated to permit redistribution
#5A lawyer friend of mine one told me that his job was basically to try to see what he could sneak past the opposition's (his sentiment, not mine) lawyers in their contracts. He explained contracts are like a running game of tag for lawyers. "If they don't read it, fuck 'em".
He also said that all contracts are mutable. Just strike in red whatever you want, sign it, and send it back. If they don't object (for whatever reason, including not expecting a non-lawyer to do such a thing and never reading your reply), you've won this round of tag.
Then mentioning that 9/10 contract disputes get settled out of court meant the law didn't really matter, it's just what you can convince others about.
Re: Intel microcode license updated to permit redistribution
#6A lawyer friend of mine one told me that his job was basically to try to see what he could sneak past the opposition's (his sentiment, not mine) lawyers in their contracts. He explained contracts are like a running game of tag for lawyers. "If they don't read it, fuck 'em". He also said that all contracts are mutable. Just strike in red whatever you want, sign it, and send it back. If they don't object (for whatever…
Of course, you want some ground rules but you also don't want to be such an ass of a company that you loose customers/collaborators over petty things.
In my company we have a legal department sometimes making contracts that us researchers are ashamed of (we get to use all your samples, any IP is ours when generated during the duration of the contract by the people involved, etc), and then there is our wish to keep collaborating with the other party and keep all of us working happily together now and in the future. These things collide, contracts get ignored.
Re: Intel microcode license updated to permit redistribution
#7A lawyer friend of mine one told me that his job was basically to try to see what he could sneak past the opposition's (his sentiment, not mine) lawyers in their contracts. He explained contracts are like a running game of tag for lawyers. "If they don't read it, fuck 'em". He also said that all contracts are mutable. Just strike in red whatever you want, sign it, and send it back. If they don't object (for whatever…
This reminded of a counter-exemplary story, A Tiny, $25 Million Mistake:
https://www.npr.org/sections/money/2014/09/16/348975479/a-ti...
> Levine had always thought a contract was binding. Now he saw two big companies laugh off his little mistake. The other side agreed to revise the contract to pay the extra $25 million.
> The whole experience surprised Levine. "I thought it was a game," he says. "You sort of score points. And they had scored this point through my fault, and they were going to get something for it."
> Business may be a game, Levine realized, but it's not a one-time game. It's more like an infinite game. It's a game in which people have to live with each other, work with each other again, and perhaps, write another big contract.
Re: Intel microcode license updated to permit redistribution
#8I had a quick Google and couldn't find any published benchmarks yet. Does anyone know of one so far?
According to a German news article [0], Intel published benchmarks themselves [1]. [0]: https://heise.de/-4144515 [1]: https://www.intel.com/content/www/us/en/architecture-and-tec...
Can anyone explain these graphs a bit. I.e the first one shows no impact what-so-ever, but are the benchmark conditions real-life-y enough?
Re: Intel microcode license updated to permit redistribution
#9A lawyer friend of mine one told me that his job was basically to try to see what he could sneak past the opposition's (his sentiment, not mine) lawyers in their contracts. He explained contracts are like a running game of tag for lawyers. "If they don't read it, fuck 'em". He also said that all contracts are mutable. Just strike in red whatever you want, sign it, and send it back. If they don't object (for whatever…
Of course, you want some ground rules but you also don't want to be such an ass of a company that you loose customers/collaborators over petty things. In my company we have a legal department sometimes making contracts that us researchers are ashamed of (we get to use all your samples, any IP is ours when generated during the duration of the contract by the people involved, etc), and then there is our wish to keep co…
That's a rules of the game. Every department want to grow its importance in the company, to get more power and resources. Well, sometimes this end up in failing company, but they have no choice - if dep X decide to stop it, other won't - and the company fail anyway, but with dep Y on the top instead, all the difference is who will have more power during some time - then the choice is clear and no department will stop their play.
Re: Intel microcode license updated to permit redistribution
#10A lawyer friend of mine one told me that his job was basically to try to see what he could sneak past the opposition's (his sentiment, not mine) lawyers in their contracts. He explained contracts are like a running game of tag for lawyers. "If they don't read it, fuck 'em". He also said that all contracts are mutable. Just strike in red whatever you want, sign it, and send it back. If they don't object (for whatever…
There was a Russian chap that did this exactly this, modified his credit card contract and the bank happily signed the modified contract without reading it: https://www.nasdaq.com/article/updated-russian-man-turns-tab...