The hangover seems to come too late to reliably cause an aversive association to alcohol. One idea behind Antabus is that the negative reaction happens quickly enough to be useful. Of course, I'd expect it would also cause an aversive reaction to the medication as well.
Once one car in ten or so is self-driving they'll act as pace cars and effectively force you to drive at the same speed and with the same care as they do. And since they keep detailed recordings of everything happening around them, you will get the blame for any incident if you tried to push the limits at the time.
And at that point, driving yourself has become a dull, monotonous exercize in boredom. So you might as well join the ranks of non-drivers as well.
Where I live (Osaka city), all my train and subway use - a daily commute and weekend trips in the area - cost less altogether than just renting a parking space for a car would cost for the same period. Then you'd add actually buying a car, paying taxes and insurance, fuel, maintenance, highway tolls...
We take taxis whenever we're in a hurry or the train is inconvenient, and we still come out way ahead of driving ourselves. In fact, I haven't actually driven for more than a decade, and only keep my license since it's a convenient form of ID.
Dual citizenship can be an issue of course - that's the main reason I haven't considered naturalization - but to me that's really one of those things where reasonable people can disagree. There's perfectly good, valid argument both for and against dual nationality, and it really comes down to how you perceive citizenship as an institution. Japan is far from the only country that normally disallows it, by the way (there's a few rare exceptions where Japan allows it).
I don't think people can ever become stateless here, as the law expressly forbids that to happen. Children can have dual citizenship; if either of their parents are Japanese they automatically gain Japanese citizenship, even if they also gain another citizenship at the same time. They only have to choose and renounce one or the other when they become adults. But if they're born on Japanese soil and would become stateless (normally because their parents are) they also gain Japanese citizenship.
Have you tried to settle permanently in Japan and get the citizenship? It is almost impossible unless you have Japanese roots.
No, it's quite easy. I have permanent residency, and plenty of people do become Japanese citizens, without any "roots" to Japan other than what you develop by living here.
I'm a permanent resident in Japan. Getting a work visa was quite easy - much easier than what I've heard about others' experience getting one in the US - and permanent residence was pretty much painless as well. At every stage, the immigration officials were friendly and genuinely helpful.
Of course, each and every autonomous car is recording every second of the closest fifty meters at all times. You so much as hint at breaking the speed limit or breaking any other traffic rule, and a dozen cars will have you recorded with your bike license plate, position, time and speed down to a tenth of a kilometer.
Driving manually, whether a car or bike, is going to become very, very dull.
This is not a lifestyle I want to live. I can't imagine a future population truly being happy with this either.
It is a lifestyle I want*, and I suspect quite a lot of other people also want. And as the cost of a manual car go up; as you are stuck driving the same pace as all the strictly law-abiding autonomous cars; and as you stare out in traffic instead of surfing the web or throwing birds at pigs like the people in the cars around you, that lifestyle will appeal to more and more people who may not like it at first.
And soon you'll have a new generation of "drivers" that grew up with autonomous cars and used them when they were still too young to drive. Most of them will never see the point in spending a bunch of money and time learning how to drive manually. Once autonomous cars are out there, it will be only a matter of time until "driving" is an expensive, somewhat eccentric hobby you do mostly on a driving track.
* I already live that lifestyle in a way, as I don't have or need a car at all where I live. I only keep my license for use as an ID.
Not when the insurance companies artificially jack up the rates for human driven cars.
If humans are the cause of more accidents there's nothing artificial about it.
More realistically, I expect most people a generation from now will find the higher vehicle cost to be easily offset by not having to get a manual driving license, freeing up driving time, lower fuel consumption and using the car even when disabled, too young or otherwise not able to drive manually for whatever reason.
PLoS has had comments for a long time, and the result is - mostly no comments at all. I suspect the problem is that you're posting in your professional capacity, under your real name. That means you can really hurt your reputation with an off-hand comment; on the other hand, they count for nothing as far as your CV and employment prospects are concerned.
Posting a comment is really a losing proposition, with no upside (you can always contact the first author directly with questions) and potential downsides. So people, rationally, don't comment. Unless PubMed has figured out a way around it, I suspect this will be the end result this time around as well.
It's a real stretch to call a one-line proxy announcement that fits in the subject a "newsletter", though. It's quite the special case. The presentation he refers to was about a much more general situation with traditional, actual newsletters.
In his specific case he could put the information in the body of the email, thus forcing people to open it; or he could offer alternative delivery mechanisms through SMS or other channels alongside email for those that get caught out by spam filters.
You have a newsletter and problem being misfiled as spam? Put each new issue online (you probably do already) and offer an RSS feed with it. Some people greatly prefer RSS to a periodic email, and you can point people to it if they tell you the emails are getting blocked.
Osaka (where I live) and Tokyo both have multiple subway and local train systems, by multiple companies and none of them have chosen to lengthen or shorten sets in response to demand. Local and rapid trains may have different number of cars and the frequency will vary throughout the day but the set length is always the same. I guess the extra work and complexity is not worth it.
Many reasons. You may want to have a web cam, temperature station or other local data source connected to the net*. You may want to host a game server. A number of applications effectively act as servers even though they're really just applications in practice.
And at least where I am, you never pay per Mb for wired internet. I just pay an extra $10 (or thereabouts) per month to get a fixed IP address from my provider, and I can use it for anything non-commercial.
I agree the physical joystick has gotten the shaft lately (sorry). The binary stick, the analog stick and analog with feedback are all among the best devices ever invented for direct control. Ask any pilot of a current airplane or drone, and see if they'd not rather use a touchscreen or joypad.
Actually some people where opted out by default. I and others were opted in. There's no discernible pattern I can figure out for who was opt-in and who was opt-out. It does not depend on what you already agreed to previously, and it does not seem to depend on the jurisdiction where you live.
I find it hard to believe that our sciences are driving the math fields, as mature and well-developed as the math community is.
This has actually always been the norm. Physics has long driven mathematics research for instance; many areas of calculus were created/discovered specifically to solve problems in physics.
..is no big deal on things that look and act much like an X86 workstation. On big machines you frequently need to cross compile; the compiler/assembler/linker suite is not GCC or closely compatible; the system libraries are intended to be compatible these days but are separate implementations with their own quirks; and the environment is geared toward specific use so you lack many libs that are taken for granted in all-round systems.
I have installed Python on such a machine. It was a big deal and nothing I would ever attempt just to get a make-like utility working. It would be far less work to replace that utility with Make than to get Python onto the machine.
You may have heard it told, but I've tried it, and I disagree. What do you mean by "leave their original use-case"?
Sorry; I get a bit abridged at times. What I meant is that Make alternatives normally are born from a specific need. A group wants to build Java programs (for example) and come up with a tool that works better than Make for that.
But then it almost invariably (so far) turns out that the tool that works great for the original use case is lacking features, or lack flexibility, or has dependencies that make it unsuitable for very different kind of projects. Make-replacements that really are general enough to fully replace it are no easier to learn and use than Make itself. It seems for all its cruft and oddities, Make does seem to represent a floor in the complexity needed to support all the different situations you may encounter.
I have tried a number of alternatives over the years because I was frustrated with Autotools (which, rather than Make itself, is what people often really complain about). Finally, for one project I bit the bullet, got myself a book and really learned Autotools properly. And found out it's not bad at all, just unintuitive until you get a good explanation. There is some cruft there of course; but many oddities are due to the portable nature of the tools, and others are simply conventions that modern languages don't follow - they're not wrong, just different.
If you really want to replace make I suspect the best replacement would be - Make. That is, define an optional "new Make" mode that is not backwards compatible, with cleaned up syntax and parsing rules; the surface stuff that people get annoyed by.
..which is nice until you sit on a system without Python (go to big compute clusters and things like Python are suddenly scarce). Make is completely standalone; and the Autotoools look the way they do because, again, you can run them with minimal external dependencies.
As I heard it told, the reason Make (and Autotools) is the default despite all the suck is because all proposed alternatives suck more once you leave their original use-case.
Creating feedback points in space is cool of course, and will have a lot of uses. But I suspect the highest impact will be when applying a simpler version to ordinary 2D touch screens, and only at the screen surface.
We could finally have screen keyboards and games where you can find the buttons with your fingers, and where they actually give tactile feedback as you press them. Might be able to define surface textures for elements on screen, again making it much easier to use your phone or tablet without having to look at the screen at all times.
Whether you use this, a regular Arduino or whatever, you still need transistors, op-amps, resistors and so on to build the stuf it interfaces with. I think the possibilities you gain with an easy to program microcontroller actually makes regular electronics more powerful and more fun to play with as a result.
I've heard a number of people I trust comment on how the Moto X just feels really good in the hand and how the screen and size is just right. So the phone is certainly not bad at all, and most of us don't actually buy the high-end phones any more than we buy the high-end cars or bikes. A really good mid-range phone is exactly what I want; I'm already making calf-eyes toward the coming Sony Z1 Mini.
What's hurting Motorola for me, personally, is that it's simply not on sale in most of the world, and seems unlikely to ever be. It's not just about being able to get it where I live, but having a phone designed from the start to be usable in all major regions of the world as I travel.
So, make the benchmark software resemble the composite behaviour of common classes of apps. OGL benchmarks effectively act as the "typical" 3D game and so on.
At which point cheating becomes pointless, as any tweaking in favour of performance on those benchmarks immediately hit you as worse batterly life and high temps for all users running any similar kinds of apps, including your reviewers.
Slashdot Mirror
The hangover seems to come too late to reliably cause an aversive association to alcohol. One idea behind Antabus is that the negative reaction happens quickly enough to be useful. Of course, I'd expect it would also cause an aversive reaction to the medication as well.
"And how exactly does your living in an area with some of the best mass transit on the planet have ANYTHING to do with self-driving cars?"
It was a reply to the comment above mine. Not a reply to the story at large. We can do that, you know.
Once one car in ten or so is self-driving they'll act as pace cars and effectively force you to drive at the same speed and with the same care as they do. And since they keep detailed recordings of everything happening around them, you will get the blame for any incident if you tried to push the limits at the time.
And at that point, driving yourself has become a dull, monotonous exercize in boredom. So you might as well join the ranks of non-drivers as well.
Where I live (Osaka city), all my train and subway use - a daily commute and weekend trips in the area - cost less altogether than just renting a parking space for a car would cost for the same period. Then you'd add actually buying a car, paying taxes and insurance, fuel, maintenance, highway tolls...
We take taxis whenever we're in a hurry or the train is inconvenient, and we still come out way ahead of driving ourselves. In fact, I haven't actually driven for more than a decade, and only keep my license since it's a convenient form of ID.
Wouldn't be at all surprised if they do care just a little bit. making the orginal correct and your's not.
Dual citizenship can be an issue of course - that's the main reason I haven't considered naturalization - but to me that's really one of those things where reasonable people can disagree. There's perfectly good, valid argument both for and against dual nationality, and it really comes down to how you perceive citizenship as an institution. Japan is far from the only country that normally disallows it, by the way (there's a few rare exceptions where Japan allows it).
I don't think people can ever become stateless here, as the law expressly forbids that to happen. Children can have dual citizenship; if either of their parents are Japanese they automatically gain Japanese citizenship, even if they also gain another citizenship at the same time. They only have to choose and renounce one or the other when they become adults. But if they're born on Japanese soil and would become stateless (normally because their parents are) they also gain Japanese citizenship.
No, it's quite easy. I have permanent residency, and plenty of people do become Japanese citizens, without any "roots" to Japan other than what you develop by living here.
You might want to check this blog/information site about naturalization in Japan, written by a former US citizen whow is now Japanese: http://www.turning-japanese.info/ Specifically this post about naturalizing without being ethnically or racially japanese: http://www.turning-japanese.info/2013/03/does-one-get-japanese-citizenship-by.html
I'm a permanent resident in Japan. Getting a work visa was quite easy - much easier than what I've heard about others' experience getting one in the US - and permanent residence was pretty much painless as well. At every stage, the immigration officials were friendly and genuinely helpful.
Of course, each and every autonomous car is recording every second of the closest fifty meters at all times. You so much as hint at breaking the speed limit or breaking any other traffic rule, and a dozen cars will have you recorded with your bike license plate, position, time and speed down to a tenth of a kilometer.
Driving manually, whether a car or bike, is going to become very, very dull.
It is a lifestyle I want*, and I suspect quite a lot of other people also want. And as the cost of a manual car go up; as you are stuck driving the same pace as all the strictly law-abiding autonomous cars; and as you stare out in traffic instead of surfing the web or throwing birds at pigs like the people in the cars around you, that lifestyle will appeal to more and more people who may not like it at first.
And soon you'll have a new generation of "drivers" that grew up with autonomous cars and used them when they were still too young to drive. Most of them will never see the point in spending a bunch of money and time learning how to drive manually. Once autonomous cars are out there, it will be only a matter of time until "driving" is an expensive, somewhat eccentric hobby you do mostly on a driving track.
* I already live that lifestyle in a way, as I don't have or need a car at all where I live. I only keep my license for use as an ID.
If humans are the cause of more accidents there's nothing artificial about it.
More realistically, I expect most people a generation from now will find the higher vehicle cost to be easily offset by not having to get a manual driving license, freeing up driving time, lower fuel consumption and using the car even when disabled, too young or otherwise not able to drive manually for whatever reason.
PLoS has had comments for a long time, and the result is - mostly no comments at all. I suspect the problem is that you're posting in your professional capacity, under your real name. That means you can really hurt your reputation with an off-hand comment; on the other hand, they count for nothing as far as your CV and employment prospects are concerned.
Posting a comment is really a losing proposition, with no upside (you can always contact the first author directly with questions) and potential downsides. So people, rationally, don't comment. Unless PubMed has figured out a way around it, I suspect this will be the end result this time around as well.
It's a real stretch to call a one-line proxy announcement that fits in the subject a "newsletter", though. It's quite the special case. The presentation he refers to was about a much more general situation with traditional, actual newsletters.
In his specific case he could put the information in the body of the email, thus forcing people to open it; or he could offer alternative delivery mechanisms through SMS or other channels alongside email for those that get caught out by spam filters.
You have a newsletter and problem being misfiled as spam? Put each new issue online (you probably do already) and offer an RSS feed with it. Some people greatly prefer RSS to a periodic email, and you can point people to it if they tell you the emails are getting blocked.
Osaka (where I live) and Tokyo both have multiple subway and local train systems, by multiple companies and none of them have chosen to lengthen or shorten sets in response to demand. Local and rapid trains may have different number of cars and the frequency will vary throughout the day but the set length is always the same. I guess the extra work and complexity is not worth it.
Many reasons. You may want to have a web cam, temperature station or other local data source connected to the net*. You may want to host a game server. A number of applications effectively act as servers even though they're really just applications in practice.
And at least where I am, you never pay per Mb for wired internet. I just pay an extra $10 (or thereabouts) per month to get a fixed IP address from my provider, and I can use it for anything non-commercial.
* Why? For fun.
I agree the physical joystick has gotten the shaft lately (sorry). The binary stick, the analog stick and analog with feedback are all among the best devices ever invented for direct control. Ask any pilot of a current airplane or drone, and see if they'd not rather use a touchscreen or joypad.
Actually some people where opted out by default. I and others were opted in. There's no discernible pattern I can figure out for who was opt-in and who was opt-out. It does not depend on what you already agreed to previously, and it does not seem to depend on the jurisdiction where you live.
This has actually always been the norm. Physics has long driven mathematics research for instance; many areas of calculus were created/discovered specifically to solve problems in physics.
I have installed Python on such a machine. It was a big deal and nothing I would ever attempt just to get a make-like utility working. It would be far less work to replace that utility with Make than to get Python onto the machine.
Sorry; I get a bit abridged at times. What I meant is that Make alternatives normally are born from a specific need. A group wants to build Java programs (for example) and come up with a tool that works better than Make for that.
But then it almost invariably (so far) turns out that the tool that works great for the original use case is lacking features, or lack flexibility, or has dependencies that make it unsuitable for very different kind of projects. Make-replacements that really are general enough to fully replace it are no easier to learn and use than Make itself. It seems for all its cruft and oddities, Make does seem to represent a floor in the complexity needed to support all the different situations you may encounter.
I have tried a number of alternatives over the years because I was frustrated with Autotools (which, rather than Make itself, is what people often really complain about). Finally, for one project I bit the bullet, got myself a book and really learned Autotools properly. And found out it's not bad at all, just unintuitive until you get a good explanation. There is some cruft there of course; but many oddities are due to the portable nature of the tools, and others are simply conventions that modern languages don't follow - they're not wrong, just different.
If you really want to replace make I suspect the best replacement would be - Make. That is, define an optional "new Make" mode that is not backwards compatible, with cleaned up syntax and parsing rules; the surface stuff that people get annoyed by.
..which is nice until you sit on a system without Python (go to big compute clusters and things like Python are suddenly scarce). Make is completely standalone; and the Autotoools look the way they do because, again, you can run them with minimal external dependencies.
As I heard it told, the reason Make (and Autotools) is the default despite all the suck is because all proposed alternatives suck more once you leave their original use-case.
Creating feedback points in space is cool of course, and will have a lot of uses. But I suspect the highest impact will be when applying a simpler version to ordinary 2D touch screens, and only at the screen surface.
We could finally have screen keyboards and games where you can find the buttons with your fingers, and where they actually give tactile feedback as you press them. Might be able to define surface textures for elements on screen, again making it much easier to use your phone or tablet without having to look at the screen at all times.
Whether you use this, a regular Arduino or whatever, you still need transistors, op-amps, resistors and so on to build the stuf it interfaces with. I think the possibilities you gain with an easy to program microcontroller actually makes regular electronics more powerful and more fun to play with as a result.
I've heard a number of people I trust comment on how the Moto X just feels really good in the hand and how the screen and size is just right. So the phone is certainly not bad at all, and most of us don't actually buy the high-end phones any more than we buy the high-end cars or bikes. A really good mid-range phone is exactly what I want; I'm already making calf-eyes toward the coming Sony Z1 Mini.
What's hurting Motorola for me, personally, is that it's simply not on sale in most of the world, and seems unlikely to ever be. It's not just about being able to get it where I live, but having a phone designed from the start to be usable in all major regions of the world as I travel.
So, make the benchmark software resemble the composite behaviour of common classes of apps. OGL benchmarks effectively act as the "typical" 3D game and so on.
At which point cheating becomes pointless, as any tweaking in favour of performance on those benchmarks immediately hit you as worse batterly life and high temps for all users running any similar kinds of apps, including your reviewers.