Milennials don't support Socialism. They support being given everything they want without having to work for it and expecting someone else to pay for it.
If you ask a Milennial "How will we pay for giving everyone free homes, cars, food, education, power, water, heat, lights, gasoline/electricity charging, massages or whatever else they decide they want today" the answer will either be "increase taxes on "the rich" (let someone else pay for it)" or "I don't know/that's a good question.".
This. Definitely this.
If you ask them what they want, it's to be given free stuff. (Free for them - obviously someone has to work to supply it, just not them).
They have associated socialism with handouts. Free healthcare. Free education. Free housing. Free entertainment... the list goes on and on.
The first is that malicious programs could open up, grab screen buffers, and get access to stuff that had been on the screen to use for their nefarious purposes.
This is bad, and unless we get decent support to isolate the frame buffers (and other graphic memory) between apps at either the driver or hardware layer, it's not going away anytime soon. Dont want this? Power cycle (all the way off - not just hiberante) between application launches would do it.
The second is sloppy programming on the part of non-malicious applications. That's what is being talked about in the application. Diablo apparently asked for a frame buffer, and then presented it, as is, to the user without putting what it wanted in place, trusting for it to be in a particular state. Which it wasn't.
You want a black screen to show to the user, then write zeros into your buffer before you show it to the user. Decent compilers/languages will tell you if you've tried to read from unitialized variables, and you should never trust that anything you've asked for dynamically is in a safe state, unless you've explicitly requested that it's cleared before being handed to you. Why should a resource from the graphics card be treated any differently?
NVidia is right about one thing here - most of the time, nearly all of the time, the thing you do with that buffer you're given is to write your stuff into it, completely overwriting it, and it would slow things down if they had to guarantee that it was cleared before handing it out to you. If your program doesn't care enough to do so itself, that's not really their fault.
It would be nice if, on program exit, all GPU resources used by that app were flushed, but again, that would involve the OS needing to be told of all the GPU resource allocations and deallocations so it could clean up properly, and that too would probably slow things down. Not a lot, but enough to be annoying when your game stutters.
Only having a 300 baud acoustic modem and a Tandy Color computer 2, I still wanted to run my own home written BBS. Wound up running the phone line through the cassette relay control on the Coco2.
All night long, Click, see if someone hit return at least one, click - hang up. Click - pick up, watch for return. Click - hang up.
Must have driven Thunder Bay Tel completely nuts trying to find out why someone would keep picking up and hanging up every 5 seconds or so for weeks on end. This was back in 1984. The BBS lasted about 2 years and did have a fair number of people connect in to it.
Wouldn't it be easier to mount, say, 4 model rockets on wires under it? Electronic ignition and off you go. If you want them to make holes in things, well, put a nail sticking out of the nose. Pick your engine size based on your required damage.
Slashdot Mirror
It doesn't blow up because it's venting pressure before an earth shattering kaboom. If yours isn't hissing, beware...
I'm thinking more, Utopia, Aeon Flux (the cartoon, not the live action movie) style.
I've noticed that human drivers quite often cause accidents. Can we get the steering wheel and gas pedal removed while we're at it?
Better advice or not, the medical searches you perform will still be added to the profile of information kept about you by Google.
And then promptly sold to your insurance company.
But it is there on Bing Translate.
In memory of Schrodinger's Cat, who selflessly gave his life today, in order that the world not be consumed by a man made black hole.
Even up here in Canada, where our health care is paid for (msotly), doctors can and do get paid based on the number of patients they see.
Milennials don't support Socialism. They support being given everything they want without having to work for it and expecting someone else to pay for it.
If you ask a Milennial "How will we pay for giving everyone free homes, cars, food, education, power, water, heat, lights, gasoline/electricity charging, massages or whatever else they decide they want today" the answer will either be "increase taxes on "the rich" (let someone else pay for it)" or "I don't know/that's a good question.".
This. Definitely this.
If you ask them what they want, it's to be given free stuff. (Free for them - obviously someone has to work to supply it, just not them).
They have associated socialism with handouts. Free healthcare. Free education. Free housing. Free entertainment... the list goes on and on.
Sigh.
Who knew that EVE had a big brother...
Logan's Run was actually a 2 hour training movie for the insurance industry.
Or hunt them down and kill them.
Vader certainly didn't have a problem with that when talking to the emperor...
"unlock the phone"
"no"
"sudo unlock the phone"
"Dammit. OK..."
There are two real issues here.
The first is that malicious programs could open up, grab screen buffers, and get access to stuff that had been on the screen to use for their nefarious purposes.
This is bad, and unless we get decent support to isolate the frame buffers (and other graphic memory) between apps at either the driver or hardware layer, it's not going away anytime soon. Dont want this? Power cycle (all the way off - not just hiberante) between application launches would do it.
The second is sloppy programming on the part of non-malicious applications. That's what is being talked about in the application. Diablo apparently asked for a frame buffer, and then presented it, as is, to the user without putting what it wanted in place, trusting for it to be in a particular state. Which it wasn't.
You want a black screen to show to the user, then write zeros into your buffer before you show it to the user. Decent compilers/languages will tell you if you've tried to read from unitialized variables, and you should never trust that anything you've asked for dynamically is in a safe state, unless you've explicitly requested that it's cleared before being handed to you. Why should a resource from the graphics card be treated any differently?
NVidia is right about one thing here - most of the time, nearly all of the time, the thing you do with that buffer you're given is to write your stuff into it, completely overwriting it, and it would slow things down if they had to guarantee that it was cleared before handing it out to you. If your program doesn't care enough to do so itself, that's not really their fault.
It would be nice if, on program exit, all GPU resources used by that app were flushed, but again, that would involve the OS needing to be told of all the GPU resource allocations and deallocations so it could clean up properly, and that too would probably slow things down. Not a lot, but enough to be annoying when your game stutters.
A Matter of Minutes... Twilight zone wins every time.
https://en.wikipedia.org/wiki/...
And we know that fusion is possible too.
Look up. Look way up... See the glowing ball of fire in the sky?
That sounds like an awesome plan. I hear Omni Consumer Products is ready to go when we are...
This has actually been covered in a book as well - (or rather a series) - Go read There will be Dragons. http://www.amazon.com/There-Wi...
And I thought the Pipboy edition of Fallout 4 was bad. (and yes, I ordered that)
Now you can get the vault dweller edition? Does it come with special DLC with it as well?
Suddenly sounds a lot more feasible.
Only having a 300 baud acoustic modem and a Tandy Color computer 2, I still wanted to run my own home written BBS. Wound up running the phone line through the cassette relay control on the Coco2.
All night long, Click, see if someone hit return at least one, click - hang up. Click - pick up, watch for return. Click - hang up.
Must have driven Thunder Bay Tel completely nuts trying to find out why someone would keep picking up and hanging up every 5 seconds or so for weeks on end. This was back in 1984. The BBS lasted about 2 years and did have a fair number of people connect in to it.
gets one step closer.
While it's not holograms, head tracking and headsets I guess for now are the next best thing.
While it's not E, O seems close enough...
https://www.cirquedusoleil.com...
Just like the uniforms required by every other evil overlord...
Wouldn't it be easier to mount, say, 4 model rockets on wires under it? Electronic ignition and off you go. If you want them to make holes in things, well, put a nail sticking out of the nose. Pick your engine size based on your required damage.
Woosh. The first flying Gyrojet...