I don't think they're trying to stop a 12 y/o who is determined to see porn. Rather, they're trying to stop someone from clicking on a link that brings them to adult content without a warning. It seems reasonable to me,
Wrong. They're trying to get some more votes from one of their demographics.
Nothing he can legislate will reduce the amount of porn children have access to.
I installed VS2015 on a spare machine for a laugh - I actually managed to get them to fix an ancient VS bug fixed by nagging them enough. The fix was in VS2015 and I wanted to see it with my own eyes.
It crashed and burned about once a minute for the entire time I tried it, no chance to save any work. So much for a new 'improved' version.
I only installed VS2013 a few months ago after it reached SP4. I'm not expecting VS2015 to be usable any time soon (I _would_ like to have my bug fixed though because it happens constantly...OTOH it's been bothering me since VC++ 6.0 so I'm almost used to it by now)
You can actually see some of the Windows source code if you want. You must sign an NDA and you have to justify your access (at least you did while I was still in the MVP program
The Pirate Bay allows you to skip the red tape.
So you can see the source, in part, if you want to.
"In part".
The patches are the biggest worry for me. Microsoft could backdoor most of the computers in the world overnight if it wanted to. They can even target specific IP addresses if they want to because the own the patch distribution network. This is why I feel it's important to disassemble/inspect the patches before installing. There's no source code available for patches so keeping my Windows PC in tip-top condition is a big drain on my resources. Still... it's worth the effort for the peace of mind it gives me later.
They don't understand that Intel/AMD CPUs could or will have backdoors. If not now, then very soon in the future.
I usually decap my CPUs and inspect them before installing them. I haven't seen anything suspicious so far.
The real problem is Windows. Having to disassemble/inspect the OS before installing wasn't too bad, it's the constant stream of patches that gets me down.
Slashdot Mirror
13-year-olds are quite capable of making their own porn these days.
Using the cameras and networking hardware given to them by their own parents.
I don't think they're trying to stop a 12 y/o who is determined to see porn. Rather, they're trying to stop someone from clicking on a link that brings them to adult content without a warning. It seems reasonable to me,
Wrong. They're trying to get some more votes from one of their demographics.
Nothing he can legislate will reduce the amount of porn children have access to.
Is he going to shut them down in just the UK or in the whole world?
Nah, people are like dogs in this respect. They need a vertical surface.
Nikola Tesla is turning in his grave.
We're supposed to take ballistics advice from somebody who can't spell "lose"?
What if my newborn baby is out on the porch? Do I really want the neighbors randomly shooting birdshot up in the sky?
Birdshot landing in my picnic? Don't want that, either.
In fact I don't want birdshot landing anywhere near me. Something doesn't have to be deadly for me to not want the neighbors firing it at me.
It's almost as if he didn't make much effort to find that.
It's OK. Once you move out, you're safe.
How do you know it wasn't buckshot?
Sure, it was a shotgun *this* time. What about next time?
I like your condition: "sufficiently elevated"
What if it's not?
Depends on what you shoot at it with.
Shooting at the sky is bad. Falling bullets can kill.
So much for a new 'improved' version
I don't know if you were being negative or playful when you wrote this but with all major overhauls there's going to be bugs.
Sure, but... I expect an IDE crash to be more difficult than "compile my code then double-click a warning message".
(Yes, I did it three times with the same result)
"We don't do pardons", followed by an appeal to patriotism (ie. if you don't agree with our decisions then you're a pinko commie)
Film at 11.
I installed VS2015 on a spare machine for a laugh - I actually managed to get them to fix an ancient VS bug fixed by nagging them enough. The fix was in VS2015 and I wanted to see it with my own eyes.
It crashed and burned about once a minute for the entire time I tried it, no chance to save any work. So much for a new 'improved' version.
I only installed VS2013 a few months ago after it reached SP4. I'm not expecting VS2015 to be usable any time soon (I _would_ like to have my bug fixed though because it happens constantly...OTOH it's been bothering me since VC++ 6.0 so I'm almost used to it by now)
Drawn and quartered. Look up the definition. It is a long and drawn out process for execution.
It's almost as if you don't actually know anything that particular punishment.
Hint: There's a third element to it.
Wait for at least SP1. Let others be the beta testers.
I for one can't wait to play video games on my new Quantum computer.
Bring it on, the graphics will be awesome!
The article says it's nothing to do with the OS, but any excuse, eh?
You can open the safe with just a piece of metal?
Yeah, that'll work.
You can actually see some of the Windows source code if you want. You must sign an NDA and you have to justify your access (at least you did while I was still in the MVP program
The Pirate Bay allows you to skip the red tape.
So you can see the source, in part, if you want to.
"In part".
The patches are the biggest worry for me. Microsoft could backdoor most of the computers in the world overnight if it wanted to. They can even target specific IP addresses if they want to because the own the patch distribution network. This is why I feel it's important to disassemble/inspect the patches before installing. There's no source code available for patches so keeping my Windows PC in tip-top condition is a big drain on my resources. Still ... it's worth the effort for the peace of mind it gives me later.
They don't understand that Intel/AMD CPUs could or will have backdoors. If not now, then very soon in the future.
I usually decap my CPUs and inspect them before installing them. I haven't seen anything suspicious so far.
The real problem is Windows. Having to disassemble/inspect the OS before installing wasn't too bad, it's the constant stream of patches that gets me down.
I want to know how 'manual update' will save you from this?
Unless you just never install updates, ever, or something like that. Which is probably worse.
Yep, those civilians were totally to blame for Pearl Harbor. They deserved to die.
Good job, America.
Whoosh!