Fun fact: when a survey was done about people's attitudes towards diversity and their skills, the graph was almost a straight line between "Skilled, in favor", and "Mediocre, scared of diversity".
People who have valuable skills aren't scared that they're going to be replaced by a one legged black lesbian transwoman.
OK but are you a restaurant that accepts reservations? And if so, if the vast majority of automated calls were from people making reservations, wouldn't that be fucking stupid of you?
I'm not sure why you think ZTE's cellphone business is the only part that was sanctioned. There's nothing in TFS that says this, and this isn't about patents or some other narrow issue where only certain products from a company would be affected. Why would a government issue a ban on just part of a company's business for violating sanctions?
ZTE is a publicly traded company, and a massive one at that. What you're proposing is that every single ZTE shareholder would have to somehow invest in this new company, every single employee would have to resign from the original and join the new, and every single asset would have to be transferred to the new company tax free.
Or they could make it even more complicated by picking the people who would be in ZTE2. And selling the company's assets and hoping enough shareholders would be interested in the successor company.
And the shareholders are going to totally love this idea. Their board of directors just drove their investment into the ground, but they're totally OK about investing in the same bunch of idiots new company that will be run exactly the same way as the first.
This is the kind of "Ha, we showed them!" approach to avoiding the law that got Shawn Fanning into trouble when he claimed that he wasn't copying anything, Napster's customers were copying, so technically it's legal. It's Geek law or, in other words, bullshit.
It's not remotely similar, and the idiots who modded up the GP need to have their heads examined.
Developer mode is a system for gaining access to the internals of your Chromebook. It allows you to install arbitrary software. It was developed deliberately by Google, contradicting the GP's contention that Google has been trying to prevent people from doing this.
Developer mode however is an insecure system. It doesn't sandbox anything. When you're in developer mode, you literally have control over the entire workings of your Chromebook. You can even overwrite the BIOS.
What this article is about is the ability to run arbitrary GNU/Linux applications in a sandbox. It will not give you, or those applications, control over the Chromebook. Your data will remain safe.
The only thing the two things have in common are that if you want to run an arbitrary GNU/Linux application, both systems allow you to do so. That's a little like arguing that a car is the same thing as a bus because both can transport you to work.
The intel that was widely mocked and ridiculed because it was ridiculous and didn't substantiate the Israeli government's assertions?
Yes, we all saw it.
It actually proved that the agreement was working. Which is why pretty much every country is up in arms right now about Trump's decision. If Israel had actually shown Iran to be violating the agreement then nobody would care about Trump pulling out, because Iran would have effectively already have done it.
But instead we've moved to a point where no country in the world will sign an agreement with us that lasts longer than the current President's term in office. And even then, will wait until after 2020, possibly (God help us) 2024.
The damage this has done, both for our credibility, and our ability to use our credibility to promote peace, is astronomical. Wars that might never have happened are now inevitable.
(Correction, it's just over 100Mb at the moment, there were some background processes running that Windows didn't group with the main process. Again though, how's that going to be a problem running an installer on a machine that is never likely to have less than a gigabyte of memory, even if it's shitty?)
I use Atom with a bunch of plug-ins and generally have almost as many files open as I have tabs open on Firefox (because THAT'S HOW I WORK DAMNIT MIND YOUR OWN BUSINESS).
Right now it's taking up 50Mb. With an 'M'. The worst I've ever seen it was at half a G.
Electron isn't very efficient, but I don't think any supported Ubuntu platform should have a problem running an Electron based installer.
2008: "They should write it in Java", "Java sucks, it's sooo bloated"
1998: "They should write it in C++", "C++ sucks, it's sooo bloated"
1988: "They should write it in C", "C sucks, it's sooo bloated"
(I don't have one for 1978, because back then personal computers came with BASIC in ROM, there was nothing to install.)
I think you're overthinking this. We're basically looking at a massive increase in the number of laptops that have a supported open GNU/Linux system. On top of that:
- Chromebooks are more secure. The proposal from Google involves sandboxing GNU/Linux applications so they're effectively as secure as the existing Webapp/NaCl/Android applications that Chromebooks currently support.
- There's an extraordinary range of Chromebook laptops, from $150 next-gen netbooks (with 720P screens) to high end rivals to the MacBook Slim (or whatever the fuck they're branded as these days.)
Even better, Chromebooks don't have a capslock key.
From the point of view of the GP, this has opened up a whole range of laptops to him or her that weren't available before. But moreover, it's quite possible that the way this is implemented means those laptops will be more useful to him or her than either that cheap HP thing, or that mid-range Dell thing, or that expensive System76 Slabtop.
I'll be curious to know how well this works. My sole disappointment is I felt that between platforms like Electron and similar but not quite the same platforms like ChromeOS we were going to see more applications written in cross platform, easy to sandbox, ways, and "Debian under ChromeOS" seems like it might slow that movement down. But time will tell.
You appear to be referring to "Developer mode". Developer mode is available in all Chromebooks, and they've always made it easy to get into. It's off by default, because the entire point of the Chromebook is to be a secure platform, and giving people access outside of the sandbox is risky.
They've never "blocked" this functionality. They implemented the functionality.
What appears to be being announced today is that they've found a way to sandbox regular old GNU/Linux applications, so they have the same level of security that NaCl, Web apps, and sandboxed Android APKs do.
That's definitely new, and that's definitely positive.
That's what higher courts are for. What do you think happens in, say, Britain when a judge consistently rules in opposition to the law?
That's not to say there aren't ways in which it can be abused anyway (Britain has had its share of infamous judges), but those cases rarely actually become public knowledge.
Additionally, the only time I've heard of judges being "made accountable" in the US were highly politicized cases where one party (guess which! It was the same one every time!) decided it didn't like the decisions being made by certain judges because they were making it hard to violate the rights of minorities.
If you live somewhere where public transit is an option, you can massively cut down on your carbon footprint by simply using public transit.
Also not only do you cut down on your carbon footprint, but you'll usually save money, reduce your stress level, and while your journey may take longer (depends though, if going into the center of a city it can reduce it) you'll be able to relax a little and take some of your life back.
I'm not a Musk fanboy by any means, I invented hyperloop in high school as far as I'm concerned.
I too invented many forms of fantastic transportation as a kid, and continue to do so as an adult. Luckily for the world, I'm not stupid enough to pretend I think they'd all work, and I'm not the sort of person that, if a civil engineer or transit expert with decades of experience addressed fundamental issues with my "invention", would call that person an idiot because he's right and I don't have an answer for him.
Even the Boring Company's proposed "cheap" tunnels weigh in at $100M/mile - Musk's figures, not the figures of a civil engineer who knows what they're talking about - and that's before you put the sealed tube in (what, you think a cheaply bored tunnel is going to have perfectly smooth walls and be air tight?): the costs of making a fully tunneled transportation system is going to be astronomical.
In practice, the big ugly tubes will be on the surface. And NIMBYs will raise hell.
They're both shitty ideas! And I refuse to believe, given the massive "mistakes" in Musk's original white paper (proposed loop costing a fraction of what it was likely to cost, serving only two of the four CAHSR cities, having barely a quarter of the capacity, and that's if run at an unrealistically high efficiency), that the Hyperloop isn't really about being a hand out to big auto too, namely a way to sink CAHSR with vaporware.
I'd also mention the IHS wasn't just about the things you mentioned, but also about encouraging suburbanization. And that had as much to do with racism as it did "Big Auto".
If Hyperloop transportation is likely to be higher in cost than trucks, how does it expect to compete with rail? Rail is probably the most efficient, cheapest, form of freight transportation in the US today. While your statement that intercity rail cargo transport hasn't changed much since steam is stupid and false, it is true that developments in that area are slowing, largely because the system is already close to optimal.
Realistically, this is intended to compete with air freight - similar speeds, much cheaper costs. But air freight is still a niche market, and building out a network that can compete with the already entrenched, and not going away, network of air terminals, is going to be phenomenally expensive and time consuming.
This is yet another attempt to find a use for a technology, because people became excited about it and then realized that it can't do what they wanted it to do, but want it to exist anyway.
If you followed his twitter feed, he's not upset about how many people are shorting Tesla, he's giggling about it.
Well, he better knock that off, and fast. One very obvious explanation for his behavior on the call is that he's deliberately trying to tank the stock for some reason. If he's "giggling about" people shorting Tesla, then that would add evidence it's intentional.
If he's doing it intentionally (or if it looks like he is), he's opening himself up to lawsuits and possibly criminal investigations.
Even if he's found not guilty at the end of it, that's not a path anyone should be following.
IDK if we should go to a locked sandbox with very limited tools
Uh, OK. Are you under the impression that Javascript has access to your file system or something?
Insofar as some of these CPU bugs are supposedly exploitable in Javascript (and while one of Spectre/Meltdown was, the other wasn't but was widely confused as being the same thing), the same exploit would work in any Turing complete language.
So you'd need more than sandboxing to protect against these kinds of CPU flaw. You'd need a language so simple it makes DOS's COMMAND.COM batch language look like C++. You'd need a language you couldn't even implement Conway's Life in.
I... that... look, that's... that's not how it works. Not at all.
If something is failing now, saying "The problem is they might get rid of that person they're keeping on to" makes little or no sense.
Trump might be the reason 170M people are gone. Or it might be the Neo-Nazis. Or it might be the harassment squads. Or it might be that their website is shitty and they keep adding "Features" nobody wants that actually makes it harder to use, like that idiot "Let's treat "likes" like "retweets"" thing they do that cannot be permanently turned off.
Or it could be one of a whole host of other reasons. But it certainly isn't because they might get rid of Trump but haven't yet.
YOU are the Developer. It is YOUR obligation to ensure you don't link to bogus, questionable or potentially malicious libraries.
1. Best practices dictates you should never reinvent the wheel. Someone else, apparently, has done it better than you have somewhere. You should seek them out and use their code.
2. Best practices dictates you should always keep on top of updates, and ensure that you're always running the latest version of every bit of code you get externally
3. Apparently you should also know, somehow, that a project you use now contains malicious code.
Honestly guys, we need a new set of "best practices" because this shit isn't working. We want to program, not be sysadmins for a giant ball of interconnected third party plug-ins.
It's not an attempt to fight bigotry with worse bigotry, it's an attempt to fight intentional or unintentional discrimination with a small amount of discrimination in the other direction.
I don't know where you're getting "bigotry" from, and I can't imagine why you think a small effort to encourage underrepresented groups into a project is somehow worse than overwhelming systemic efforts to channel only a privileged minority into it.
I am not making a judgment here about whether it's a good idea, but it's absolutely not worse than the system it's trying to undo, and it has nothing to do with bigotry.
Slashdot Mirror
Fun fact: when a survey was done about people's attitudes towards diversity and their skills, the graph was almost a straight line between "Skilled, in favor", and "Mediocre, scared of diversity".
People who have valuable skills aren't scared that they're going to be replaced by a one legged black lesbian transwoman.
OK but are you a restaurant that accepts reservations? And if so, if the vast majority of automated calls were from people making reservations, wouldn't that be fucking stupid of you?
I think we need a law against people who draw the conclusion that because someone has suggested something, they must be proposing a law to enforce it.
Where are you getting it from that the astronomers think the error rate of Gaia is exactly zero?
I'm not sure why you think ZTE's cellphone business is the only part that was sanctioned. There's nothing in TFS that says this, and this isn't about patents or some other narrow issue where only certain products from a company would be affected. Why would a government issue a ban on just part of a company's business for violating sanctions?
ZTE is a publicly traded company, and a massive one at that. What you're proposing is that every single ZTE shareholder would have to somehow invest in this new company, every single employee would have to resign from the original and join the new, and every single asset would have to be transferred to the new company tax free.
Or they could make it even more complicated by picking the people who would be in ZTE2. And selling the company's assets and hoping enough shareholders would be interested in the successor company.
And the shareholders are going to totally love this idea. Their board of directors just drove their investment into the ground, but they're totally OK about investing in the same bunch of idiots new company that will be run exactly the same way as the first.
This is the kind of "Ha, we showed them!" approach to avoiding the law that got Shawn Fanning into trouble when he claimed that he wasn't copying anything, Napster's customers were copying, so technically it's legal. It's Geek law or, in other words, bullshit.
Not going to happen.
It's not remotely similar, and the idiots who modded up the GP need to have their heads examined.
Developer mode is a system for gaining access to the internals of your Chromebook. It allows you to install arbitrary software. It was developed deliberately by Google, contradicting the GP's contention that Google has been trying to prevent people from doing this.
Developer mode however is an insecure system. It doesn't sandbox anything. When you're in developer mode, you literally have control over the entire workings of your Chromebook. You can even overwrite the BIOS.
What this article is about is the ability to run arbitrary GNU/Linux applications in a sandbox. It will not give you, or those applications, control over the Chromebook. Your data will remain safe.
The only thing the two things have in common are that if you want to run an arbitrary GNU/Linux application, both systems allow you to do so. That's a little like arguing that a car is the same thing as a bus because both can transport you to work.
The intel that was widely mocked and ridiculed because it was ridiculous and didn't substantiate the Israeli government's assertions?
Yes, we all saw it.
It actually proved that the agreement was working. Which is why pretty much every country is up in arms right now about Trump's decision. If Israel had actually shown Iran to be violating the agreement then nobody would care about Trump pulling out, because Iran would have effectively already have done it.
But instead we've moved to a point where no country in the world will sign an agreement with us that lasts longer than the current President's term in office. And even then, will wait until after 2020, possibly (God help us) 2024.
The damage this has done, both for our credibility, and our ability to use our credibility to promote peace, is astronomical. Wars that might never have happened are now inevitable.
(Correction, it's just over 100Mb at the moment, there were some background processes running that Windows didn't group with the main process. Again though, how's that going to be a problem running an installer on a machine that is never likely to have less than a gigabyte of memory, even if it's shitty?)
I use Atom with a bunch of plug-ins and generally have almost as many files open as I have tabs open on Firefox (because THAT'S HOW I WORK DAMNIT MIND YOUR OWN BUSINESS).
Right now it's taking up 50Mb. With an 'M'. The worst I've ever seen it was at half a G.
Electron isn't very efficient, but I don't think any supported Ubuntu platform should have a problem running an Electron based installer.
2008: "They should write it in Java", "Java sucks, it's sooo bloated"
1998: "They should write it in C++", "C++ sucks, it's sooo bloated"
1988: "They should write it in C", "C sucks, it's sooo bloated"
(I don't have one for 1978, because back then personal computers came with BASIC in ROM, there was nothing to install.)
I think you're overthinking this. We're basically looking at a massive increase in the number of laptops that have a supported open GNU/Linux system. On top of that:
- Chromebooks are more secure. The proposal from Google involves sandboxing GNU/Linux applications so they're effectively as secure as the existing Webapp/NaCl/Android applications that Chromebooks currently support.
- There's an extraordinary range of Chromebook laptops, from $150 next-gen netbooks (with 720P screens) to high end rivals to the MacBook Slim (or whatever the fuck they're branded as these days.)
Even better, Chromebooks don't have a capslock key.
From the point of view of the GP, this has opened up a whole range of laptops to him or her that weren't available before. But moreover, it's quite possible that the way this is implemented means those laptops will be more useful to him or her than either that cheap HP thing, or that mid-range Dell thing, or that expensive System76 Slabtop.
I'll be curious to know how well this works. My sole disappointment is I felt that between platforms like Electron and similar but not quite the same platforms like ChromeOS we were going to see more applications written in cross platform, easy to sandbox, ways, and "Debian under ChromeOS" seems like it might slow that movement down. But time will tell.
That's incredibly misleading.
You appear to be referring to "Developer mode". Developer mode is available in all Chromebooks, and they've always made it easy to get into. It's off by default, because the entire point of the Chromebook is to be a secure platform, and giving people access outside of the sandbox is risky.
They've never "blocked" this functionality. They implemented the functionality.
What appears to be being announced today is that they've found a way to sandbox regular old GNU/Linux applications, so they have the same level of security that NaCl, Web apps, and sandboxed Android APKs do.
That's definitely new, and that's definitely positive.
That's what higher courts are for. What do you think happens in, say, Britain when a judge consistently rules in opposition to the law?
That's not to say there aren't ways in which it can be abused anyway (Britain has had its share of infamous judges), but those cases rarely actually become public knowledge.
Additionally, the only time I've heard of judges being "made accountable" in the US were highly politicized cases where one party (guess which! It was the same one every time!) decided it didn't like the decisions being made by certain judges because they were making it hard to violate the rights of minorities.
Also not only do you cut down on your carbon footprint, but you'll usually save money, reduce your stress level, and while your journey may take longer (depends though, if going into the center of a city it can reduce it) you'll be able to relax a little and take some of your life back.
Just saying.
I too invented many forms of fantastic transportation as a kid, and continue to do so as an adult. Luckily for the world, I'm not stupid enough to pretend I think they'd all work, and I'm not the sort of person that, if a civil engineer or transit expert with decades of experience addressed fundamental issues with my "invention", would call that person an idiot because he's right and I don't have an answer for him.
Even the Boring Company's proposed "cheap" tunnels weigh in at $100M/mile - Musk's figures, not the figures of a civil engineer who knows what they're talking about - and that's before you put the sealed tube in (what, you think a cheaply bored tunnel is going to have perfectly smooth walls and be air tight?): the costs of making a fully tunneled transportation system is going to be astronomical.
In practice, the big ugly tubes will be on the surface. And NIMBYs will raise hell.
They're both shitty ideas! And I refuse to believe, given the massive "mistakes" in Musk's original white paper (proposed loop costing a fraction of what it was likely to cost, serving only two of the four CAHSR cities, having barely a quarter of the capacity, and that's if run at an unrealistically high efficiency), that the Hyperloop isn't really about being a hand out to big auto too, namely a way to sink CAHSR with vaporware.
I'd also mention the IHS wasn't just about the things you mentioned, but also about encouraging suburbanization. And that had as much to do with racism as it did "Big Auto".
If Hyperloop transportation is likely to be higher in cost than trucks, how does it expect to compete with rail? Rail is probably the most efficient, cheapest, form of freight transportation in the US today. While your statement that intercity rail cargo transport hasn't changed much since steam is stupid and false, it is true that developments in that area are slowing, largely because the system is already close to optimal.
Realistically, this is intended to compete with air freight - similar speeds, much cheaper costs. But air freight is still a niche market, and building out a network that can compete with the already entrenched, and not going away, network of air terminals, is going to be phenomenally expensive and time consuming.
This is yet another attempt to find a use for a technology, because people became excited about it and then realized that it can't do what they wanted it to do, but want it to exist anyway.
It's dumb, let it die.
Well, he better knock that off, and fast. One very obvious explanation for his behavior on the call is that he's deliberately trying to tank the stock for some reason. If he's "giggling about" people shorting Tesla, then that would add evidence it's intentional.
If he's doing it intentionally (or if it looks like he is), he's opening himself up to lawsuits and possibly criminal investigations.
Even if he's found not guilty at the end of it, that's not a path anyone should be following.
Steel isn't really a solution to the concrete CO2 problem though, production of steel also results in high CO2 emissions.
Uh, OK. Are you under the impression that Javascript has access to your file system or something?
Insofar as some of these CPU bugs are supposedly exploitable in Javascript (and while one of Spectre/Meltdown was, the other wasn't but was widely confused as being the same thing), the same exploit would work in any Turing complete language.
So you'd need more than sandboxing to protect against these kinds of CPU flaw. You'd need a language so simple it makes DOS's COMMAND.COM batch language look like C++. You'd need a language you couldn't even implement Conway's Life in.
Not gonna happen.
I... that... look, that's... that's not how it works. Not at all.
If something is failing now, saying "The problem is they might get rid of that person they're keeping on to" makes little or no sense.
Trump might be the reason 170M people are gone. Or it might be the Neo-Nazis. Or it might be the harassment squads. Or it might be that their website is shitty and they keep adding "Features" nobody wants that actually makes it harder to use, like that idiot "Let's treat "likes" like "retweets"" thing they do that cannot be permanently turned off.
Or it could be one of a whole host of other reasons. But it certainly isn't because they might get rid of Trump but haven't yet.
1. Best practices dictates you should never reinvent the wheel. Someone else, apparently, has done it better than you have somewhere. You should seek them out and use their code.
2. Best practices dictates you should always keep on top of updates, and ensure that you're always running the latest version of every bit of code you get externally
3. Apparently you should also know, somehow, that a project you use now contains malicious code.
Honestly guys, we need a new set of "best practices" because this shit isn't working. We want to program, not be sysadmins for a giant ball of interconnected third party plug-ins.
It's not an attempt to fight bigotry with worse bigotry, it's an attempt to fight intentional or unintentional discrimination with a small amount of discrimination in the other direction.
I don't know where you're getting "bigotry" from, and I can't imagine why you think a small effort to encourage underrepresented groups into a project is somehow worse than overwhelming systemic efforts to channel only a privileged minority into it.
I am not making a judgment here about whether it's a good idea, but it's absolutely not worse than the system it's trying to undo, and it has nothing to do with bigotry.