Thankfully, HPAQ will squander this opportunity just like they squandered every other opportunity in recent memory with the exception of illegal printer ink tying.
Apple's logical falacy in this case is called "bifurcation". Deconstruct the argument as: 1) Technological measures to combat theft are good 2) Effective technical measures can only be implemented using a locked down ROM. The bifurcation is the unproved claim that locking down a ROM is the only effective technological measure, when in fact there may be other possibilities.
Moral of the story: be skeptical of any claim Apple makes, particularly when they earnest explain why a user's rights over their own purchased product should be abridged to the benefit of Apple.
Don't shoot the messenger. We always appreciate it when Microsoft submits a bug report like this. Next step is to fix Firefox to use significantly less CPU than Microsoft's product. It's hard to see anything wrong with that.
In many ways, Google is run by a bunch of luddites. Google also hates remote working and thinks that each project has to be run by a single team in a single office. Obviously, Larry never noticed that the Linux kernel is developed in 10,000 different offices simultaneously and is bigger than the sum total of everything Google ever did.
I'm just amazed by the fervor of the Marissa apologists. Marissa did an obviously stupid thing which is sure to bite Yahoo on the ass. Everybody knows what the problem is at Yahoo with lazy, tenured senior engineers. Cancelling remote was just stupid, the real problem is letting the slackers get away with it. Now they will just slack in the office and Marissa will be perfectly happy. Meanwhile, anybody with talent will be thinking twice about hanging around at Yahoo waiting for the next stupid edict. She got booted from the executive suite at Google for doing stupid things too. If she plays her cards right she will be out of Yahoo before the shit hits the fan and on to her next victim smelling like a rose.
Actually, Microsoft only got off (nearly) scott-free with the feds. They had to pay out hundreds of millions to states and billions to private parties, who all relied on the federal judgement.
Yahoo can't stage a comeback with Marissa Mayer at the helm. Case in point: cancelling all remote working while the rest of the word is learning how to adapt to and benefit from it. Expect more such idiocy with this overrated bimbo in charge.
"The open source driver for NVidia". Nouveau. NVidia does not need to "have" this driver for it to be open source. The contrary if anything. I can't for the life of me imagine a reason for your troll.
If you want cash, you have to give me a discount greater than my card gives me. I am not here to make your store profitable.
What an ass. Did you ever think for a moment that cutting out the retail bank as middleman could make life better for you, the merchant and society in general?
Templates and lambdas are two completely separate things. Most of my lambda usage is without templates. And template usage is largely unreadable because of crappy STL design (eg., disallows constant expressions) rather than the template language itself.
Structure returns used to suck in GCC code generator wise, now they are fine. The same will be true of lambdas. They offer optimization opportunities if anything.
I presume that you think it would be a good idea to tax all uses of cash as well?
If you buy 1 BTC for $100 and sell it for $120 then yes, you should be taxed on the $20 profit you made. As is done currently with speculating on stock and currency exchange. What's the big news?
Whoosh. That is not what the proposal is about. The Canadian proposal is that if you buy $100 worth of bitcoins and sell them for the exact same price, you will have to pay a transaction tax, unlike the case with normal cash.
Lambdas are indeed "tricks" that IMO are syntax candy (in C++), can be a bitch to debug, and add little value
You know about this trick, but you do not know this trick. The C++ incarnation is mildly funky but flexible and tidly solves a host of messy structural issues. And it's easy to read if you actually think that way, which IMHO, any practicing programmer should be able to do.
old people have higher Health Care and don't like pulling 80+ weeks.
Or even 40+ weeks. And don't need to because they tend to do their work more efficiently as opposed to galloping odf enthusiastically in all directions. Ultimately producing stronger, more maintainable code. By way of substantiation, note that the typical European worker at ~37 hours/week is typically as productive as an American or Asian worker supposedly putting in way more hours. The equalizer is, Europeans tend to plan better and waste less time.
BTW, note that being an older programmer does not obviate the possibility of having a young lover. Far from it. In work or love it's about keeping your stamina up: take care of your eyes and your body. Treasure your enthusiasm for life. Keep your mind active and never stop learning. The rest just falls into place.
Slashdot Mirror
Thankfully, HPAQ will squander this opportunity just like they squandered every other opportunity in recent memory with the exception of illegal printer ink tying.
Apple's logical falacy in this case is called "bifurcation". Deconstruct the argument as: 1) Technological measures to combat theft are good 2) Effective technical measures can only be implemented using a locked down ROM. The bifurcation is the unproved claim that locking down a ROM is the only effective technological measure, when in fact there may be other possibilities.
Moral of the story: be skeptical of any claim Apple makes, particularly when they earnest explain why a user's rights over their own purchased product should be abridged to the benefit of Apple.
Don't shoot the messenger. We always appreciate it when Microsoft submits a bug report like this. Next step is to fix Firefox to use significantly less CPU than Microsoft's product. It's hard to see anything wrong with that.
In many ways, Google is run by a bunch of luddites. Google also hates remote working and thinks that each project has to be run by a single team in a single office. Obviously, Larry never noticed that the Linux kernel is developed in 10,000 different offices simultaneously and is bigger than the sum total of everything Google ever did.
Backward compatibility is not a hard problem, Vint Cerf just isn't very good at it as evidenced by the IPv6 fiasco.
If she were a man, the technical term would be "dickhead".
I'm just amazed by the fervor of the Marissa apologists. Marissa did an obviously stupid thing which is sure to bite Yahoo on the ass. Everybody knows what the problem is at Yahoo with lazy, tenured senior engineers. Cancelling remote was just stupid, the real problem is letting the slackers get away with it. Now they will just slack in the office and Marissa will be perfectly happy. Meanwhile, anybody with talent will be thinking twice about hanging around at Yahoo waiting for the next stupid edict. She got booted from the executive suite at Google for doing stupid things too. If she plays her cards right she will be out of Yahoo before the shit hits the fan and on to her next victim smelling like a rose.
No, because she's a bimbo. Do a little research, the facts aren't hard to find.
Actually, Microsoft only got off (nearly) scott-free with the feds. They had to pay out hundreds of millions to states and billions to private parties, who all relied on the federal judgement.
Yahoo can't stage a comeback with Marissa Mayer at the helm. Case in point: cancelling all remote working while the rest of the word is learning how to adapt to and benefit from it. Expect more such idiocy with this overrated bimbo in charge.
IBM got righteously busted for tying in the 70's. I can't think of any reason why Microsoft should escape similar proceedings today.
The "don't be evil" has left the building. Cue evil Googlers to mod this into oblivion.
Everyonce... excellent new word, we should use it.
Not just any fish. It absolutely must be herring.
BSODs? That's Windows, right?
1) unfair comparison
2) old news
3) 100% nvidia's fault
4) Fuck you NVidia!
5) Profit.
Apparently, some knuckle dragger with mod points does not know their history.
1) unfair comparison
2) old news
3) 100% nvidia's fault
4) Fuck you NVidia!
5) Profit.
"The open source driver for NVidia". Nouveau. NVidia does not need to "have" this driver for it to be open source. The contrary if anything. I can't for the life of me imagine a reason for your troll.
If you want cash, you have to give me a discount greater than my card gives me. I am not here to make your store profitable.
What an ass. Did you ever think for a moment that cutting out the retail bank as middleman could make life better for you, the merchant and society in general?
Templates and lambdas are two completely separate things. Most of my lambda usage is without templates. And template usage is largely unreadable because of crappy STL design (eg., disallows constant expressions) rather than the template language itself.
Structure returns used to suck in GCC code generator wise, now they are fine. The same will be true of lambdas. They offer optimization opportunities if anything.
I presume that you think it would be a good idea to tax all uses of cash as well?
If you buy 1 BTC for $100 and sell it for $120 then yes, you should be taxed on the $20 profit you made. As is done currently with speculating on stock and currency exchange. What's the big news?
Whoosh. That is not what the proposal is about. The Canadian proposal is that if you buy $100 worth of bitcoins and sell them for the exact same price, you will have to pay a transaction tax, unlike the case with normal cash.
Lambdas are indeed "tricks" that IMO are syntax candy (in C++), can be a bitch to debug, and add little value
You know about this trick, but you do not know this trick. The C++ incarnation is mildly funky but flexible and tidly solves a host of messy structural issues. And it's easy to read if you actually think that way, which IMHO, any practicing programmer should be able to do.
Give an example of a "trick".
C++11 lambdas.
old people have higher Health Care and don't like pulling 80+ weeks.
Or even 40+ weeks. And don't need to because they tend to do their work more efficiently as opposed to galloping odf enthusiastically in all directions. Ultimately producing stronger, more maintainable code. By way of substantiation, note that the typical European worker at ~37 hours/week is typically as productive as an American or Asian worker supposedly putting in way more hours. The equalizer is, Europeans tend to plan better and waste less time.
BTW, note that being an older programmer does not obviate the possibility of having a young lover. Far from it. In work or love it's about keeping your stamina up: take care of your eyes and your body. Treasure your enthusiasm for life. Keep your mind active and never stop learning. The rest just falls into place.