Alas, it's a Metro-version. Not everyone likes the new Metro-version and wants the classic version instead, including the person I set up with the classic games.
You can find all the classic games on the Internet as a simple installer, though. Solitaire doesn't exist in Windows 8 either and I recently had to find and install it on a Win8 - laptop for an older person. I don't remember where I downloaded it, but the link in http://techtoy.co.uk/microsoft... seems to be more-or-less the same. (I have not installed that version so I haven't checked it for viruses, I'm sure you can do that yourself.)
That either you're exaggerating or you do something very, very wrong with your drives? I use low-end, cheapest of the cheapest consumer-SSDs and for example this 64GB drive I have has logged 9607 hours of power-on time. Has it broken yet? No. Are there any issues with it? Nope, not a single one. I do have to ask you: what exactly do you do with those drives of yours if you manage to break them so fast?
More like Google doesn't appear to support RTMP like everyone else.
That's not a reason for them not to add support for YouTube live-streaming in OBS, but then working with Elgato and XSplit on adding it. It's not like Elgato or XSplit can use RTMP with it, either.
Obviously Google is getting a kickback from Elgato and XSplit for any new customers they can attract with the YouTube-support, OBS can't give them a kickback so they're ignored.
I do have to point out that it wasn't "normal usage." The article says the laptop is designed to blow the hot air out from the bottom, but he had the laptop on a soft blanket so it couldn't do that. It would've gotten charred regardless of the OS if you're so stupid as to block the exhausts.
In that case, even a password of 'veronica' should be strong enough to last until the breach is discovered (days?), the user notified
Considering how awfully many cases there have been where it has taken the company weeks or even months to notify anyone of the breach I'm going to have to disagree on that.
The plain simple truth is that complexity of a password is barely relevant at all when compared to the threat of an outright data breach at a provider. Who cares if your password is 'veronica' (your daughters name) or `myL1ttleBr0ny%` since an attacker isn't going to bother with brute forcing anything but '123456' and 'password' because they will get tarpitted by any reputable provider before they can guess anything out of a dictionary more than 5 entries long.
Your basis for saying bassword-complexity is irrelevant is that bad people would be doing online brute-forcing? They do matter somewhat when it comes to online-cracking, but the real relevancy doesn't lie there. The passwords matter when it comes to offline brute-forcing: the more complex the password the longer it'll take to crack it even if you have the hash for it. With good passwords and well-done hashing and salting you may end up cracking them for weeks by which time whoever you obtained them from will hopefully already have made their users change their passwords.
vi comes preinstalled in most *nixes, but it is just alien to your average user, and emacs - though it behaves more like what users expect - always ends confusing them because of the key chords
I'm not even an average user and I still have no idea how to use Vi or Emacs. At least Nano does what I want.
I don't know if you're obtuse on purpose or not, but I'll explain in any case: if a person wants to be able to take advantage of adaptive vsync, but they have an NVIDIA GPU their only choices are to buy into NVIDIA's lock-in or buy a new GPU *and* a new display. Both situations are anything but ideal.
"that didn't require monitor manufacturers to employ any proprietary add-ons, and that could be adopted by any GPU maker." -- I definitely like the general idea here, but NVIDIA trying to do lock-in and squeeze even more money out of people with requiring proprietary add-ons is only going to hurt the market; it forces manufacturers to choose either camp limiting markets, or both camps increasing costs. It's bullshit. NVIDIA should work with AMD and the other manufacturers on this, not against them.
Personally, I believe that all the issues you mentioned are only functions of time; given enough time all cars will be self-driving and all such issues will be solved. I do agree that all cars won't be self-driving any time soon, but I see no technical reason for why these things would suddenly stop advancing at some arbitrary point before such things can be ironed out.
"When it’s not on the highway, one of the humans inside will take the wheel."
I agree with you. That quote right there pretty much undermines the whole "autonomously" - thing. Not to mention that it'll only be allowed to drive during a sunny day. Much, much less impressive than what the announcement here makes it look like. When the car can actually handle itself all the way from San Fransisco to New Your City (except for re-fueling), in any weather, night or day, including potholes on the road and construction work and whatnot *that's* when I'll be really impressed.
I'm not sure this is a good thing. The extra melanin apparently gives the eye extra protection from UV rays. I guess if you live in the far north its no big issue but if you live in the southern hemisphere near the equator you may want to thing twice about this. That melanin is there for a reason
Good thing Slashdotters are protected, computer displays don't produce UV-rays!
I dunno about bloat, but after reading through the article I just don't see anything I'd need. I never liked mouse gestures, for example, and I don't need more keyboard shortcuts, I mostly just use ctrl+n, ctrl+w, ctrl+r and ctrl+s in Firefox and that's it. I also have no need to insert notes into websites or have an integrated e-mail client; I have separate programs for that if/when I need it. It just doesn't seem to offer anything for me.
I, for one, have been using Firefox from the moment it was first released and I used Netscape before that. I still do not feel they've "abandoned" me in any way, the browser is still full-featured and useable and better than any other browser I've tried. And yet, I haven't had to "wrestle" with addons nor have I so much as even looked at about:config, let alone changed anything there.
As others have mentioned, the minimum requirement is OpenGL ES 3.1 - support. Others didn't say what that actually means in practice, so I'm jumping in. http://en.wikipedia.org/wiki/O... lists the following sample of hardware that supports OpenGL ES 3.1:
Adreno 400 series[25][26]
Intel HD Graphics for Intel Atom Z3700 series (Android)
Intel HD Graphics for Intel Celeron N and J series (Android)
Intel HD Graphics for Intel Pentium N and J series (Android)
Mali T6xx (midgard) series onwards[27] (Android, Linux)
Nvidia GeForce 400 series onwards (Windows)
Nvidia Tegra K1 (Android)
Nvidia Tegra X1 (Android)
PowerVR Series 6, 6XE, 6XT, 7XE and 7XT (Linux, Android)
Vivante GC2000 series onwards (optional with GC800 and GC1000)[28]
GeForce 400 is already 5 years old hardware, so as long as someone writes the drivers there's going to be a whole lot of supported hardware already out there and in active use. The list doesn't seem to mention AMD-hardware at all, but I would assume something similar as NVIDIA's 5 years.
I get your point, but I disagree on the part where you write that background operations need the disk or else they can't possibly work at all. Current smartphones are not designed to work without accessing the disk, that's true, but in theory 1GB of RAM is plenty for processes like polling a chat server or SMS to run entirely in it.
Yes, but if the phone was to lose power, like e.g. run out of battery or crash you'd lose all the data in RAM. From a general usability-standpoint losing any data that does only reside on your phone is unacceptable, most people would definitely throw a major fit about it even if it only ever actually harmed very few individuals. What if that SMS-message you just got, for example, was something important, but it got lost in bit-space? Well, you wouldn't know until it's too late!
As for keeping things in RAM: Android isn't known for being small and efficient, not even Lollipop. There are plenty of RAM-hungry background-tasks running and things like e.g. Facebook and such that are notoriously bad. Then some phones even offer things like spoken keyword-recognition that would require keeping a whole effing lot of stuff at all times in RAM just to work. I doubt 1GB RAM would be even nearly enough on most people's phones, though 2GB or more would of course help. You'd still have the issue I mentioned above, though.
As I said in the earlier comments, ARMv8 does support AES-encryption/-decryption in hardware. Most phones out there at the moment are not ARMv8, though, so they still have to resort to software-encryption/-decryption and that is the reason why Google backed off with the requirement of defaulting to encrypting devices. Up-and-coming higher-end phones are starting to ship with ARMv8 SoCs so they can perfectly feasibly enable full-disk encryption (FDE), but low-to-mid-end devices will most likely take several years before they have H/W-accelerated AES-encryption/-decryption.
So the protection is only effective if someone steals my phone while it's turned off, which is, like, 0.1% of the time?
Yes, that's exactly what it was designed for. If the system required you to enter the FDE-password whenever you open up the screen then how would background-processes, like e.g. SMS-receiving, chat and such stuff work? They'd only be able to access the disk when you have the display open and that'd obviously make the whole thing unuseable as a smartphone in the first place. No full-disk encryption scheme has been designed to withstand attacks originating from an already-running system since you need to keep the key in memory to do anything with the disk in the first place!
Slashdot Mirror
Alas, it's a Metro-version. Not everyone likes the new Metro-version and wants the classic version instead, including the person I set up with the classic games.
You can find all the classic games on the Internet as a simple installer, though. Solitaire doesn't exist in Windows 8 either and I recently had to find and install it on a Win8 - laptop for an older person. I don't remember where I downloaded it, but the link in http://techtoy.co.uk/microsoft... seems to be more-or-less the same. (I have not installed that version so I haven't checked it for viruses, I'm sure you can do that yourself.)
What does that tell you?
That either you're exaggerating or you do something very, very wrong with your drives? I use low-end, cheapest of the cheapest consumer-SSDs and for example this 64GB drive I have has logged 9607 hours of power-on time. Has it broken yet? No. Are there any issues with it? Nope, not a single one. I do have to ask you: what exactly do you do with those drives of yours if you manage to break them so fast?
More like Google doesn't appear to support RTMP like everyone else.
That's not a reason for them not to add support for YouTube live-streaming in OBS, but then working with Elgato and XSplit on adding it. It's not like Elgato or XSplit can use RTMP with it, either.
Obviously Google is getting a kickback from Elgato and XSplit for any new customers they can attract with the YouTube-support, OBS can't give them a kickback so they're ignored.
Just add a virtual nose: http://www.wired.com/2015/04/r...
and the fact that normal usage melted it
I do have to point out that it wasn't "normal usage." The article says the laptop is designed to blow the hot air out from the bottom, but he had the laptop on a soft blanket so it couldn't do that. It would've gotten charred regardless of the OS if you're so stupid as to block the exhausts.
I'm all in favour of tossing the brat out. Besides, the water is starting to smell anyways.
In that case, even a password of 'veronica' should be strong enough to last until the breach is discovered (days?), the user notified
Considering how awfully many cases there have been where it has taken the company weeks or even months to notify anyone of the breach I'm going to have to disagree on that.
The plain simple truth is that complexity of a password is barely relevant at all when compared to the threat of an outright data breach at a provider. Who cares if your password is 'veronica' (your daughters name) or `myL1ttleBr0ny%` since an attacker isn't going to bother with brute forcing anything but '123456' and 'password' because they will get tarpitted by any reputable provider before they can guess anything out of a dictionary more than 5 entries long.
Your basis for saying bassword-complexity is irrelevant is that bad people would be doing online brute-forcing? They do matter somewhat when it comes to online-cracking, but the real relevancy doesn't lie there. The passwords matter when it comes to offline brute-forcing: the more complex the password the longer it'll take to crack it even if you have the hash for it. With good passwords and well-done hashing and salting you may end up cracking them for weeks by which time whoever you obtained them from will hopefully already have made their users change their passwords.
vi comes preinstalled in most *nixes, but it is just alien to your average user, and emacs - though it behaves more like what users expect - always ends confusing them because of the key chords
I'm not even an average user and I still have no idea how to use Vi or Emacs. At least Nano does what I want.
I don't know if you're obtuse on purpose or not, but I'll explain in any case: if a person wants to be able to take advantage of adaptive vsync, but they have an NVIDIA GPU their only choices are to buy into NVIDIA's lock-in or buy a new GPU *and* a new display. Both situations are anything but ideal.
"that didn't require monitor manufacturers to employ any proprietary add-ons, and that could be adopted by any GPU maker." -- I definitely like the general idea here, but NVIDIA trying to do lock-in and squeeze even more money out of people with requiring proprietary add-ons is only going to hurt the market; it forces manufacturers to choose either camp limiting markets, or both camps increasing costs. It's bullshit. NVIDIA should work with AMD and the other manufacturers on this, not against them.
Personally, I believe that all the issues you mentioned are only functions of time; given enough time all cars will be self-driving and all such issues will be solved. I do agree that all cars won't be self-driving any time soon, but I see no technical reason for why these things would suddenly stop advancing at some arbitrary point before such things can be ironed out.
How about the first bootup bit where you have to link your fucking admin account to a fucking online account?
You don't have to. You can just create a local account.
Second was that abomination of a start screen.
That's only a bother until you install a Start-menu replacement.
"When it’s not on the highway, one of the humans inside will take the wheel."
I agree with you. That quote right there pretty much undermines the whole "autonomously" - thing. Not to mention that it'll only be allowed to drive during a sunny day. Much, much less impressive than what the announcement here makes it look like. When the car can actually handle itself all the way from San Fransisco to New Your City (except for re-fueling), in any weather, night or day, including potholes on the road and construction work and whatnot *that's* when I'll be really impressed.
I guess Linus needs a new job.
I'm not sure this is a good thing. The extra melanin apparently gives the eye extra protection from UV rays. I guess if you live in the far north its no big issue but if you live in the southern hemisphere near the equator you may want to thing twice about this. That melanin is there for a reason
Good thing Slashdotters are protected, computer displays don't produce UV-rays!
I dunno about bloat, but after reading through the article I just don't see anything I'd need. I never liked mouse gestures, for example, and I don't need more keyboard shortcuts, I mostly just use ctrl+n, ctrl+w, ctrl+r and ctrl+s in Firefox and that's it. I also have no need to insert notes into websites or have an integrated e-mail client; I have separate programs for that if/when I need it. It just doesn't seem to offer anything for me.
I, for one, have been using Firefox from the moment it was first released and I used Netscape before that. I still do not feel they've "abandoned" me in any way, the browser is still full-featured and useable and better than any other browser I've tried. And yet, I haven't had to "wrestle" with addons nor have I so much as even looked at about:config, let alone changed anything there.
As others have mentioned, the minimum requirement is OpenGL ES 3.1 - support. Others didn't say what that actually means in practice, so I'm jumping in. http://en.wikipedia.org/wiki/O... lists the following sample of hardware that supports OpenGL ES 3.1:
Adreno 400 series[25][26]
Intel HD Graphics for Intel Atom Z3700 series (Android)
Intel HD Graphics for Intel Celeron N and J series (Android)
Intel HD Graphics for Intel Pentium N and J series (Android)
Mali T6xx (midgard) series onwards[27] (Android, Linux)
Nvidia GeForce 400 series onwards (Windows)
Nvidia Tegra K1 (Android)
Nvidia Tegra X1 (Android)
PowerVR Series 6, 6XE, 6XT, 7XE and 7XT (Linux, Android)
Vivante GC2000 series onwards (optional with GC800 and GC1000)[28]
GeForce 400 is already 5 years old hardware, so as long as someone writes the drivers there's going to be a whole lot of supported hardware already out there and in active use. The list doesn't seem to mention AMD-hardware at all, but I would assume something similar as NVIDIA's 5 years.
It's free, but you are only allowed to distribute through Steam (meaning Valve gets 30-40% of your revenue).
No, you must also distribute through Steam, not only. Big difference.
I get your point, but I disagree on the part where you write that background operations need the disk or else they can't possibly work at all. Current smartphones are not designed to work without accessing the disk, that's true, but in theory 1GB of RAM is plenty for processes like polling a chat server or SMS to run entirely in it.
Yes, but if the phone was to lose power, like e.g. run out of battery or crash you'd lose all the data in RAM. From a general usability-standpoint losing any data that does only reside on your phone is unacceptable, most people would definitely throw a major fit about it even if it only ever actually harmed very few individuals. What if that SMS-message you just got, for example, was something important, but it got lost in bit-space? Well, you wouldn't know until it's too late!
As for keeping things in RAM: Android isn't known for being small and efficient, not even Lollipop. There are plenty of RAM-hungry background-tasks running and things like e.g. Facebook and such that are notoriously bad. Then some phones even offer things like spoken keyword-recognition that would require keeping a whole effing lot of stuff at all times in RAM just to work. I doubt 1GB RAM would be even nearly enough on most people's phones, though 2GB or more would of course help. You'd still have the issue I mentioned above, though.
As I said in the earlier comments, ARMv8 does support AES-encryption/-decryption in hardware. Most phones out there at the moment are not ARMv8, though, so they still have to resort to software-encryption/-decryption and that is the reason why Google backed off with the requirement of defaulting to encrypting devices. Up-and-coming higher-end phones are starting to ship with ARMv8 SoCs so they can perfectly feasibly enable full-disk encryption (FDE), but low-to-mid-end devices will most likely take several years before they have H/W-accelerated AES-encryption/-decryption.
So the protection is only effective if someone steals my phone while it's turned off, which is, like, 0.1% of the time?
Yes, that's exactly what it was designed for. If the system required you to enter the FDE-password whenever you open up the screen then how would background-processes, like e.g. SMS-receiving, chat and such stuff work? They'd only be able to access the disk when you have the display open and that'd obviously make the whole thing unuseable as a smartphone in the first place. No full-disk encryption scheme has been designed to withstand attacks originating from an already-running system since you need to keep the key in memory to do anything with the disk in the first place!