OT: in my experience, every time I participate in a thread and get highly modded (4 or 5) I then receive mod-points within a week or so. Briefly looking at your comments, you're not getting the original mods, so maybe you don't get the points? I've not checked out the source to see how slashcode handles this (is it part of the standard code distribution, or a customization for/. only?).
G+ fits my desire for social-networking perfectly: I hardly have to spend any time on it to get what I want out of it. I spend no time whatsoever on the other systems, because they're more cumbersome and demand my time in ways I'm not comfortable with. G+ is the only system that lets me contribute the little amount of time I'm willing to contribute, without being useless. So maybe its users *do* use it for fewer minutes a month -- but isn't that okay? Is there not a market for that? Lots of people probably watch crappy TV -- should we judge other channels based on the fact that they have a few, well-targeted shows, that a segment of the population watches (but nothing else)? Maybe it should be our goal to use these systems less, not more! In that respect, G+ represents an increase in efficiency -- which is a driver of GNP. So it's a good thing. Go G+!
So, if it rained on the blimp, would the water fall all the way through? When it flies through a cloud -- is the cloud really flying through the blimp?
My wife's family has a lot of Celiac disease going around. I can promise you that, as patients, they know far more about it than any of the general practitioners they visit (or, in one case, the specialists who went 30 years without properly diagnosing it), who probably haven't read about it since they had a few-minute lesson about it in medical school -- assuming they're young enough. The older ones, I've personally observed, tend to just nod wisely, then leave the room and go look it up. And that's something that (more or less) 1% of the population has -- I feel sorry for anyone with a rarer condition. The system of trusting doctors to somehow "know everything" and everyone else to "know nothing" can't work, the limits of our individual knowledge don't scale that way. (That said, it'd be a good start for doctors to acknowledge their own limits. As engineers, we're quite willing to look stuff up when we run across it, but I don't see that so often in the medical field. Is that the result of being told, right or wrong, that medical school was where they'd learn everything? An over-developed skepticism of anything they read? I really would like to know. Because it seems far too common to have doctors who don't take the time to learn and become experts in their patients' less-common conditions.)
The clinic I worked with (as programmer) once announced that they HAD to destroy records after 7 years. As I recall, HIPAA only required them to keep the records for at least that long -- not keep them then destroy them at 7 years + 1 day. But with that kind of misunderstanding, we can't trust our doctors' offices to be the keepers of our data.
Also, this isn't just about us keeping and reading our own data: it's also about making it easier to go from doctor to doctor. Sure, a hospital/ER might willingly give out data to patients -- but is it in a format that's easy to import at all other doctors' offices? No? Well damn. How does one doctor know what else you're seeing doctors for? You... tell them. In that painful intake form, that's hand-written, every time you come into the office. My sister went to the trouble of taking all her records from other doctors (painful to get) to a new doctor, only to have him dismiss all of it and start his diagnostic path from scratch. Why bother to read through someone else's notes? Pshaw! Just start over. No reason to save time by not repeating experiments, when a patient's well-being is on the line, and they came to you because previous stuff didn't work.
We should have our data. And we should be able to present it when we go to any doctor, to bring them instantly up to date on your history -- generally as a patient and specifically to the conditions you want treated.
The closest I've seen is this: vets' offices. Maybe it's thanks to a monopoly in the vet industry, but quite a few of the vets we've seen over the years (as we moved from state to state) used the same software. They could read the print-outs we brought from other vets' offices (we had to keep all that in a folder ourselves, nothing electronic) because it was in exactly the format they were used to. That's at least a step up.
France, by the way, uses (used?) a nationally-issued "carnet de sante" in which all your doctors would write their notes, at least for kids. Standard format, all vaccinations and other procedures and observations recorded, dated, with doctor information in case a phone call was necessary. And it was carried by the patient. I don't recall french doctors' office having large shelving units full of old patient data -- they relied on the patients themselves to bring that back in each time. And they took the time to re-read old notes, both from themselves and from other doctors. It IS doable.
Let's not forget that Siri uses Wolfram Alpha, though clearly not all of it (having tried them side by side.) That the two share some quirkiness isn't unexpected.
You know what? Just for you, I'll apologize. I assumed that, like kids these days, you didn't know the difference between those data-structures, and call everything a "hash table" when you mean, at best, "associative array", usually backed by a tree. [We've been interviewing recently, candidates haven't exactly been passing with flying colors.] Congrats on knowing your data and having an efficient solution to the specific problem. Pot and kettle are done, though.
How do you think that algorithm works, exactly? The reason it's efficient is because it's stored in an index (b-tree / red-black tree), which involves non-linear (though fast) insert operations. Whether you sort as you insert, or sort after inserting, it doesn't matter: it's not linear time. Also, your algorithm fails to consider hash collisions, unless you're doing extra processing on all "similar" items (multiset or multimap) to verify equality, not just equivalency. That algorithm would still involve quadratic/2 (no need to compare a vs. b and b vs. a) comparisons between hashes-to-same-value entries, though at least you'd only have to do it for the few collisions you come across.
Maybe if you had ever been forced to *implement* some of those containers, from scratch, you'd know how they work. Some of us actually had to do that, thank you very much. If you do ever come across an implementation of 'DISTINCT' that works on unindexed data in linear time, please let all the major database vendors know. They'll be *very* interested.
(Example: I found a quadratic algorithm used to deduplicate an arbitrary large table in there, when a hash-table, as available in the Java libraries, would do the job in linear time)
Err, no? You could gather the hashes in linear time, but you'd need to sort them to efficiently find the duplicates, and sorting isn't linear-time. It'd be faster than quadratic, yes, but let's not get carried away. Also, please don't pull data into memory in JAVA for this, if you can have the database do it.
Morale of that is that 100 incompetent people Moral.
Why is it OK for Google to steal their ideas and then give the resulting product away?
Misunderstanding of patents: you can acquire a patent even if you're not the inventor, and you can negotiate (without actually litigating) with it even if there exists prior art that would theoretically invalidate it on the basis of the cost of legal action; two people can invent the same thing independently without looking over each others' shoulders (it's quite common). The fact that company A has a patent for X, and company B does something resembling X, doesn't mean that B has, in any way, stolen from A. In fact, if you want to copy off of someone else's work, patents are possibly the most difficult way of going about it.
The companies involved have plenty of other sources of revenue with which to recoup the costs of developing technologies like the mouseless mouse click. Invalidating patents doesn't mean invalidating software licenses for entire software products, nor does it make hardware sales disappear. They'll be okay, I promise.
Patents were well-intentioned, but not designed to perform to expectations. They still don't protect small inventors. There's no useful definition of "reasonable" license fees. We're moving in the direction of first-to-file, which screws independent inventors who don't constantly troll the patent lists to see if their idea was previously patented.
Agreed. My reading is that the GP is narrowly correct: CSS can't "completely" reskin a site, because it depends on the underlying html which does have some structural semantics to it. XML data + XSL templates (possibly several, for different end-devices and/or user agents) + CSS would more closely fit his goals, but the XSLT approach wasn't nearly as widely publicized as CSS, so I don't completely blame him for missing that boat. Even today's popular toolkits encourage "backing pages" for data, but the layer above that is generally straight to html, not to XML for later transformation.
While Firebird supports update or insert, who else does? Yes, the merge syntax is common, but that's a lot more annoying to use for day-to-day single-row updates in an OLTP environment. Also, what does "agile" have to do with it? Or did you not mean it in the project-management sense?
I think you misunderstood. I'm talking about the hold that one person can have over another for an extended period of time. I'm not talking about a john -- I'm talking about the traffickers. It's the same relationship as black-mailing a politician, or having family back home in Mexico under constant threat, etc. There's no free market system that can make those pictures disappear from someone else's camera, there's no free-market police to protect your family. I see it like a "hold" or a "lock" (martial arts); if someone already has limited mobility [by our policies], it's much easier to trap them. The more freedoms we grant each other, the less likely someone is to get stuck in one of those positions. Yes, we should help each other out, too, but that doesn't excuse us for having created the situation in the first place.
If it's consenting and safe, who cares if the demand curve shifts? Who's talking of making it legal and acceptable for teenagers to be enslaved and raped? We have laws against exploitation of children, regardless of industry. (Well, almost. I don't get why farm and rail industries get so many exemptions from labor laws.) [Also, I could have used murder in my analogy, but didn't. So sorry. Trump you later?] You could go a long way to helping and encouraging people to use the justice system if you don't shame them and pursue them for what is their job either by choice, by circumstance, or by force, if you didn't mis-use the justice system's resources pursuing the wrong crimes. Society has a weird feedback loop where if we make something illegal, we by extension make it morally wrong, rather than the other way around. So before they can get help from their friends, family, and society at large, you have to change the law, to change the attitudes.
Selling sex for money can be victimless, even if the "prostitution system" isn't. But why can women (and men!) be exploited? It's generally because there's some other reason: a) lack of justice system to protect them: as long as the cops are out arresting johns and prostitutes, instead of traffickers, we have a problem. b) drugs: by making them illegal, we drive up the price, drive the users into the arms of sellers, drive the addicted underground, and make them slaves of the drug lords -- we're driving them away. c) trafficking: has a lot to do with immigration, international politics and global economics; we need to work on the poverty problems around the world, and maintain open-border immigration policies, so our labor/market can resolve itself, without driving people to do insane things like sell their bodies to traffickers in the hope of a better life down the road -- only to be unable to break free for fear of being thrown out of the country, or worse, have their family thrown out.
The problems you see with prostitution are the symptoms that accompany any illegal activity: all illegal activities tend to get conglomerated under a single umbrella organization (mafia, etc.) because they have the contacts, they have the know-how, they have the experience to run all those businesses, cross-monetize, etc. You make money from trafficking someone across the border, then you make money from getting them hooked on drugs, then you make money selling their services...
Making a single point in the system illegal doesn't solve the overall problem. Making things legal actually solves more, besides agreeing with basic human rights of self-determination.
When prostitution becomes legalized in an area, demand outstrips supply, prices go up enough that traffickers move in [...]
This would be as opposed to when it's illegal, thus the supply of legal services = 0, so traffickers *necessarily* move in? How is that better? And really, that's like saying that we shouldn't allow poor people near rich people, because when the demand gets high enough, there will be theft -- as if we, as a society, had never invented a justice system to deal with these situations, where a demand exists that shouldn't be supplied. As long as prostitution is illegal, those who are *not* consenting cannot make good use of the justice system to protect themselves.
Thank you. I kept scrolling, hoping someone would already have brought this up. What happened to polluting the sea, smog, acid rain, cancer, asthma? What happened to sustainability, fairness? The shift to a debate over "global warming," which can be argued for decades, has co-opted what should have been plainly obvious discussion of environmental policy.
I believe the standard response, after 9/11, was "if you don't like it, you can move to France." That is, even if laws are federal, people will just be told to switch countries instead of states. It's not a solution, it's just a retort. Your argument seems like it would recommend open borders, freedom of immigration and emigration. (Emigration is rather easy, but if nobody will accept you, it's pointless.) If the people of Mexico don't like it down there, why shouldn't they move here? Oh, wait, because we don't want to let them in! Why not? We're not afraid of migration between states because there's little incentive to move -- only minor differences, thus minor sloshing about. If we have more variety, I expect states will setup barriers to entry, as we have at the national level, because that's what we do when we start having places that are "this way" vs. "that way". We start to want to keep people out who might want to make changes inside our sacred place, people who could skew our votes and cause us to need to leave and setup a new place. And so forth for all eternity, as we run away from each other. Hurray?
If you're going to go down this path, how about something more clean: any group of people, at any point, can essentially secede from the union, take their land, and make a new country/state/whatever, with their own laws. Why should "states" be sacred? Why should you obey the laws of your own country, when you didn't decide to live here in the first place? Your citizenship (by birth) in this country doesn't guarantee you the right to change citizenship at 18, so you're essentially a prisoner anyway. You should have a right to form your own country, inside the boundaries of this one, and cut ties! If we're going to slosh about, let's do it joyously.
You mention NY City, but provide no argumentation on why the Federal government should give up power specifically to the State, and not to Cities, etc. I still argue you're making arbitrary distinctions. I'm sure you'd leave some powers at the Federal level, but so far the only argument I see is that the Constitution says so, or that we should amend the Constitution -- but how do we do that, other than through our current process? If 51% of us (at the national level) are okay with that power staying with the Federal government, then you have no way of achieving State power. You have to have the power before you can get the power.
To be clear: I'm not arguing against individuals having more say, or reducing government, or whatever -- I just don't understand the fascination with *state* rights.
But that still doesn't answer why the State is the ideal layer for this to happen. It's arbitrary. Sure, we can quote the Constitution, or bring up the Founding Fathers, to justify doing things "by the book", but why? Just because that's the way some dead guys designed the system? Including dead guys who felt they had very little right to tell the next generation how to run the show? So then it just becomes an argument about either doing things by the book, or rewriting the book. Which is fine and dandy, but it doesn't speak to the issue of *why*. Why can't I make prostitution illegal on my plot of land? Ultimately, shouldn't I be able to decide? And I'm sure anti-abortionists would feel that banning it in some states, and not in others, is akin to having slavery in the state next door: morally unjustifiable. We clearly recognize that there are basic human rights -- and some less obvious -- that deserve upholding both here and abroad. We don't consider murder in Somalia acceptable just because there's no functioning government to decide that it's wrong -- we're unlikely to be okay with morality issues varying much at all across state (or county) boundaries. We're uncomfortable with them varying across national boundaries as it is.
Yes, variety is great. But people don't make decisions purely on one factor. You're not going to create a state to put all the republicans in, because it'll satisfy their political desires -- because ultimately, they decide where to live based on politics, religion, family, jobs, landscape, weather, friends, history, culture. You can't create enough buckets to make everyone, or even most, or likely even some, people happy. As it is, clearly, people don't move just because of economic choices -- the south would be empty by now. Clearly, people don't move because of pollution or overpopulation, the north-east would be empty. They don't move because of housing prices, the west would be empty. They don't move because of legalization, the west would be even fuller. The whole "if you don't like it, you can move" argument fails the reality test. People only move when they HAVE to. They move when their governments start shooting them -- and even then, not everyone does. They move when famine sets in -- and even then, not everyone does.
We need to find solutions that don't require removing people from their current geographical area.
All power to the Counties! All power to the Cities! All power to the neighborhoods!
What is the deal with States, that they're so awesome? Maybe it's because I live in Oklahoma at the moment, but I'm just not seeing it. When we talk about mobility, you have to remember that the reason it's relatively (not absolutely, by a long shot) easy to pick up and move between states is that there's a certain amount of standardization provided by the federal government. Even something as simple as "states must recognize marriages from other states" makes a huge difference in where people could/would move for a job, for economic reasons. And it just goes up from there.
Also, do you really think the people of Missouri have sufficiently different needs and wants from the people of Oklahoma, that they need different laws? Maybe Utah does, and Texas just needs it for its ego, but really? We're all humans [for now], we're all potential works and employers. You might argue that when economic trouble hits, different regions need different economic policies applied because of local industry variations, but that's not prevented by the federal government; it already doles out money to various industries selectively, affecting regions differently. We decry the International Criminal Court as a violation of our sovereignty, we despise super-national unions like the EU, but really we're just drawing arbitrary lines in the sand. This far, and no further.
Are some states "red" and others "blue"? Maybe, but does that mean that we need states that are right next to each other, with either a 49/51 or 51/49 ratio, to be run entirely differently? Do you think that the resulting "sloshing", as people move out of their current states to escape overly-partisan policies, is good for us in the long term? Do you think polarizing our populations even more will solve our problems?
I realize this is about ideology, whether you believe that we are generally smarter or dumber as a group than as an individual. And I think that it's both, depending on the issue. Maybe we're smarter individually when running a small business, but we're dumber when it comes to planning health insurance, the military, etc. All of that is debatable, and actively debated, and that's healthy. I guess we could just split the union. Two countries. One centralized, one completely decentralized. Tear families apart. Break our economy. Increase tensions. Lose power in the world. And then split again, when each side disagrees on how much centralization is good.
States' rights sound awesome, but what would you *do* with that power and granularity, that can't or shouldn't be done at a higher or lower level?
Exactly. I wrote a custom plugin for intranet-only use, to be deployed in the enterprise; I set to it allow up to 4.x, thinking that was plenty, and I hadn't seen anything in 4 beta that would break it. And then 5 comes along, and the plugin won't run. Now I have to go to the effort of changing it, signing, deploying, waiting for that to update everywhere, etc. to fix the problem. Why? No good reason. None. It should work fine in 5.x, which is really 4.x with tiny goodies, we just assumed that another big version # change should also require thorough testing, whenever that happened, if ever. I'm pretty sure this one doesn't. Nor will 6.x, 7.x, or 19.x. I was thinking next time of setting the upper bound to 99.x, because that'll last me, what, a year? Yay! Stupid. If you want to call your browser "Firefox 23", go for it. But internally, please let plugins still see "4.3.21", so they can make good decisions about compatibility. Maybe even assign version numbers to various chunks of the code: chrome, DOM, utilities, etc. so a plugin can detect API changes to a given section? Don't up the major version unless you remove or seriously change existing API's in that section.
Slashdot Mirror
OT: in my experience, every time I participate in a thread and get highly modded (4 or 5) I then receive mod-points within a week or so. Briefly looking at your comments, you're not getting the original mods, so maybe you don't get the points? I've not checked out the source to see how slashcode handles this (is it part of the standard code distribution, or a customization for /. only?).
G+ fits my desire for social-networking perfectly: I hardly have to spend any time on it to get what I want out of it. I spend no time whatsoever on the other systems, because they're more cumbersome and demand my time in ways I'm not comfortable with. G+ is the only system that lets me contribute the little amount of time I'm willing to contribute, without being useless. So maybe its users *do* use it for fewer minutes a month -- but isn't that okay? Is there not a market for that? Lots of people probably watch crappy TV -- should we judge other channels based on the fact that they have a few, well-targeted shows, that a segment of the population watches (but nothing else)? Maybe it should be our goal to use these systems less, not more! In that respect, G+ represents an increase in efficiency -- which is a driver of GNP. So it's a good thing. Go G+!
Spoiler alert: Deus ex machina, and he's back in business again by the end of the movie. Doesn't get the girl, though.
So, if it rained on the blimp, would the water fall all the way through? When it flies through a cloud -- is the cloud really flying through the blimp?
My wife's family has a lot of Celiac disease going around. I can promise you that, as patients, they know far more about it than any of the general practitioners they visit (or, in one case, the specialists who went 30 years without properly diagnosing it), who probably haven't read about it since they had a few-minute lesson about it in medical school -- assuming they're young enough. The older ones, I've personally observed, tend to just nod wisely, then leave the room and go look it up. And that's something that (more or less) 1% of the population has -- I feel sorry for anyone with a rarer condition. The system of trusting doctors to somehow "know everything" and everyone else to "know nothing" can't work, the limits of our individual knowledge don't scale that way. (That said, it'd be a good start for doctors to acknowledge their own limits. As engineers, we're quite willing to look stuff up when we run across it, but I don't see that so often in the medical field. Is that the result of being told, right or wrong, that medical school was where they'd learn everything? An over-developed skepticism of anything they read? I really would like to know. Because it seems far too common to have doctors who don't take the time to learn and become experts in their patients' less-common conditions.)
The clinic I worked with (as programmer) once announced that they HAD to destroy records after 7 years. As I recall, HIPAA only required them to keep the records for at least that long -- not keep them then destroy them at 7 years + 1 day. But with that kind of misunderstanding, we can't trust our doctors' offices to be the keepers of our data.
Also, this isn't just about us keeping and reading our own data: it's also about making it easier to go from doctor to doctor. Sure, a hospital/ER might willingly give out data to patients -- but is it in a format that's easy to import at all other doctors' offices? No? Well damn. How does one doctor know what else you're seeing doctors for? You ... tell them. In that painful intake form, that's hand-written, every time you come into the office. My sister went to the trouble of taking all her records from other doctors (painful to get) to a new doctor, only to have him dismiss all of it and start his diagnostic path from scratch. Why bother to read through someone else's notes? Pshaw! Just start over. No reason to save time by not repeating experiments, when a patient's well-being is on the line, and they came to you because previous stuff didn't work.
We should have our data. And we should be able to present it when we go to any doctor, to bring them instantly up to date on your history -- generally as a patient and specifically to the conditions you want treated.
The closest I've seen is this: vets' offices. Maybe it's thanks to a monopoly in the vet industry, but quite a few of the vets we've seen over the years (as we moved from state to state) used the same software. They could read the print-outs we brought from other vets' offices (we had to keep all that in a folder ourselves, nothing electronic) because it was in exactly the format they were used to. That's at least a step up.
France, by the way, uses (used?) a nationally-issued "carnet de sante" in which all your doctors would write their notes, at least for kids. Standard format, all vaccinations and other procedures and observations recorded, dated, with doctor information in case a phone call was necessary. And it was carried by the patient. I don't recall french doctors' office having large shelving units full of old patient data -- they relied on the patients themselves to bring that back in each time. And they took the time to re-read old notes, both from themselves and from other doctors. It IS doable.
Let's not forget that Siri uses Wolfram Alpha, though clearly not all of it (having tried them side by side.) That the two share some quirkiness isn't unexpected.
You know what? Just for you, I'll apologize. I assumed that, like kids these days, you didn't know the difference between those data-structures, and call everything a "hash table" when you mean, at best, "associative array", usually backed by a tree. [We've been interviewing recently, candidates haven't exactly been passing with flying colors.] Congrats on knowing your data and having an efficient solution to the specific problem. Pot and kettle are done, though.
"If you find something is already in the hash"
How do you think that algorithm works, exactly? The reason it's efficient is because it's stored in an index (b-tree / red-black tree), which involves non-linear (though fast) insert operations. Whether you sort as you insert, or sort after inserting, it doesn't matter: it's not linear time. Also, your algorithm fails to consider hash collisions, unless you're doing extra processing on all "similar" items (multiset or multimap) to verify equality, not just equivalency. That algorithm would still involve quadratic/2 (no need to compare a vs. b and b vs. a) comparisons between hashes-to-same-value entries, though at least you'd only have to do it for the few collisions you come across.
Maybe if you had ever been forced to *implement* some of those containers, from scratch, you'd know how they work. Some of us actually had to do that, thank you very much. If you do ever come across an implementation of 'DISTINCT' that works on unindexed data in linear time, please let all the major database vendors know. They'll be *very* interested.
5. Goto 1.
Wait, I think I found the *real* problem ...
(Example: I found a quadratic algorithm used to deduplicate an arbitrary large table in there, when a hash-table, as available in the Java libraries, would do the job in linear time)
Err, no? You could gather the hashes in linear time, but you'd need to sort them to efficiently find the duplicates, and sorting isn't linear-time. It'd be faster than quadratic, yes, but let's not get carried away. Also, please don't pull data into memory in JAVA for this, if you can have the database do it.
Morale of that is that 100 incompetent people
Moral.
[evidence needed]
[citation needed]
[explicitly stated allegations needed]
[ad hominem needs review]
Why is it OK for Google to steal their ideas and then give the resulting product away?
Misunderstanding of patents: you can acquire a patent even if you're not the inventor, and you can negotiate (without actually litigating) with it even if there exists prior art that would theoretically invalidate it on the basis of the cost of legal action; two people can invent the same thing independently without looking over each others' shoulders (it's quite common). The fact that company A has a patent for X, and company B does something resembling X, doesn't mean that B has, in any way, stolen from A. In fact, if you want to copy off of someone else's work, patents are possibly the most difficult way of going about it.
The companies involved have plenty of other sources of revenue with which to recoup the costs of developing technologies like the mouseless mouse click. Invalidating patents doesn't mean invalidating software licenses for entire software products, nor does it make hardware sales disappear. They'll be okay, I promise.
Patents were well-intentioned, but not designed to perform to expectations. They still don't protect small inventors. There's no useful definition of "reasonable" license fees. We're moving in the direction of first-to-file, which screws independent inventors who don't constantly troll the patent lists to see if their idea was previously patented.
Agreed. My reading is that the GP is narrowly correct: CSS can't "completely" reskin a site, because it depends on the underlying html which does have some structural semantics to it. XML data + XSL templates (possibly several, for different end-devices and/or user agents) + CSS would more closely fit his goals, but the XSLT approach wasn't nearly as widely publicized as CSS, so I don't completely blame him for missing that boat. Even today's popular toolkits encourage "backing pages" for data, but the layer above that is generally straight to html, not to XML for later transformation.
While Firebird supports update or insert, who else does? Yes, the merge syntax is common, but that's a lot more annoying to use for day-to-day single-row updates in an OLTP environment. Also, what does "agile" have to do with it? Or did you not mean it in the project-management sense?
That's a lot like the PL/SQL-compatible variant of Firebird, called Fyracle, which is still based on Firebird 1.5, not the current 2.1 or 2.5 series.
I think you misunderstood. I'm talking about the hold that one person can have over another for an extended period of time. I'm not talking about a john -- I'm talking about the traffickers. It's the same relationship as black-mailing a politician, or having family back home in Mexico under constant threat, etc. There's no free market system that can make those pictures disappear from someone else's camera, there's no free-market police to protect your family. I see it like a "hold" or a "lock" (martial arts); if someone already has limited mobility [by our policies], it's much easier to trap them. The more freedoms we grant each other, the less likely someone is to get stuck in one of those positions. Yes, we should help each other out, too, but that doesn't excuse us for having created the situation in the first place.
If it's consenting and safe, who cares if the demand curve shifts?
Who's talking of making it legal and acceptable for teenagers to be enslaved and raped? We have laws against exploitation of children, regardless of industry. (Well, almost. I don't get why farm and rail industries get so many exemptions from labor laws.) [Also, I could have used murder in my analogy, but didn't. So sorry. Trump you later?]
You could go a long way to helping and encouraging people to use the justice system if you don't shame them and pursue them for what is their job either by choice, by circumstance, or by force, if you didn't mis-use the justice system's resources pursuing the wrong crimes. Society has a weird feedback loop where if we make something illegal, we by extension make it morally wrong, rather than the other way around. So before they can get help from their friends, family, and society at large, you have to change the law, to change the attitudes.
Selling sex for money can be victimless, even if the "prostitution system" isn't. But why can women (and men!) be exploited? It's generally because there's some other reason:
a) lack of justice system to protect them: as long as the cops are out arresting johns and prostitutes, instead of traffickers, we have a problem.
b) drugs: by making them illegal, we drive up the price, drive the users into the arms of sellers, drive the addicted underground, and make them slaves of the drug lords -- we're driving them away.
c) trafficking: has a lot to do with immigration, international politics and global economics; we need to work on the poverty problems around the world, and maintain open-border immigration policies, so our labor/market can resolve itself, without driving people to do insane things like sell their bodies to traffickers in the hope of a better life down the road -- only to be unable to break free for fear of being thrown out of the country, or worse, have their family thrown out.
The problems you see with prostitution are the symptoms that accompany any illegal activity: all illegal activities tend to get conglomerated under a single umbrella organization (mafia, etc.) because they have the contacts, they have the know-how, they have the experience to run all those businesses, cross-monetize, etc. You make money from trafficking someone across the border, then you make money from getting them hooked on drugs, then you make money selling their services...
Making a single point in the system illegal doesn't solve the overall problem. Making things legal actually solves more, besides agreeing with basic human rights of self-determination.
When prostitution becomes legalized in an area, demand outstrips supply, prices go up enough that traffickers move in [...]
This would be as opposed to when it's illegal, thus the supply of legal services = 0, so traffickers *necessarily* move in? How is that better? And really, that's like saying that we shouldn't allow poor people near rich people, because when the demand gets high enough, there will be theft -- as if we, as a society, had never invented a justice system to deal with these situations, where a demand exists that shouldn't be supplied. As long as prostitution is illegal, those who are *not* consenting cannot make good use of the justice system to protect themselves.
Thank you. I kept scrolling, hoping someone would already have brought this up. What happened to polluting the sea, smog, acid rain, cancer, asthma? What happened to sustainability, fairness? The shift to a debate over "global warming," which can be argued for decades, has co-opted what should have been plainly obvious discussion of environmental policy.
I believe the standard response, after 9/11, was "if you don't like it, you can move to France." That is, even if laws are federal, people will just be told to switch countries instead of states. It's not a solution, it's just a retort. Your argument seems like it would recommend open borders, freedom of immigration and emigration. (Emigration is rather easy, but if nobody will accept you, it's pointless.) If the people of Mexico don't like it down there, why shouldn't they move here? Oh, wait, because we don't want to let them in! Why not? We're not afraid of migration between states because there's little incentive to move -- only minor differences, thus minor sloshing about. If we have more variety, I expect states will setup barriers to entry, as we have at the national level, because that's what we do when we start having places that are "this way" vs. "that way". We start to want to keep people out who might want to make changes inside our sacred place, people who could skew our votes and cause us to need to leave and setup a new place. And so forth for all eternity, as we run away from each other. Hurray?
If you're going to go down this path, how about something more clean: any group of people, at any point, can essentially secede from the union, take their land, and make a new country/state/whatever, with their own laws. Why should "states" be sacred? Why should you obey the laws of your own country, when you didn't decide to live here in the first place? Your citizenship (by birth) in this country doesn't guarantee you the right to change citizenship at 18, so you're essentially a prisoner anyway. You should have a right to form your own country, inside the boundaries of this one, and cut ties! If we're going to slosh about, let's do it joyously.
You mention NY City, but provide no argumentation on why the Federal government should give up power specifically to the State, and not to Cities, etc. I still argue you're making arbitrary distinctions. I'm sure you'd leave some powers at the Federal level, but so far the only argument I see is that the Constitution says so, or that we should amend the Constitution -- but how do we do that, other than through our current process? If 51% of us (at the national level) are okay with that power staying with the Federal government, then you have no way of achieving State power. You have to have the power before you can get the power.
To be clear: I'm not arguing against individuals having more say, or reducing government, or whatever -- I just don't understand the fascination with *state* rights.
But that still doesn't answer why the State is the ideal layer for this to happen. It's arbitrary. Sure, we can quote the Constitution, or bring up the Founding Fathers, to justify doing things "by the book", but why? Just because that's the way some dead guys designed the system? Including dead guys who felt they had very little right to tell the next generation how to run the show? So then it just becomes an argument about either doing things by the book, or rewriting the book. Which is fine and dandy, but it doesn't speak to the issue of *why*. Why can't I make prostitution illegal on my plot of land? Ultimately, shouldn't I be able to decide? And I'm sure anti-abortionists would feel that banning it in some states, and not in others, is akin to having slavery in the state next door: morally unjustifiable. We clearly recognize that there are basic human rights -- and some less obvious -- that deserve upholding both here and abroad. We don't consider murder in Somalia acceptable just because there's no functioning government to decide that it's wrong -- we're unlikely to be okay with morality issues varying much at all across state (or county) boundaries. We're uncomfortable with them varying across national boundaries as it is.
Yes, variety is great. But people don't make decisions purely on one factor. You're not going to create a state to put all the republicans in, because it'll satisfy their political desires -- because ultimately, they decide where to live based on politics, religion, family, jobs, landscape, weather, friends, history, culture. You can't create enough buckets to make everyone, or even most, or likely even some, people happy. As it is, clearly, people don't move just because of economic choices -- the south would be empty by now. Clearly, people don't move because of pollution or overpopulation, the north-east would be empty. They don't move because of housing prices, the west would be empty. They don't move because of legalization, the west would be even fuller. The whole "if you don't like it, you can move" argument fails the reality test. People only move when they HAVE to. They move when their governments start shooting them -- and even then, not everyone does. They move when famine sets in -- and even then, not everyone does.
We need to find solutions that don't require removing people from their current geographical area.
All power to the Counties! All power to the Cities! All power to the neighborhoods!
What is the deal with States, that they're so awesome? Maybe it's because I live in Oklahoma at the moment, but I'm just not seeing it. When we talk about mobility, you have to remember that the reason it's relatively (not absolutely, by a long shot) easy to pick up and move between states is that there's a certain amount of standardization provided by the federal government. Even something as simple as "states must recognize marriages from other states" makes a huge difference in where people could/would move for a job, for economic reasons. And it just goes up from there.
Also, do you really think the people of Missouri have sufficiently different needs and wants from the people of Oklahoma, that they need different laws? Maybe Utah does, and Texas just needs it for its ego, but really? We're all humans [for now], we're all potential works and employers. You might argue that when economic trouble hits, different regions need different economic policies applied because of local industry variations, but that's not prevented by the federal government; it already doles out money to various industries selectively, affecting regions differently. We decry the International Criminal Court as a violation of our sovereignty, we despise super-national unions like the EU, but really we're just drawing arbitrary lines in the sand. This far, and no further.
Are some states "red" and others "blue"? Maybe, but does that mean that we need states that are right next to each other, with either a 49/51 or 51/49 ratio, to be run entirely differently? Do you think that the resulting "sloshing", as people move out of their current states to escape overly-partisan policies, is good for us in the long term? Do you think polarizing our populations even more will solve our problems?
I realize this is about ideology, whether you believe that we are generally smarter or dumber as a group than as an individual. And I think that it's both, depending on the issue. Maybe we're smarter individually when running a small business, but we're dumber when it comes to planning health insurance, the military, etc. All of that is debatable, and actively debated, and that's healthy. I guess we could just split the union. Two countries. One centralized, one completely decentralized. Tear families apart. Break our economy. Increase tensions. Lose power in the world. And then split again, when each side disagrees on how much centralization is good.
States' rights sound awesome, but what would you *do* with that power and granularity, that can't or shouldn't be done at a higher or lower level?
Exactly. I wrote a custom plugin for intranet-only use, to be deployed in the enterprise; I set to it allow up to 4.x, thinking that was plenty, and I hadn't seen anything in 4 beta that would break it. And then 5 comes along, and the plugin won't run. Now I have to go to the effort of changing it, signing, deploying, waiting for that to update everywhere, etc. to fix the problem. Why? No good reason. None. It should work fine in 5.x, which is really 4.x with tiny goodies, we just assumed that another big version # change should also require thorough testing, whenever that happened, if ever. I'm pretty sure this one doesn't. Nor will 6.x, 7.x, or 19.x. I was thinking next time of setting the upper bound to 99.x, because that'll last me, what, a year? Yay!
Stupid.
If you want to call your browser "Firefox 23", go for it. But internally, please let plugins still see "4.3.21", so they can make good decisions about compatibility. Maybe even assign version numbers to various chunks of the code: chrome, DOM, utilities, etc. so a plugin can detect API changes to a given section? Don't up the major version unless you remove or seriously change existing API's in that section.