Google doesn't ship Chrome for FreeBSD. Chromium is in packages, but Chrome and Chromium are not the same thing - Chrome includes things like the Netflix DRM. Updates to the Chromium port also take a while because Google refuses to accept patches for FreeBSD (closing the submitted issues as 'FreeBSD is not a supported platform') and so the port needs to maintain a large set of patches.
The problem with that argument is that people might think 'well, if the key is going to be locked away somewhere securely and only used if I commit a crime (which I know I will never do, because I am a law-abiding citizen with nothing to hide), then that's probably fine.' The other part of the issue is that storing that many keys securely is really, really hard. The combined value of those keys to criminals is far more than the contents of Fort Knox. Who would be responsible for keeping it secure from attackers? The other important part of the argument is that, if that key exists, it's not just your government that can access it. How would you feel about Chinese or Russian law enforcement having a key to your house?
If the button did not exist, would the person have sent the message telling their friends about the purchase? If so, then it's hard to justify that it's spam originating from the company[1]. If not, then it's clear that Amazon is at least partially to blame for someone receiving unsolicited commercial email advertising Amazon.
Did the email just contain a message from the person, or was it decorated with Amazon branding and 'click here to buy more stuff from Amazon' logos? If it just contained the message, then it's easy to argue that Amazon is just helping people communicate, if it contains Amazon advertising then it's much harder to argue that.
[1] Iit may still be spam from the individual, of course - sending bulk commercial email to someone that you don't have a prior business relationship with is typically the legal definition of spam. It's still spam if you send an advertising email to all of your friends, though most people wouldn't mind too much if it's a one-off event.
Not sure about your locale, but in the UK you are only required to have third-party cover. I believe most western countries have similar rules. If you're involved in an accident, then you must be able to pay for the damage that you inflict on others, or you are not allowed to use the public highways. You are free not to have any cover for damage to your property or self, and you can put up a bond if you are willing to pay the total cost out of pocket (or get very cheap premiums if you're willing to pay the first few thousand out of pocket and only claim for really bad accidents).
I suspect that would only be a problem if the rate of basic income were fixed across the EU. Wages are lower in the east, but so is cost of living, so if implemented properly then basic income would buy the same standard of living in each country. I can imagine people moving south (why live on the poverty line in the UK when you can live on the poverty line by the sea in Greece or Portugal?), but moving west would only make sense if they expected to get jobs that were more in demand in the west than the east.
Basic income is about the same level as a full-time minimum wage job and they'd still be being paid this on top of their salary (just by their home country). Would you expect them to really decide to drop back to half of the income that they'd become accustomed to?
What percentage of users of any computer or smartphone do you think actually notice who their search provider is? These days, there are basically the small set of people that set it explicitly to DuckDuckGo and the overwhelming majority who just use whatever the default is because it's good enough.
FreeBSD introduced jails in 2000. Solaris gained support for Zones (jails, but rebranded) in 2004. Linux still has a load of competing solution and no sensible management interface, hence Docker exists to add them as a third party thing.
The Nights Dawn trilogy. It's about 3,000 pages long, and goes rapidly downhill in the last 300. Aside from Misspent Youth, everything else Peter F. Hamilton has written has been worth reading, but Nights Dawn put off a lot of people by having a truly bad ending.
There is a well-known defence against this kind of attack. You don't put up generic dialog boxes like this. When the user configures the app, they should provide a picture or a pass phrase, which is displayed in the dialog box whenever it appears. If the dialog does not contain that picture / phrase, then the user knows that it's not the one for their system.
I stopped reading New Scientist about 20 years ago, and that summary doesn't sound too unlike my recollections of it. Did it improve for a bit in the middle?
With all of the good things that he's written, I think that we can forgive the author one deus ex machina. And never speak of that trilogy again. Ever.
That doesn't really follow. If you wanted to collect solar wind, you'd need to condense it, which you'd do by large magnetic fields to funnel it into a collector. A relatively small collector would collect the hydrogen from a very large area. Of course, if you're able to create strong and structured magnetic fields over such an area, you could probably also skim hydrogen from the sun a bit more aggressively.
No they don't. They have okay pay, but there are at least half a dozen large companies that pay better, try to hire the same people, and will give them an answer sooner.
Responsible in this case would have been immediate disclosure of the work-around, then waiting a few hours for all of the distributions that have signed on to coordinate releases for this kind of security update to have their packages ready before releasing the details of the exploit. Instead, they botched the release and told everyone how to exploit it before anyone had updated packages.
Google's process is very much geared towards finding problem solvers, ignoring the need of finding the people who can identify the correct problems to solve. Their interview process isn't too bad with that goal in mind. The real problem is what happens afterwards. They make you wait a few months while they make a decision, and then they want you to start the following week. The only people who are still looking for a job by the time Google decides that they actually want them are PhD students who applied during their final year. Everyone else has already taken a good offer somewhere else.
8x PCIe v3 gives you 7,880MB/s. Even just throwing the data out over the two 10GigE connectors, you'll only use a third of that. I doubt that 8 Cortex-A57 cores are going to find themselves data starved processing the rest.
JavaScript is not a completely terrible language (though the implicit conversions and weird semantics of the + operator make it far from one of the best - at least it has first-class closures and sane variadics), but every time I try to use it for something serious I get hit with the problem that it only supports 53-bit integers. For interoperability with code written in pretty much any other language, not having a 64-bit integer type is annoying.
That's only true as long as they are the only contributors. If they take patches from anyone else (without copyright assignment or some kind of contributors' agreement that allows them to use the code under a different license) then having it GPL'd would prevent them from using it in a proprietary product. Which effectively boils down to preventing them from bothering to do the open source release at all. Which tends to be the point that GPL advocates miss. I'd rather a company open sourced 10% of their code (or even 1%) than 0%.
It is MIT licensed, but that doesn't mean that they can revoke the license. You can fork it and add anything that you want. They can take your changes and decide not to open source the next release, but you'd still have all of the code that they'd already released.
Slashdot Mirror
Those using FreeBSD basically have to use Chrome
Google doesn't ship Chrome for FreeBSD. Chromium is in packages, but Chrome and Chromium are not the same thing - Chrome includes things like the Netflix DRM. Updates to the Chromium port also take a while because Google refuses to accept patches for FreeBSD (closing the submitted issues as 'FreeBSD is not a supported platform') and so the port needs to maintain a large set of patches.
You know what they say about people who don't study history? That they've never heard of an East India Company.
The problem with that argument is that people might think 'well, if the key is going to be locked away somewhere securely and only used if I commit a crime (which I know I will never do, because I am a law-abiding citizen with nothing to hide), then that's probably fine.' The other part of the issue is that storing that many keys securely is really, really hard. The combined value of those keys to criminals is far more than the contents of Fort Knox. Who would be responsible for keeping it secure from attackers? The other important part of the argument is that, if that key exists, it's not just your government that can access it. How would you feel about Chinese or Russian law enforcement having a key to your house?
If the button did not exist, would the person have sent the message telling their friends about the purchase? If so, then it's hard to justify that it's spam originating from the company[1]. If not, then it's clear that Amazon is at least partially to blame for someone receiving unsolicited commercial email advertising Amazon.
Did the email just contain a message from the person, or was it decorated with Amazon branding and 'click here to buy more stuff from Amazon' logos? If it just contained the message, then it's easy to argue that Amazon is just helping people communicate, if it contains Amazon advertising then it's much harder to argue that.
[1] Iit may still be spam from the individual, of course - sending bulk commercial email to someone that you don't have a prior business relationship with is typically the legal definition of spam. It's still spam if you send an advertising email to all of your friends, though most people wouldn't mind too much if it's a one-off event.
Two words: Conspicuous consumption.
Not sure about your locale, but in the UK you are only required to have third-party cover. I believe most western countries have similar rules. If you're involved in an accident, then you must be able to pay for the damage that you inflict on others, or you are not allowed to use the public highways. You are free not to have any cover for damage to your property or self, and you can put up a bond if you are willing to pay the total cost out of pocket (or get very cheap premiums if you're willing to pay the first few thousand out of pocket and only claim for really bad accidents).
Given how easily Snowden got the data, you can bet that the FSB has had copies of everything and more long before The Guardian.
I suspect that would only be a problem if the rate of basic income were fixed across the EU. Wages are lower in the east, but so is cost of living, so if implemented properly then basic income would buy the same standard of living in each country. I can imagine people moving south (why live on the poverty line in the UK when you can live on the poverty line by the sea in Greece or Portugal?), but moving west would only make sense if they expected to get jobs that were more in demand in the west than the east.
Basic income is about the same level as a full-time minimum wage job and they'd still be being paid this on top of their salary (just by their home country). Would you expect them to really decide to drop back to half of the income that they'd become accustomed to?
What percentage of users of any computer or smartphone do you think actually notice who their search provider is? These days, there are basically the small set of people that set it explicitly to DuckDuckGo and the overwhelming majority who just use whatever the default is because it's good enough.
FreeBSD introduced jails in 2000. Solaris gained support for Zones (jails, but rebranded) in 2004. Linux still has a load of competing solution and no sensible management interface, hence Docker exists to add them as a third party thing.
The Nights Dawn trilogy. It's about 3,000 pages long, and goes rapidly downhill in the last 300. Aside from Misspent Youth, everything else Peter F. Hamilton has written has been worth reading, but Nights Dawn put off a lot of people by having a truly bad ending.
There is a well-known defence against this kind of attack. You don't put up generic dialog boxes like this. When the user configures the app, they should provide a picture or a pass phrase, which is displayed in the dialog box whenever it appears. If the dialog does not contain that picture / phrase, then the user knows that it's not the one for their system.
I stopped reading New Scientist about 20 years ago, and that summary doesn't sound too unlike my recollections of it. Did it improve for a bit in the middle?
With all of the good things that he's written, I think that we can forgive the author one deus ex machina. And never speak of that trilogy again. Ever.
That doesn't really follow. If you wanted to collect solar wind, you'd need to condense it, which you'd do by large magnetic fields to funnel it into a collector. A relatively small collector would collect the hydrogen from a very large area. Of course, if you're able to create strong and structured magnetic fields over such an area, you could probably also skim hydrogen from the sun a bit more aggressively.
The fact is, google has good pay
No they don't. They have okay pay, but there are at least half a dozen large companies that pay better, try to hire the same people, and will give them an answer sooner.
Responsible in this case would have been immediate disclosure of the work-around, then waiting a few hours for all of the distributions that have signed on to coordinate releases for this kind of security update to have their packages ready before releasing the details of the exploit. Instead, they botched the release and told everyone how to exploit it before anyone had updated packages.
And they found this and patched it very fast.
And then completely screwed up responsible disclosure, because apparently time zones are hard.
Google's process is very much geared towards finding problem solvers, ignoring the need of finding the people who can identify the correct problems to solve. Their interview process isn't too bad with that goal in mind. The real problem is what happens afterwards. They make you wait a few months while they make a decision, and then they want you to start the following week. The only people who are still looking for a job by the time Google decides that they actually want them are PhD students who applied during their final year. Everyone else has already taken a good offer somewhere else.
Storage controllers tend to be x8 devices
8x PCIe v3 gives you 7,880MB/s. Even just throwing the data out over the two 10GigE connectors, you'll only use a third of that. I doubt that 8 Cortex-A57 cores are going to find themselves data starved processing the rest.
What are you doing that uses the FFI in V8?
JavaScript is not a completely terrible language (though the implicit conversions and weird semantics of the + operator make it far from one of the best - at least it has first-class closures and sane variadics), but every time I try to use it for something serious I get hit with the problem that it only supports 53-bit integers. For interoperability with code written in pretty much any other language, not having a 64-bit integer type is annoying.
That's only true as long as they are the only contributors. If they take patches from anyone else (without copyright assignment or some kind of contributors' agreement that allows them to use the code under a different license) then having it GPL'd would prevent them from using it in a proprietary product. Which effectively boils down to preventing them from bothering to do the open source release at all. Which tends to be the point that GPL advocates miss. I'd rather a company open sourced 10% of their code (or even 1%) than 0%.
It is MIT licensed, but that doesn't mean that they can revoke the license. You can fork it and add anything that you want. They can take your changes and decide not to open source the next release, but you'd still have all of the code that they'd already released.