It wasn't actually a crime. Federal law "requires" it, but not carrying your documentation on you is not a federal criminal offense. The usual practice, if you forgot your green card at home, is that the officer just follows you home while you get it. They don't charge you with a crime.
Technically yes, but those requirements usually aren't strictly enforced. I don't usually carry my passport on my person in foreign countries, because it greatly increases the risk of it being damaged/lost/stolen. Especially if you go to the beach; are you supposed to take it swimming with you, or leave it unprotected under a beach umbrella? I've never heard of tourists being arrested for that, either, at least in relatively sane western countries. If you get stopped for some reason and tell the policeman that your passport is back in the safe at your hotel, they'll either just take your word for it, or follow you back to your hotel to get it. They won't charge you with a criminal not-carrying-passport offense, because that would be stupid.
And in the U.S., permanent residents typically aren't hassled, at least until now. Officially a green-card holder needs to carry their green card with them, but in practice this has never really been enforced in an onerous way. My mom was a permanent resident for decades before eventually getting around to getting citizenship, and I don't think she was ever asked to show her green card outside of circumstances where it was clearly necessary, like upon reentry into the U.S., I-9 employment verification, or other such bureaucratic stuff. She certainly didn't carry it while jogging.
Yeah, but the fixes are different. If it's a technically sound format with bad documentation, the fix is to write better documentation. But if the format itself has significant technical shortcomings, just documenting it better isn't a fix.
Weird Al generally gets the permission of the copyright owners before recording his versions. There have been some dust-ups where artists were annoyed at having their songs Weird-Al-ified without their permission, but in those cases it turned out that their labels had given permission without telling them. See his FAQ.
Ah yeah, I was assuming salaried (exempt) employees, which is the norm for office jobs that involve routine use of computers; though I suppose there are some hourly-wage data-entry jobs.
There are some cases where hourly workers can have their pay docked, but even then, as the site you link to says, only if "caused by the employee's gross negligence, or dishonest or willful act." And the bar for gross negligence is fairly high, not just anything that could have been prevented if the employee had been more careful.
It's illegal to dock employees' pay for damage to the employer's property.
For accidental damage, employees have no liability at all: It's considered the employer's responsibility to manage its workplace in a way that minimizes accidental damage, and any that does occur is considered a cost of doing business. Viruses routinely appearing on company machines, especially if it happens to many employees' machines, is probably in that category.
For damage done intentionally or through serious negligence, the employee may be responsible, but the employer still cannot dock their pay; they must sue the employee to recover the damages, and must prove by a preponderance of the evidence that the damage was inflicted intentionally or negligently.
Well, in California selling lost property is equivalent to selling stolen property under certain conditions, mostly depending on whether the person who found it made reasonable efforts to return it to the owner first.
It's a different kind of flaw, though. Rullgard was arguing that Ogg is inherently technically flawed. Arguing that it's technically fine but unusable due to a lack of documentation is a different argument.
They make pretty good hardware, too. The ergonomic keyboards occupy a nice optimum on the price/quality curve: much better than the cheapo stuff, but not the absurd $200 boutique stuff either.
Yeah... the resolution and daylight visibility beats e-paper, too. When it's something I don't have to pay too much close attention to, I sometimes print out 2 pages per side, i.e. 4 pages per physical sheet of paper. And that is still more readable to me than, say, a Kindle, especially for papers formatted like academic papers. On occasion I've even done 4-per-side, and it's readable.
Oddly, one feature Bing beats Google on is that its API has a much more generous license, allowing you to use results in non-user-facing apps like scripts; to reorder or filter results or mix them with results from other sources; etc. Google's API only allows you to republish its results, unchanged, within a user-facing app, basically nothing much more complicated than including a "Google results for this term" sidebar.
Which makes it even less believable as an "internet addiction" study, and more like, "if you cut people off from the world, they feel cut off from the world".
Great examples, thanks! It's something I think about periodically, which seems to relate to different kinds of steady states. There are some things that, at any reasonable point in the future, we can expect to recreate if we need to. But there are other things that are very dependent on the precise current conditions, which sounds uncomfortably chaotic. If you take "what 100 smart people could recreate in a year if they had to" as our safe fall-back position, there's increasingly a really large gap between the current state-of-the-art and that safe fallback.
It does feel weirdly like living on borrowed time, though. It's something that, apparently, nobody can make anymore, but you can straggle on because at some point in the past they made a whole lot of them.
How hard is it to actually operate an obsolete system with something vaguely like the original parts? It's in an awkward gap: too obsolete for modern mass-production to be willing to sell you, yet too complicated for you to DIY it. This makes for an odd gap of basically unmaintainable infrastructure. If you want to maintain infrastructure based on pen, paper, and the abacus, you're good. And if you want to stay on the current state-of-the-art for technology (or within a few years of it), you're also good.
But there's this weird gap in between. What if you want to play Nintendo games on a CRT fed by an RF adapter? Better either stock up on a bunch of legacy parts that were made before they stopped mass-producing them; or: find some way to ramp up your DIY tech to be able to produce that level of part; or: manage to implement something close enough in software so that your emulator is good enough.
There's some uncertainty over the level of ash that poses a significant threat, though. What's known is that zero ash is fine, and a lot of ash causes significant damage, but not too much seems to be known about the concentration/response curve beyond that.
Of course, it's also pretty clear that Branson is angling for a handout here, not really deeply interested in science or public policy. He has a pretty big self-interest in convincing people that the cause of the shutdown was government overreaction, in which case the government should compensate the airlines; rather than having people believe that the shutdown was a necessary reaction to the volcanic eruption.
That's one of the major flaws of the transition plan: not making IPv6 addresses just a superset of IPv4 addresses. If they had, legacy IPv4 systems would still be reachable from IPv6 systems, just not vice-versa, and everyone would automatically be upgraded to "on IPv6" as soon as their OS's protocol stack and applications were upgraded.
No, the economic implications have nothing to do with the science.
I don't think that's entirely true. If a lot of money is riding on a prediction, the concerns are different than if it's less immediately important whether a particular hypothesis is correct or not. The risk/loss functions differ, so how you should go about procuring/evaluating evidence differs. Unless you think the scientific method is exempt from decision theory?
The fact that you can build your own of something doesn't mean that the company that controls most of the market isn't a monopoly. By your definition, nobody should've been whining about Microsoft having a monopoly, because you could always install Linux.
Slashdot Mirror
It wasn't actually a crime. Federal law "requires" it, but not carrying your documentation on you is not a federal criminal offense. The usual practice, if you forgot your green card at home, is that the officer just follows you home while you get it. They don't charge you with a crime.
Technically yes, but those requirements usually aren't strictly enforced. I don't usually carry my passport on my person in foreign countries, because it greatly increases the risk of it being damaged/lost/stolen. Especially if you go to the beach; are you supposed to take it swimming with you, or leave it unprotected under a beach umbrella? I've never heard of tourists being arrested for that, either, at least in relatively sane western countries. If you get stopped for some reason and tell the policeman that your passport is back in the safe at your hotel, they'll either just take your word for it, or follow you back to your hotel to get it. They won't charge you with a criminal not-carrying-passport offense, because that would be stupid.
And in the U.S., permanent residents typically aren't hassled, at least until now. Officially a green-card holder needs to carry their green card with them, but in practice this has never really been enforced in an onerous way. My mom was a permanent resident for decades before eventually getting around to getting citizenship, and I don't think she was ever asked to show her green card outside of circumstances where it was clearly necessary, like upon reentry into the U.S., I-9 employment verification, or other such bureaucratic stuff. She certainly didn't carry it while jogging.
Yeah, but the fixes are different. If it's a technically sound format with bad documentation, the fix is to write better documentation. But if the format itself has significant technical shortcomings, just documenting it better isn't a fix.
True if you're hourly, but not allowed for salaried employees even if they agreed to it (because salaries aren't allowed to have conditions).
Weird Al generally gets the permission of the copyright owners before recording his versions. There have been some dust-ups where artists were annoyed at having their songs Weird-Al-ified without their permission, but in those cases it turned out that their labels had given permission without telling them. See his FAQ.
Ah yeah, I was assuming salaried (exempt) employees, which is the norm for office jobs that involve routine use of computers; though I suppose there are some hourly-wage data-entry jobs.
There are some cases where hourly workers can have their pay docked, but even then, as the site you link to says, only if "caused by the employee's gross negligence, or dishonest or willful act." And the bar for gross negligence is fairly high, not just anything that could have been prevented if the employee had been more careful.
It's illegal to dock employees' pay for damage to the employer's property.
For accidental damage, employees have no liability at all: It's considered the employer's responsibility to manage its workplace in a way that minimizes accidental damage, and any that does occur is considered a cost of doing business. Viruses routinely appearing on company machines, especially if it happens to many employees' machines, is probably in that category.
For damage done intentionally or through serious negligence, the employee may be responsible, but the employer still cannot dock their pay; they must sue the employee to recover the damages, and must prove by a preponderance of the evidence that the damage was inflicted intentionally or negligently.
Well, in California selling lost property is equivalent to selling stolen property under certain conditions, mostly depending on whether the person who found it made reasonable efforts to return it to the owner first.
It's a different kind of flaw, though. Rullgard was arguing that Ogg is inherently technically flawed. Arguing that it's technically fine but unusable due to a lack of documentation is a different argument.
The fact that the Supreme Court took the case suggests that it isn't black-letter law, doesn't it?
Not a fan of evolution by natural selection, eh?
They make pretty good hardware, too. The ergonomic keyboards occupy a nice optimum on the price/quality curve: much better than the cheapo stuff, but not the absurd $200 boutique stuff either.
Yeah... the resolution and daylight visibility beats e-paper, too. When it's something I don't have to pay too much close attention to, I sometimes print out 2 pages per side, i.e. 4 pages per physical sheet of paper. And that is still more readable to me than, say, a Kindle, especially for papers formatted like academic papers. On occasion I've even done 4-per-side, and it's readable.
Oddly, one feature Bing beats Google on is that its API has a much more generous license, allowing you to use results in non-user-facing apps like scripts; to reorder or filter results or mix them with results from other sources; etc. Google's API only allows you to republish its results, unchanged, within a user-facing app, basically nothing much more complicated than including a "Google results for this term" sidebar.
Which makes it even less believable as an "internet addiction" study, and more like, "if you cut people off from the world, they feel cut off from the world".
Next up: old people addicted to bingo night.
Great examples, thanks! It's something I think about periodically, which seems to relate to different kinds of steady states. There are some things that, at any reasonable point in the future, we can expect to recreate if we need to. But there are other things that are very dependent on the precise current conditions, which sounds uncomfortably chaotic. If you take "what 100 smart people could recreate in a year if they had to" as our safe fall-back position, there's increasingly a really large gap between the current state-of-the-art and that safe fallback.
It does feel weirdly like living on borrowed time, though. It's something that, apparently, nobody can make anymore, but you can straggle on because at some point in the past they made a whole lot of them.
exactly three, but that three is, at the same time, only one
Kill me once, shame on you. Kill me twice... can't get killed again.
How hard is it to actually operate an obsolete system with something vaguely like the original parts? It's in an awkward gap: too obsolete for modern mass-production to be willing to sell you, yet too complicated for you to DIY it. This makes for an odd gap of basically unmaintainable infrastructure. If you want to maintain infrastructure based on pen, paper, and the abacus, you're good. And if you want to stay on the current state-of-the-art for technology (or within a few years of it), you're also good.
But there's this weird gap in between. What if you want to play Nintendo games on a CRT fed by an RF adapter? Better either stock up on a bunch of legacy parts that were made before they stopped mass-producing them; or: find some way to ramp up your DIY tech to be able to produce that level of part; or: manage to implement something close enough in software so that your emulator is good enough.
Oddly, modern jet engines are generally okay dealing with sand. The fine silica particles in volcanic ash seem to pose much more of a problem.
There's some uncertainty over the level of ash that poses a significant threat, though. What's known is that zero ash is fine, and a lot of ash causes significant damage, but not too much seems to be known about the concentration/response curve beyond that.
Of course, it's also pretty clear that Branson is angling for a handout here, not really deeply interested in science or public policy. He has a pretty big self-interest in convincing people that the cause of the shutdown was government overreaction, in which case the government should compensate the airlines; rather than having people believe that the shutdown was a necessary reaction to the volcanic eruption.
That's one of the major flaws of the transition plan: not making IPv6 addresses just a superset of IPv4 addresses. If they had, legacy IPv4 systems would still be reachable from IPv6 systems, just not vice-versa, and everyone would automatically be upgraded to "on IPv6" as soon as their OS's protocol stack and applications were upgraded.
I don't think that's entirely true. If a lot of money is riding on a prediction, the concerns are different than if it's less immediately important whether a particular hypothesis is correct or not. The risk/loss functions differ, so how you should go about procuring/evaluating evidence differs. Unless you think the scientific method is exempt from decision theory?
The fact that you can build your own of something doesn't mean that the company that controls most of the market isn't a monopoly. By your definition, nobody should've been whining about Microsoft having a monopoly, because you could always install Linux.