I think this can be generalized to: dating is a game of statistics. Think about what traits are correlated with what demographics to maximise your chances of success.
there is zero chance they could recover the cost from GCHQ
Interesting thought: we normally regard investor-state dispute settlement clauses negatively, but this is an actual case where they would be helpful in compensating Gemalto for the harm caused to them. Requiring the NSA, etc. to pay compensation for the harm caused could do a lot to curtail their actions.
Yes, an individual render operation is always going to be more expensive. But it's not necessary to always update the screen - given that watches are usually held in a specific orientation when being read, you could easily reduce power consumption by an order of magnitude if you only rendered the time when it was actually being read. There's also the possibility of drawing power from the wearer's movement, similar to an automatic.
A librarian that does not value paper. That is like a cardiovascular surgeon that eats a pound of bacon every day.
Librarians value knowledge, not paper; the paper is just a medium. Also, saturated fat isn't bad for your heart (in fact the evidence is leaning towards it being good for your HDL/LDL ratio), and bacon is actually a common occurrence in low carb breakfasts.
I want my children and grandchildren to have the books I purchased and read. Those digital formats will be gone in just a few years while I have books older than my country.
PDF and ePUB aren't going anywhere. There's a distinction to be made between ebooks and DRM, in much the same way as there is between digital music (MP3, AAC, etc.) and DRM.
Most people want some forms of censorship, if only for the simple matter of organizing your content.
That's not censorship, that's filtering. The difference is that filtering allows the user to control what they view, while censorship places that control in the hands of the publisher.
I personally would like to see more changes like this because not everyone on the internet can discern between what they click on...
Blogger already had warning pages appear for adult blogs which had to be dismissed before the user could view the content. Those were sufficient to prevent anyone from viewing content they didn't want to, (and nothing short of constant vigilance is going to stop a kid from viewing content they're interested in.)
All this does is force active adult blogs to migrate to other sites, and take a bunch of inactive ones offline (unless the Internet Archive archives them before then).
Then surprise surprise AMD chips trade blows with chips costing more than twice as much [youtube.com] with several tests the AMD outright smoking and in others within a couple percentage points of the i5s.
The issue is that the damage is done; AMD hasn't updated their CPU lineup recently. The FX-8350 was originally released in late 2012 and still seems to be the best option from their FX series. (The FX-8370 is just a nicer binning, and the FX-9xxx appear to be ridiculously overclocked, with almost twice the TDP.) I'm planning to upgrade my PC later this year, but buying a 3 year old CPU just seems insane. In contrast, Haswell processors are barely a year old, and a Haswell i5 delivers comparable performance.
Meanwhile, AMD's APU lines max out at 4 cores, which is a step backwards from my Phenom II hex core, and the APU offers little advantage given that I'd be getting a discrete graphics card anyway. (The main workload for this system is compilation, so believe me when I say that the no. of cores absolutely does matter.)
I'm the sort of person who should be a shoe-in for AMD's high end, but I can't even tell if the FX line is obsolete or not. I think that says a lot about their execution.
They shouldn't just be hit via a class action suit (assuming Lenovo isn't sticking a "binding arbitration" clause to defeat the ability for consumers to seek recourse) but Federal prosecution under one of the many computer security laws that would string up anyone else.
Honest question: is putting a backdoor/vulnerability into a product actually a crime in the US? As I understand it, most of the computer security laws are about actively breaking in ("gaining access"). The closest I can think of are contractual issues with sale ("fitness for purpose") and negligence, but both of those are civil.
I have a feeling this is less about recovering from damages and more about teaching them a formal lesson (well, cashing-in under the guise of teaching them a formal lesson).
That's the entire point of a class action suit. To stop powerful companies from doing a large number of small harms and getting away with it.
Ironically, awarding damages on an individual basis to the claimants would be far more punitive than whatever damages are awarded.
You assume it's necessary to show an ad before every video. If the video isn't long enough to insert an ad after, just don't show one until the next video has been viewed.
There hasn't, but I wouldn't expect it to matter. I don't believe the name is actually used anywhere (everyone just uses the version number), and its only defined in a makefile that's part of the kernel git repo. I'm not even sure if there's a rule for when it should be changed - I suspect it's merely whenever Linus feels like it.
The actual evidence is a little more mixed. From Wikipedia:
Most studies support a link between adult criminality and testosterone, although the relationship is modest if examined separately for each sex. Nearly all studies of juvenile delinquency and testosterone are not significant. Most studies have also found testosterone to be associated with behaviors or personality traits linked with criminality such as antisocial behavior and alcoholism. Many studies have also been done on the relationship between more general aggressive behavior/feelings and testosterone. About half the studies have found a relationship and about half no relationship.[72]...
It has been empirically shown that boys who had a history of high physical aggression, from age 6 to 12, were found to have lower testosterone levels at age 13 compared with boys with no history of high physical aggression. The former were also failing in school and were unpopular with their peers. Both concurrent and longitudinal analyses indicate that testosterone levels were positively associated with social success rather than with physical aggression.[76]
As a result of its questionable status with regard to copyright restrictions and other potential legal issues, the TrueCrypt License is not considered "free" by several major Linux distributions and is therefore not included in Debian, Ubuntu, Fedora, openSUSE, or Gentoo.
While this is true of the others, it is not true of Gentoo. Gentoo's policy seems to be that while the base system should not depend on non-FOSS components, having them present in the main tree is fine. (This might be partly because it's pretty easy to filter which licenses you want on your system using ACCEPT_LICENSE.)
Do you honestly think installing your own OS image is enough ? You can embed malware in the bios. Would you like me to post a proof of concept ?
I won't buy a Lenovo after this incident. No way. Done.
You don't need to. Their business-grade lines (e.g. Thinkpads) include remote administration tools that basically let you do whatever you want to the laptop over Ethernet without turning it on. You can disable it in the BIOS/UEFI, but it's enabled by default.
Generics, as done in some languages, are excellent. Java is not one of those languages, primarily due to how it handles type erasure. Requiring the programmer to use an explicitly boxed type (Integer instead of int) is also rather clumsy, as is the lack of inference for type parameters.
IMO, C#'s implementation of generics is considerably better.
The other half is of course managed languages, but really slimming down C# to work on a RP doesn't seem impractical - just something that MS hasn't had a reason to focus on.
Or if you're impatient, you could just use D - the syntax is virtually identical to C#, but you get the performance of native code. I actually wrote some patches for buildroot a while back that added support for gdc, which make it pretty easy to compile a suitable toolchain for using D on a Raspberry Pi.
I frequently work with people who are terrified to touch anything related to kernel.
It's more than that - people (inexperienced developers in particular) are terrified to break outside of their encapsulated environment. They instinctively assume the standard libraries are flawless and bug-free, and that they don't have to worry about how they work, which is a useful approximation until that's no longer the case. The idea of looking at the source for said library to understand it better simply doesn't occur to them, or they overestimate its complexity. (To be fair, this is a view strongly encouraged by closed source software, which is a black box to even those interested in the internals.)
The kernel is different from userspace because it doesn't have the same protections and isolation. In userspace, (un)locking the wrong mutex gets you an exception with a nice message or a well defined error code. Do the same thing in the kernel and you get an oops with the stack trace pointing to a BUG_ON() assertion with some confusing looking code. It's the very opposite of the encapsulated environment presented by many userspace languages - misusing the mutex results in the developer being forced to look at the workings of it. Once you become used to that, your skill at working with complex systems develops rapidly.
It might be something a college student might be able to devote time and effort to. Obviously, it won't pay directly, but after graduating, being able to point to a module in the kernel with one's name on it is a good way to find jobs.
I'll second this. I'm a college* student who's currently picking up kernel programming for this exact reason. (Also, I find file system design interesting.) Whether or not it will help my employability remains to be seen, but it only takes the perception of utility to result in an increase in development.
That's a terrible idea. It's not Ubuntu vs Mint vs Fedora, it's Ubuntu vs Debian vs Gentoo vs Arch - there's a massive spectrum of distros in terms of ease of use, stability, customizability, etc. There is no one size fits all solution - a rock solid production system is going to be completely different to a bleeding edge development system.
Separating distros from upstream projects is also important because the upstream projects rely on distros adopting their latest software at different times to maintain stability. Users of bleeding edge distros like Arch effectively test the software for users of more conservative distros like Debian.
It's also worth noting that Kubuntu is probably one of the worst KDE-based distros - IIRC, the 4.0 release mess was exacerbated by their maintainers configuring things poorly. And let's not forget that KDE is leaning towards using systemd internally... (I use systemd myself, but I think the idea of forcing it upon users is ludicrous.)
It would be fine if they were simply removing OC support on new cards. The problem is that they are removing a feature from a product that has already been sold, and even used as an advertising point by some manufacturers. This is no different to Sony removing OtherOS from the PS3.
It's poor style to not indent the inner for, because C family languages do allow one line for-statements, which the body is replaced by a single semi-colon. Someone skimming over the code could easily interpret it as such.
Wayland is a replacement for the X window server. (X is the software the sits between your graphics drivers and your desktop environment.) X is ancient at this point and has fundamental issues with its design that mean security issues which can't be fixed without breaking backward compatibility. X has a lot of features that it is required to support to maintain backward compatibility that no one uses any more - modern systems work by just pushing blocks of pixels to it. Wayland only supports this method of operation, so it's much simpler than X. Wayland's main developers are ex-X developers who are intimately familiar with the problem's X has (see Daniel Stone's talk on youtube for more info).
Wayland has been somewhat controversial because it does not have support for network transparency, unlike X. However, most modern apps don't use X in a network transparent way, and X network transparency is actually slower than VNC. The Wayland developers have advocated an approach similar to VNC for network transparency, but AFAIK there's no major implementation of it yet, so it remains controversial (even though almost no one is actually using it right now).
Slashdot Mirror
Yes, yes we do.
I think this can be generalized to: dating is a game of statistics. Think about what traits are correlated with what demographics to maximise your chances of success.
there is zero chance they could recover the cost from GCHQ
Interesting thought: we normally regard investor-state dispute settlement clauses negatively, but this is an actual case where they would be helpful in compensating Gemalto for the harm caused to them. Requiring the NSA, etc. to pay compensation for the harm caused could do a lot to curtail their actions.
Kmail
Yes, an individual render operation is always going to be more expensive. But it's not necessary to always update the screen - given that watches are usually held in a specific orientation when being read, you could easily reduce power consumption by an order of magnitude if you only rendered the time when it was actually being read. There's also the possibility of drawing power from the wearer's movement, similar to an automatic.
A librarian that does not value paper. That is like a cardiovascular surgeon that eats a pound of bacon every day.
Librarians value knowledge, not paper; the paper is just a medium. Also, saturated fat isn't bad for your heart (in fact the evidence is leaning towards it being good for your HDL/LDL ratio), and bacon is actually a common occurrence in low carb breakfasts.
I want my children and grandchildren to have the books I purchased and read. Those digital formats will be gone in just a few years while I have books older than my country.
PDF and ePUB aren't going anywhere. There's a distinction to be made between ebooks and DRM, in much the same way as there is between digital music (MP3, AAC, etc.) and DRM.
Most people want some forms of censorship, if only for the simple matter of organizing your content.
That's not censorship, that's filtering. The difference is that filtering allows the user to control what they view, while censorship places that control in the hands of the publisher.
I personally would like to see more changes like this because not everyone on the internet can discern between what they click on...
Blogger already had warning pages appear for adult blogs which had to be dismissed before the user could view the content. Those were sufficient to prevent anyone from viewing content they didn't want to, (and nothing short of constant vigilance is going to stop a kid from viewing content they're interested in.)
All this does is force active adult blogs to migrate to other sites, and take a bunch of inactive ones offline (unless the Internet Archive archives them before then).
Then surprise surprise AMD chips trade blows with chips costing more than twice as much [youtube.com] with several tests the AMD outright smoking and in others within a couple percentage points of the i5s.
The issue is that the damage is done; AMD hasn't updated their CPU lineup recently. The FX-8350 was originally released in late 2012 and still seems to be the best option from their FX series. (The FX-8370 is just a nicer binning, and the FX-9xxx appear to be ridiculously overclocked, with almost twice the TDP.) I'm planning to upgrade my PC later this year, but buying a 3 year old CPU just seems insane. In contrast, Haswell processors are barely a year old, and a Haswell i5 delivers comparable performance.
Meanwhile, AMD's APU lines max out at 4 cores, which is a step backwards from my Phenom II hex core, and the APU offers little advantage given that I'd be getting a discrete graphics card anyway. (The main workload for this system is compilation, so believe me when I say that the no. of cores absolutely does matter.)
I'm the sort of person who should be a shoe-in for AMD's high end, but I can't even tell if the FX line is obsolete or not. I think that says a lot about their execution.
They shouldn't just be hit via a class action suit (assuming Lenovo isn't sticking a "binding arbitration" clause to defeat the ability for consumers to seek recourse) but Federal prosecution under one of the many computer security laws that would string up anyone else.
Honest question: is putting a backdoor/vulnerability into a product actually a crime in the US? As I understand it, most of the computer security laws are about actively breaking in ("gaining access"). The closest I can think of are contractual issues with sale ("fitness for purpose") and negligence, but both of those are civil.
I have a feeling this is less about recovering from damages and more about teaching them a formal lesson (well, cashing-in under the guise of teaching them a formal lesson).
That's the entire point of a class action suit. To stop powerful companies from doing a large number of small harms and getting away with it.
Ironically, awarding damages on an individual basis to the claimants would be far more punitive than whatever damages are awarded.
You assume it's necessary to show an ad before every video. If the video isn't long enough to insert an ad after, just don't show one until the next video has been viewed.
There hasn't, but I wouldn't expect it to matter. I don't believe the name is actually used anywhere (everyone just uses the version number), and its only defined in a makefile that's part of the kernel git repo. I'm not even sure if there's a rule for when it should be changed - I suspect it's merely whenever Linus feels like it.
For example, for the CPU it's common that I have more RAM than I can access at any one time at top speed.
No, no it isn't, and it hasn't been since the Amiga.
There is no PC where it is common to have different speeds of memory.
Maybe not on desktops, but it definitely exists in servers, where it's referred to as NUMA.
Not even today's Linux. How many distros actually have AppArmor/SELinux enabled?
The actual evidence is a little more mixed. From Wikipedia:
Most studies support a link between adult criminality and testosterone, although the relationship is modest if examined separately for each sex. Nearly all studies of juvenile delinquency and testosterone are not significant. Most studies have also found testosterone to be associated with behaviors or personality traits linked with criminality such as antisocial behavior and alcoholism. Many studies have also been done on the relationship between more general aggressive behavior/feelings and testosterone. About half the studies have found a relationship and about half no relationship.[72] ...
It has been empirically shown that boys who had a history of high physical aggression, from age 6 to 12, were found to have lower testosterone levels at age 13 compared with boys with no history of high physical aggression. The former were also failing in school and were unpopular with their peers. Both concurrent and longitudinal analyses indicate that testosterone levels were positively associated with social success rather than with physical aggression.[76]
-- http://en.wikipedia.org/wiki/T...
So, testosterone may be linked to antisocial behaviour, alcoholism and/or social success (in minors), but the jury is still out on aggression.
As a result of its questionable status with regard to copyright restrictions and other potential legal issues, the TrueCrypt License is not considered "free" by several major Linux distributions and is therefore not included in Debian, Ubuntu, Fedora, openSUSE, or Gentoo.
While this is true of the others, it is not true of Gentoo. Gentoo's policy seems to be that while the base system should not depend on non-FOSS components, having them present in the main tree is fine. (This might be partly because it's pretty easy to filter which licenses you want on your system using ACCEPT_LICENSE.)
Do you honestly think installing your own OS image is enough ? You can embed malware in the bios.
Would you like me to post a proof of concept ?
I won't buy a Lenovo after this incident. No way. Done.
You don't need to. Their business-grade lines (e.g. Thinkpads) include remote administration tools that basically let you do whatever you want to the laptop over Ethernet without turning it on. You can disable it in the BIOS/UEFI, but it's enabled by default.
Generics, as done in some languages, are excellent. Java is not one of those languages, primarily due to how it handles type erasure. Requiring the programmer to use an explicitly boxed type (Integer instead of int) is also rather clumsy, as is the lack of inference for type parameters.
IMO, C#'s implementation of generics is considerably better.
The other half is of course managed languages, but really slimming down C# to work on a RP doesn't seem impractical - just something that MS hasn't had a reason to focus on.
Or if you're impatient, you could just use D - the syntax is virtually identical to C#, but you get the performance of native code. I actually wrote some patches for buildroot a while back that added support for gdc, which make it pretty easy to compile a suitable toolchain for using D on a Raspberry Pi.
I frequently work with people who are terrified to touch anything related to kernel.
It's more than that - people (inexperienced developers in particular) are terrified to break outside of their encapsulated environment. They instinctively assume the standard libraries are flawless and bug-free, and that they don't have to worry about how they work, which is a useful approximation until that's no longer the case. The idea of looking at the source for said library to understand it better simply doesn't occur to them, or they overestimate its complexity. (To be fair, this is a view strongly encouraged by closed source software, which is a black box to even those interested in the internals.)
The kernel is different from userspace because it doesn't have the same protections and isolation. In userspace, (un)locking the wrong mutex gets you an exception with a nice message or a well defined error code. Do the same thing in the kernel and you get an oops with the stack trace pointing to a BUG_ON() assertion with some confusing looking code. It's the very opposite of the encapsulated environment presented by many userspace languages - misusing the mutex results in the developer being forced to look at the workings of it. Once you become used to that, your skill at working with complex systems develops rapidly.
It might be something a college student might be able to devote time and effort to. Obviously, it won't pay directly, but after graduating, being able to point to a module in the kernel with one's name on it is a good way to find jobs.
I'll second this. I'm a college* student who's currently picking up kernel programming for this exact reason. (Also, I find file system design interesting.) Whether or not it will help my employability remains to be seen, but it only takes the perception of utility to result in an increase in development.
* called university here
That's a terrible idea. It's not Ubuntu vs Mint vs Fedora, it's Ubuntu vs Debian vs Gentoo vs Arch - there's a massive spectrum of distros in terms of ease of use, stability, customizability, etc. There is no one size fits all solution - a rock solid production system is going to be completely different to a bleeding edge development system.
Separating distros from upstream projects is also important because the upstream projects rely on distros adopting their latest software at different times to maintain stability. Users of bleeding edge distros like Arch effectively test the software for users of more conservative distros like Debian.
It's also worth noting that Kubuntu is probably one of the worst KDE-based distros - IIRC, the 4.0 release mess was exacerbated by their maintainers configuring things poorly. And let's not forget that KDE is leaning towards using systemd internally... (I use systemd myself, but I think the idea of forcing it upon users is ludicrous.)
It would be fine if they were simply removing OC support on new cards. The problem is that they are removing a feature from a product that has already been sold, and even used as an advertising point by some manufacturers. This is no different to Sony removing OtherOS from the PS3.
It's poor style to not indent the inner for, because C family languages do allow one line for-statements, which the body is replaced by a single semi-colon. Someone skimming over the code could easily interpret it as such.
Wayland is a replacement for the X window server. (X is the software the sits between your graphics drivers and your desktop environment.) X is ancient at this point and has fundamental issues with its design that mean security issues which can't be fixed without breaking backward compatibility. X has a lot of features that it is required to support to maintain backward compatibility that no one uses any more - modern systems work by just pushing blocks of pixels to it. Wayland only supports this method of operation, so it's much simpler than X. Wayland's main developers are ex-X developers who are intimately familiar with the problem's X has (see Daniel Stone's talk on youtube for more info).
Wayland has been somewhat controversial because it does not have support for network transparency, unlike X. However, most modern apps don't use X in a network transparent way, and X network transparency is actually slower than VNC. The Wayland developers have advocated an approach similar to VNC for network transparency, but AFAIK there's no major implementation of it yet, so it remains controversial (even though almost no one is actually using it right now).