Many such structures in densely-populated areas have large, flat, mostly-empty roofs. (Hell, some of the apartment buildings in my little urban area of ~40k people have flat roofs, as do most of the local dorms.)
4,726 karma · joined April 5, 2013
Many such structures in densely-populated areas have large, flat, mostly-empty roofs. (Hell, some of the apartment buildings in my little urban area of ~40k people have flat roofs, as do most of the local dorms.)
I was presenting an alternative on the assumption the government would anyway.
This is the same VP, by the way, that testified before the same committee in January on net neutrality.[2]
Are you suggesting he's lying to Congress?
Last year, Amazon hired for their Prime Air team, among other high-profile individuals, a former NASA astronaut, a Keyhole co-founder, and a mess of aerospace vets and MIT grads.[3]
Argue all you want about its viability, but this is not "a press release" or "april fool's joke".
[0] http://www.theguardian.com/technology/2015/mar/24/amazon-con...
[1] http://www.cbsnews.com/news/amazon-unveils-futuristic-plan-d...
[2] http://recode.net/2015/01/21/congress-still-bickering-over-n...
[3] http://techcrunch.com/2014/08/20/despite-faa-setbacks-amazon...
Can you come up with a concrete example of how such a court order might come about in a case that the government is intervening in in this manner?
> Similarly, if A is constantly harassing B, B should just shut up and take the money the government pays him in compensation, along with the harassment that isn't being stopped?
See above.
> Are you sure that is the outcome you are advocating for?
It's difficult to know, since these seem to have no relationship to any hypothetical case I can come up with.
You mean the drone delivery they're actively testing in the UK? The drone delivery they're fighting with the FAA about? The drone delivery they just testified before Congress about?
They're spending an awful lot of time, money, and political capital on something that makes no sense, will never happen, and was just a press release.
A switch to JSON-RPC 2.0 meant everyone now understood the entirety of the specifications our APIs relied on, and if we couldn't find a good implementation for our target, we could either fix one, or write one ourselves in just a few hours.
The productivity gain was effectively infinite.
I look at the JSON API specification in all its architecture astronaut glory, and weep.
A set of rules. Such rules are potentially eligible for patent protection. They are not eligible for copyright protection.
> On one hand you can say that games are not protected. Tetris however is. And has successfully been defended us such in court.
I suggest you read the actual text of the Mino decision, which rests heavily on visual elements, not gameplay. I also suggest you not put too much stock in the decision of a single district court judge. District court decisions are not binding precedent. Especially ones obviously written by a judge who either doesn't understand what the functional elements of a game are, or was looking for an excuse to find for Tetris.
> The layout and configuration of levels is not an idea.
Those would be assets.
This is long settled in US law. Things like art and text are copyrightable. The game itself is not.
I haven't bothered having anyone cut my hair in years, but yeah, people working at SuperCuts make crap, in much the same way and for the same reason that people working at McDonalds make crap.
ECMA-262 isn't really relevant at all, since it's not the (or even an) authority on JSON. JSON was simply derived from it -- in an incompatible way at that. It's doubly irrelevant since you were talking about Unix, so that's what I was addressing.
By the way, your phrasing is odd/confusing. You're talking about "epochs" in a strange way. In Unix/POSIX land, there is one epoch, "The time zero hours, zero minutes, zero seconds, on January 1, 1970 Coordinated Universal Time (UTC).". Unix timestamps are derived from the epoch, they do not define it.
I can't imagine what could lead you to think I'd be interested in "learning" from someone who clearly doesn't even understand what my claims/opinions are, but insists they're "ignorant" and "trolling".
What you've accomplished here is not to teach, but to harden my existing biases.
Just to be sure I didn't comment in my sleep, I went back and looked, and I see the word "meaningless" nowhere in my comments.
> But if you study, you find out they they have very specific meanings.
Some people have defined them in very specific ways. The description in the originally linked article is actually one of the ones I hate the least. That doesn't make it good, and doesn't make the terms useful.
> Calling C pointers "references" is just the tip of the misunderstanding iceberg.
What, precisely, will it take to convince you that I understand your position and simply disagree with it?
> But if you prefer to wander around in ignorance
Please stop being insulting.
ECMA-262 even explicitly uses 7159's predecessor (4627) with two exceptions[1], one of which is the top-level compatibility headache 7159 fixed, and the other just requires the API to disregard the "MAY" in section 4.
[0] https://www.tbray.org/ongoing/When/201x/2014/03/05/RFC7159-J...
[1] http://www.ecma-international.org/ecma-262/5.1/#sec-15.12
What conclusion would that be, exactly?
> your claim that pass-by-reference is meaningless
I didn't make that claim.
> and is also what Java does
I didn't make that claim, either. Nor would I ever. Stop putting words in my mouth.
If you don't understand how you're being insulting here, I can't help you.
> The JLS does define exactly what happens when parameters are passed...
Yes, it's very nice in that respect.
> And that happens to match the definition of pass-by-value/call-by-value exactly (even Java is listed as an example language for pass-by-value)
It happens to match the definition of "call-by-value" used by whoever wrote that blurb on Wikipedia you seem to love so much. The irony here, of course, is that people who like to use these terms don't even agree on how they're spelled...
None of this makes the terms useful.
http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_...
I assume you mean the JLS, in which case it -- very wisely -- does not use the term "pass-by-value" (or any similar term I've seen) to label its semantics. It simply describes its semantics.
> Read Wikipedia too. Or really any other real reference that isn't some confused people in a forum.)
So is it "most people" or a reference that, if anything, supports my point (JLS), an un-encyclopedia, and unspecified "real references" that aren't from people you enjoy insulting?
> That's what the article does.
That's one thing the article does, yes. Why is it you think you need to point that out?
> People in these forums who still don't get it need something more. That's what I'm giving them.
I agree you are giving people in this forum "something more". I suspect we disagree as to what that "something" is.
I am not confused, I disagree.
> In addition, pass-by-reference and pass-by-value are very useful terms for anyone interested in accurately speaking about and understanding what will happen when they run the program they write.
The terms would be useful if people agreed on their meaning (they do not) and if languages actually followed one way or the other consistently (they do not). That is the very reason this thread exists.
If you wish to accurately speak about what will happen, then speak about it. Describe what actually happens, instead of spending your time arguing about which round hole the square peg fits in better.
> There are people who consider accuracy and understanding to be pedantry.
In practice, pass-by-value and pass-by-reference provide neither accuracy nor understanding. Stop using them, and these arguments instantly vanish.
> More often than not, in my experience, they are a larger source of bugs than those who strive to truly understand how their tools work.
That I strive to truly understand how my tools work is the very reason I reject these terms as worthless.
(It's ironic, by the way, that in seeking to be more pedantic, you reference stacks. Stacks are not part of C.)
Edit: Actually, no, I don't think it's right. Modern chroma keying could probably handle this.