Not content with smashing elementary subatomic particles, not content even with accelerating protons or lead ions, now they want to accelerate people, inside long evacuated tubes, to ridiculous speeds.
Living Across the Pond in rainy old England, this comes across as an April Fool 123 days late. But then suggestions in 2016 that Trump would win would also come across as April 1 jokes too.
I've often commented to friends that gradually banks will come up with a bank-authenticated blockchain system, where instead of requiring hundreds of gigawatts per day, the banks simply dictate a set of machines which are allowed to do the authenticating. The need for the computational pissing contest is the weak link of bitcoin. It's an interesting experiment, and something that should be seen and watched as just that: a financial, computational, and sociological experiment.
The law states that companies own whatever the recover from derelict space vessels; and since outer space is beyond the jurisdiction of national courts, like international waters are, any space vessel is fair game.
There will be new laws and treaties long before actual space mining starts happening.
The complaint is that if Flash is available, people will not migrate away. What needs to happen is for the source to be prepped for open sourcing, but held in escrow for a time until migration away from flash is largely complete. It is critical that an open source Flash does not compete with migration away from it. So migration away must be a prerequisite.
Being able to represent the sort of thing you'd use C or C++ for as a data structure within Python, and then turn into binary via LLVM is something I've been wishing for for a long time. I imagine I'll need to keep wishing for a while longer, but things like numba (in python), and application of LLVM like LLVMPipe, and the Synthesis OS project from a few years back suggest the pieces for doing this are gradually appearing.
It is best understood as a subsystem which emulates Linux from the point of view of software running on top of it. As for X support, what would be interesting is a naive Windows compositor for Wayland.
Reminds me of a religious conservative taking the age-at-death of a number of porn stars, taking its average, and comparing that with the average age-of-death in the US, totally oblivious to those pornstars who are still alive and the contribution of their ages-at-death, which are presently unknown.
From an epidemiology perspective, the 99% is, of course, useless. It's like saying that 99% of people who had terminal cancer died of cancer.
On the other hand, (and why the fuck isn't this angle being spelt out more??), you have a reasonable number of brains to look at, from which you can infer ways to recognise where the brain injuries come from, and use this to better understand how often these problems occur in general. For example the questions that should be asked are about what sort of tests can we come up with to detect this sort of brain injury sooner.
I had read about UNIX, had a fascination with it from the start of the 90s, first got to see it for real when I started university in 1995, and Slackware 3.0 appeared on the PCW April 1996 issue. (I think it was this issue and version: google isn't much help here, and neither is the rest of the web.)
Took me a week to work out rm deletes files. My usual solution to finding myself in vi was exiting via ctrl-z followed by jobs -l followed by kill -9. Until I'd learned rm and mv, if I created problems by creating a file, I'd reinstall. I figure out many things I could type by reinstalling and watching the package names. Learned the basics of TeX via a gentle introduction document, and basically taught myself by reverse engineering the gobbledigook one found in.sty packages. (I found out rm via a hint inferred from the openlook file manager asking 'do you want to remove this file', rather than 'delete' or 'erase', which were the two synonyms I knew from DOS. At first, the only UNIX command I knew was ls, since the UNIX column in PCW mentioned it somewhere. cd worked the same way as DOS, and from DOS I recalled that md and mkdir were synonyms, so tried md and mkdir and found the latter worked.)
In those days there were no online howtos (or at least, no easy way to even know such things existed, and no easy way to find out about ways to find stuff -- these were the days when some industry commentators were suggesting that Microsoft Network would make the internet obsolete:-)) ).
Microsoft Windows is a legal operating system you can run on your PC, but it is possible to install add-ons which permit the user to download pirated content. Indeed Microsoft Windows is the most popular platform amongst software and media pirates. In addition, Microsoft does essentially nothing to prevent its operating system being used for piracy.
Do less, but more reliably. Let spins like ubuntustudio or kubuntu add the packages. Have metapackages corresponding to them on the installer, with a simple choice (think of the chooser in Noobs), with some spins requiring a network connection. Have an install tab creator which lets you easily choose defaults.
Then have a very minimal default desktop and an easy way to choose bundles. Put GNOME and LXDE on the standard I so, use GNOME as the default choice. Put Firefox and chromium on as browsers by default. I generally have Firefox as default.
Those are my thoughts. For now I use ubuntustudio with a script and a tar of my usual convenience scripts (so install from iso, copy script and tarball over, run script as root, leave to simmer for 30 minutes, or until well cooked). I do have a big pile of cheap laptops, and the creative, writing and python stuff are what I want out of the box.
I've started exploring debootstrap. Being able to image a drive you can then stick in a machine is something I'd love.
If two top mathematicians are having a conversation, in English, about the ins and outs of, say, the latest greatest advancements in applying group cohomology to analytic number theory, consider the transcript that GCHQ/NSA would get from that phone call, and the difficulty in understanding it. Demanding that the phone company be able to decipher the language for them is stupid. Demanding that the phone company not offer the facility for people to communicate in languages that the phone company cannot decipher on behalf of GCHQ/NSA would be stupid, and kind of like madatory-1984-NewSpeak-on-steroids.
For one thing, it is too easy to write end-to-end encrypted messaging services. The _hard_ part of what things like WhatsApp do is to make it scalable to handle millions of concurrent users with the ease it does. Everyday people need this, but terrorists do not. An ad hoc end-to-end encryption system can be done in a few hundred lines of JS/PHP/HTML, using e.g. cryptojs. The result can be stuck at any url you like, temporarily, in such a way that there is no practical means to recover messages without the correct keys. (Basically a key-value store, where the key is produced by some kind of deterministic hashing method, as is the decryption key for the information stored there. Both the server end can easily break things up based on further hashing of the key, and likewise the client can break up messages into separate chunks, separately encrypted with keys produced by various salted hashes, such that you need to recover it all.)
Consider fire. Consider fire fighting, fire detection, and fire prevention.
There are many well known ways of using either heat, or presence of smoke in the air, to indicate a high likelihood that there is a fire in a region of a building. But these detection methods do not tell you anything about how the fire started. Combining information from many detectors across a large building can tell you about how a fire is spreading, but not about how a raging fire _might_ spread.
That people who have had some episodes labelled as 'schizophrenia' leaves common tell-tale signs detectable in this way is good to know, from a research point of view. But just like the 'fire analogies' above, where multiple similar looking fires, with similar results, can start in markedly different ways, the similar features in brains of people diagnosed with 'schizophrenia' only tell _part_ of the picture. As for how their brain came to be that way, such evidence can be likened to evidence that a fire in one room is a common cause of a fire in a neighbouring room. Things like 'chemical imbalances' are often touted as the 'cause' of things like bipolar disorder, or schizophrenia, rather than as a link in a causative chain. (This to me has always seemed as silly as saying that the pictures on your TV are _caused_ by electrical fluctuations in the aerial.)
In general, I think people working with mind and brain tend to overgeneralise, exaggerate, and oversell the consequences of their observations. This is further compounded when potential counter-evidence is 'defended against' and 'argued away', as happens between different factions of the mental health profession. People want things to be straightforward and simple, as if treating cuts and broken bones, and often inadvertently assume things are that simple before proceeding with studies whose results rely upon statistical reasoning which is contingent upon various assumptions uniformly holding across the population being studied... and then generally don't make clear their assumptions. People then read peer-reviewed research, and assuming a far simpler and more uniform picture than the evidence warrants.
A statement like 'laptop in classroom is worse' implicitly treats all classes as alike, considers it a simple either/or matter, and disregards things like teaching children how best to make use if a laptop, and habits so as to avoid depending on them unnecessarily. Assuming away the complex nature of a real world problem makes for meaningless results, no matter how widely headline grabbing they are.
Address them at the same time. Basically put in a solid right to repair with legal teeth, and then use that as a lever to require documentation and relevant source code to be made available. (Think of how constitutional rights have pushed things around in the US. An EU-wide 'constitutional right to repair' would be a major stepping stone, since the market is large enough to be worth it for a lot of companies.)
The solution to that is for a mastered track with good dynamic range have a corresponding 'gain adjustment info' file (basically bounce the audio before smashing the crap out if it with a compressor - then record what the final stage of compression does to it - using standardised and publicly known algorithms). A playback device could then easily give the overcompressed output.
I tried an OrangePiLite. The WiFi was unsupported, the Ethernet port was removed to make way for it, and USB Ethernet and WiFi adapters I tried did not work with the Linux images supplied. Not worth the time given Rpi's work.
Slashdot Mirror
Not content with smashing elementary subatomic particles, not content even with accelerating protons or lead ions, now they want to accelerate people, inside long evacuated tubes, to ridiculous speeds.
Is that ten years worth of 1080p porn in your pocket, or...
Living Across the Pond in rainy old England, this comes across as an April Fool 123 days late. But then suggestions in 2016 that Trump would win would also come across as April 1 jokes too.
This is why mainstream OSs are so prone to malware, why hack-prone WordPress is so popular. It may be true, but it is not a good thing.
So they are numbers written in a different notation than base 10 place-value. I mean, XXXIV clearly isn't a number.
I've often commented to friends that gradually banks will come up with a bank-authenticated blockchain system, where instead of requiring hundreds of gigawatts per day, the banks simply dictate a set of machines which are allowed to do the authenticating. The need for the computational pissing contest is the weak link of bitcoin. It's an interesting experiment, and something that should be seen and watched as just that: a financial, computational, and sociological experiment.
The law states that companies own whatever the recover from derelict space vessels; and since outer space is beyond the jurisdiction of national courts, like international waters are, any space vessel is fair game.
There will be new laws and treaties long before actual space mining starts happening.
The complaint is that if Flash is available, people will not migrate away. What needs to happen is for the source to be prepped for open sourcing, but held in escrow for a time until migration away from flash is largely complete. It is critical that an open source Flash does not compete with migration away from it. So migration away must be a prerequisite.
Being able to represent the sort of thing you'd use C or C++ for as a data structure within Python, and then turn into binary via LLVM is something I've been wishing for for a long time. I imagine I'll need to keep wishing for a while longer, but things like numba (in python), and application of LLVM like LLVMPipe, and the Synthesis OS project from a few years back suggest the pieces for doing this are gradually appearing.
It is best understood as a subsystem which emulates Linux from the point of view of software running on top of it. As for X support, what would be interesting is a naive Windows compositor for Wayland.
Reminds me of a religious conservative taking the age-at-death of a number of porn stars, taking its average, and comparing that with the average age-of-death in the US, totally oblivious to those pornstars who are still alive and the contribution of their ages-at-death, which are presently unknown.
From an epidemiology perspective, the 99% is, of course, useless. It's like saying that 99% of people who had terminal cancer died of cancer.
On the other hand, (and why the fuck isn't this angle being spelt out more??), you have a reasonable number of brains to look at, from which you can infer ways to recognise where the brain injuries come from, and use this to better understand how often these problems occur in general. For example the questions that should be asked are about what sort of tests can we come up with to detect this sort of brain injury sooner.
And weren't the Intel offerings a tad easier to fry?
Sure the difference between murder and manslaughter is one of intent to kill. But in both cases the outcome at hand is death of the victim.
The FTC's requirement may not have intended this effect, but it was forseeable, and avoidable.
I had read about UNIX, had a fascination with it from the start of the 90s, first got to see it for real when I started university in 1995, and Slackware 3.0 appeared on the PCW April 1996 issue. (I think it was this issue and version: google isn't much help here, and neither is the rest of the web.)
Took me a week to work out rm deletes files. My usual solution to finding myself in vi was exiting via ctrl-z followed by jobs -l followed by kill -9. Until I'd learned rm and mv, if I created problems by creating a file, I'd reinstall. I figure out many things I could type by reinstalling and watching the package names. Learned the basics of TeX via a gentle introduction document, and basically taught myself by reverse engineering the gobbledigook one found in .sty packages. (I found out rm via a hint inferred from the openlook file manager asking 'do you want to remove this file', rather than 'delete' or 'erase', which were the two synonyms I knew from DOS. At first, the only UNIX command I knew was ls, since the UNIX column in PCW mentioned it somewhere. cd worked the same way as DOS, and from DOS I recalled that md and mkdir were synonyms, so tried md and mkdir and found the latter worked.)
In those days there were no online howtos (or at least, no easy way to even know such things existed, and no easy way to find out about ways to find stuff -- these were the days when some industry commentators were suggesting that Microsoft Network would make the internet obsolete :-)) ).
Microsoft Windows is a legal operating system you can run on your PC, but it is possible to install add-ons which permit the user to download pirated content. Indeed Microsoft Windows is the most popular platform amongst software and media pirates. In addition, Microsoft does essentially nothing to prevent its operating system being used for piracy.
Do less, but more reliably. Let spins like ubuntustudio or kubuntu add the packages. Have metapackages corresponding to them on the installer, with a simple choice (think of the chooser in Noobs), with some spins requiring a network connection. Have an install tab creator which lets you easily choose defaults.
Then have a very minimal default desktop and an easy way to choose bundles. Put GNOME and LXDE on the standard I so, use GNOME as the default choice. Put Firefox and chromium on as browsers by default. I generally have Firefox as default.
Those are my thoughts. For now I use ubuntustudio with a script and a tar of my usual convenience scripts (so install from iso, copy script and tarball over, run script as root, leave to simmer for 30 minutes, or until well cooked). I do have a big pile of cheap laptops, and the creative, writing and python stuff are what I want out of the box.
I've started exploring debootstrap. Being able to image a drive you can then stick in a machine is something I'd love.
If two top mathematicians are having a conversation, in English, about the ins and outs of, say, the latest greatest advancements in applying group cohomology to analytic number theory, consider the transcript that GCHQ/NSA would get from that phone call, and the difficulty in understanding it. Demanding that the phone company be able to decipher the language for them is stupid. Demanding that the phone company not offer the facility for people to communicate in languages that the phone company cannot decipher on behalf of GCHQ/NSA would be stupid, and kind of like madatory-1984-NewSpeak-on-steroids.
For one thing, it is too easy to write end-to-end encrypted messaging services. The _hard_ part of what things like WhatsApp do is to make it scalable to handle millions of concurrent users with the ease it does. Everyday people need this, but terrorists do not. An ad hoc end-to-end encryption system can be done in a few hundred lines of JS/PHP/HTML, using e.g. cryptojs. The result can be stuck at any url you like, temporarily, in such a way that there is no practical means to recover messages without the correct keys. (Basically a key-value store, where the key is produced by some kind of deterministic hashing method, as is the decryption key for the information stored there. Both the server end can easily break things up based on further hashing of the key, and likewise the client can break up messages into separate chunks, separately encrypted with keys produced by various salted hashes, such that you need to recover it all.)
You're very welcome on my lawn. ;-)
Consider fire. Consider fire fighting, fire detection, and fire prevention.
There are many well known ways of using either heat, or presence of smoke in the air, to indicate a high likelihood that there is a fire in a region of a building. But these detection methods do not tell you anything about how the fire started. Combining information from many detectors across a large building can tell you about how a fire is spreading, but not about how a raging fire _might_ spread.
That people who have had some episodes labelled as 'schizophrenia' leaves common tell-tale signs detectable in this way is good to know, from a research point of view. But just like the 'fire analogies' above, where multiple similar looking fires, with similar results, can start in markedly different ways, the similar features in brains of people diagnosed with 'schizophrenia' only tell _part_ of the picture. As for how their brain came to be that way, such evidence can be likened to evidence that a fire in one room is a common cause of a fire in a neighbouring room. Things like 'chemical imbalances' are often touted as the 'cause' of things like bipolar disorder, or schizophrenia, rather than as a link in a causative chain. (This to me has always seemed as silly as saying that the pictures on your TV are _caused_ by electrical fluctuations in the aerial.)
In general, I think people working with mind and brain tend to overgeneralise, exaggerate, and oversell the consequences of their observations. This is further compounded when potential counter-evidence is 'defended against' and 'argued away', as happens between different factions of the mental health profession. People want things to be straightforward and simple, as if treating cuts and broken bones, and often inadvertently assume things are that simple before proceeding with studies whose results rely upon statistical reasoning which is contingent upon various assumptions uniformly holding across the population being studied... and then generally don't make clear their assumptions. People then read peer-reviewed research, and assuming a far simpler and more uniform picture than the evidence warrants.
This restricts cashless to businesses where money is taken first, or where card preauth is used.
A statement like 'laptop in classroom is worse' implicitly treats all classes as alike, considers it a simple either/or matter, and disregards things like teaching children how best to make use if a laptop, and habits so as to avoid depending on them unnecessarily. Assuming away the complex nature of a real world problem makes for meaningless results, no matter how widely headline grabbing they are.
Address them at the same time. Basically put in a solid right to repair with legal teeth, and then use that as a lever to require documentation and relevant source code to be made available. (Think of how constitutional rights have pushed things around in the US. An EU-wide 'constitutional right to repair' would be a major stepping stone, since the market is large enough to be worth it for a lot of companies.)
The solution to that is for a mastered track with good dynamic range have a corresponding 'gain adjustment info' file (basically bounce the audio before smashing the crap out if it with a compressor - then record what the final stage of compression does to it - using standardised and publicly known algorithms). A playback device could then easily give the overcompressed output.
I tried an OrangePiLite. The WiFi was unsupported, the Ethernet port was removed to make way for it, and USB Ethernet and WiFi adapters I tried did not work with the Linux images supplied. Not worth the time given Rpi's work.
You are very generous in assuming they give you good enough software for it to function. The OrangePi's taught me not to take this for granted.