Comment Re:Exactly. (Score 1) 318
Thanks for the correction, chum...p.
Thanks for the correction, chum...p.
It's not an entitlement. The difference is "having a right" versus "being willing to pay".
I don't have a right to have anyone perform for me, but I certainly can decide whether or not I'm willing to pay for a performance. If the available performances don't match my expectations, they may not make a sale. They are not entitled to my purchase.
I can access it just fine, all you need is access to AC's computer.
coded themselves into such a place that most maintenance issues have an automated solution already in place
It's like the Tooth Fairy, Loch Ness Monster, and Jesus all revealed themselves at once.
Everything is a "spike". Done.
In my experience, user-facing software is much harder to break into sprints than architecture and infrastructure.
I think there's some truth to what you're saying, but it's overly simplistic. Rights and technology are orthogonal. The record is hardly a progression of the powerful using new technologies to trample our rights; it's hardly the opposite either. Rights are demanded, and taken, by threat of loss of legitimacy for the powerful who refuse us those rights; they're lost when that threat is unsupportable. It may be that technology and disparity of power have advanced to the point that that threat is empty now, in which case your point is spot on. But I don't think we've reached that point. Yet.
I will say that the all is lost attitude isn't helping though.
If you call me on the phone, and the police asks me what you said, I can tell them. I don't know what rights I have to refuse to tell them if I don't want to, but you have no right to stop me if I decide to tell them.
And you wonder why I never call anymore.
Would the government need a warrant to compel your mother to turn over all the letters she's sent to you over the years, so they can retro-actively track your location in an attempt to link you to crimes?
Hell to the yes.
'broadcasting' in the tech sense, yes, but NOT in the usual PUBLIC SENSE. convenient that you leave that part out.
[... other stuff...]
Broadcasting can't be said to be being done in any one particular sense. It's broadcasting, PERIOD. Your cellphone, when operating in normal, customary mode, (not off, or in airplane mode, etc.,) is sending out a radio signal identifying itself to cell towers; without cellphones doing this, the cellular telephone system wouldn't work.
While I won't bother getting in the middle of the rest of the dispute, you're making a technical argument about a legal, non-technical distinction. I can see how you'd make that mistake, because the context also makes some technical claims. But let's be clear: in legal terms, "broadcast" (sending data over radio waves) is not the same as "broadcast" (making content available to an audience). Writing an email on the bus doesn't give the riders permission to read its contents, just as downloading a song does not constitute a public performance.
This is an important distinction.
if the cops came to my door and asked if I've seen a guy around the neighborhood with such-and-such description, I'm pretty sure I'd give them a prompt and truthful answer.
Because you think that's the morally appropriate choice? Or for some other reason(s)?
Any person with sufficiently sensitive equipment can essentially intercept any transmission, and discover a whole lot that isn't an explicit transmission. By this logic, we cannot legally expect to defend any form of privacy once it is compromised. That certainly appears to be the realpolitik, but it doesn't have to be accepted or defended. It certainly isn't justified by the fact that sound and light waves can be perceived by ears and eyes.
You've more or less described almost every functional programming language. And many of them, quite old, are gaining in popularity well past their introduction, in no small part because functional programming turns out to be well suited for parallel computing (and therefore to distributed computing and multiple processor cores). It should not be surprising to hear more about languages like Erlang (1986) and Haskell (1990), or to see new functional languages introduced going forward.
I would have read the rest of your comment, but you're obviously playing a terrible game of telephone. Every language is parsed. Java is a compiled (not interpreted) language.
Turns out that's a reasonable expectation. http://arstechnica.com/gaming/...
"Ninety percent of baseball is half mental." -- Yogi Berra