1,470 karma · joined February 16, 2012
Say what you want about enterprise software but Oracle is a beast... if you work for a company willing to shell out for it. That cost will seem sillier though Postgres closes the feature gap.
> That's frowned on in real estate.
...which is ironic to me, since both agents are incentivized towards the exact same outcome: the property changing hands.Even if it were hidden from the public, it's fairly straightforward to reason that it is stored in a database and that at least one employee has read-access to that database. I would be more fascinated to learn that no DraftKings or FanDuel employee ever played DFS without at least looking at their own ownership data.
> "for humans"
The earliest example of this that I could find is from a 2007 article by Jeff Atwood entitled "Sorting for Humans : Natural Sort Order". Coincidentally, Atwood double-dipped on it a few months later with an article called "Monkeypatching for Humans" (but I think he meant "monkey" in a different way).I think in recent years, Kenneth Reitz has really taken "for humans" and run with it: "Python for Humans", "Deployment for Humans", "requests: HTTP for Humans". He's even gone so far as to (facetiously?) trademark it ("args: Argument Parsing for Humans™"). Now everything with syntactic sugar is "for humans".
If you think your API represents a breakthrough in simplicity then trust me: it will do the talking for you.
Is this one of the reasons people use Java? Is it way wrong to say Docker is like a JVM for non-Java?
> Why should Forbes wait for comment, when Spotify didn't wait for their users?
That's like asking "why shouldn't Forbes stab their users in the face when Spotify shits on their users chests?"In other words, I don't think he's saying Forbes did Spotify dirty, rather Forbes did wrong by their readers by publishing a story without investigating it first.
If John Deere is only willing to sell lifetime licenses to operate their vehicles, thus putting the farmer at risk in ways like you described, why do farmers still buy these "licenses"?
Naively, they must represent some advantage (despite their shortcomings), otherwise John Deere wouldn't be able to sell these things.
r
.db('dragonball')
.table('characters')
.filter(function(row){
return row('maxStrength').gt(700000).and(row('species').contains('Saiyan'));
})
.orderBy(r.desc('maxStrength'));
presumably returns one row per character, whereas SELECT c.*
FROM characters c
INNER JOIN character_species cs ON c.id = cs.character_id
INNER JOIN species s ON cs.species_id = s.id
WHERE max_strength > 700000
AND s.name = 'Saiyan'
ORDER BY max_strength DESC;
returns at least one row per character. Rather, the equivalent SQL (depending on what syntax is available) might be: SELECT c.*
FROM characters c
WHERE max_strength > 700000
AND EXISTS (SELECT NULL
FROM character_species cs
INNER JOIN species s ON cs.species_id = s.id
WHERE c.id = cs.character_id
AND s.name = 'Saiyan')
ORDER BY max_strength DESC;
The above returns one row per character, no matter how many matching entries there are in `character_species` or `species`.Pursuing this a little further then, suppose you wanted to expand your search to include humans and androids. In SQL, only a slight modification is needed:
SELECT c.*
FROM characters c
WHERE max_strength > 700000
AND EXISTS (SELECT NULL
FROM character_species cs
INNER JOIN species s ON cs.species_id = s.id
WHERE c.id = cs.character_id
AND s.name IN ('Saiyan', 'Human', 'Android'))
ORDER BY max_strength DESC;
I shudder to think what that would look like in functional form. Something like this? r
.db('dragonball')
.table('characters')
.filter(function(row){
return row('maxStrength').gt(700000).and(row('species').contains('Saiyan')).or(row('species').contains('Human')).or(row('species').contains('Android'));
})
.orderBy(r.desc('maxStrength'));
But how would it know how to group the disjunctions?In my very limited experience, examples like these always look so tantalizing until you start taking them a little further and then you quickly realize there's no such thing as a free lunch. In this case, you pay for the flexibility of RethinkDB with the expressiveness SQL.
> We will send you a 128-bit encrypted HTTPS link via SMS that you can click to enter your credit card number. We do not store your credit card number. All payment processing is handled by Stripe.
What if one of your operators sends me a link to pay them instead and I never get what I asked for?Also, for something people are wary is a scam, saying "be careful what you wish for" in your first reply is a little bit ominous!
> Any chance Boston Dynamics will adopt a don't be evil policy?
Actually, Boston Dynamics is a wholly owned subsidiary of Google Inc. > I'll pick an animal -> dragons are the coolest animal -> nobody will ever guess dragon, this is way better than using my dog's name.
I must confess, this is typically my exact thought process when crafting a password, a username, or even sometimes a nickname for people to call me in real life.Maybe I'm just being pedantic but I don't think a poll about how people would vote for the president is a good indicator of how people feel about atheists in comparison to other groups of people. I don't even think the latter is quantifiable.
I'm a little amused by you guys trying to work out all the "PR" angles Cook could be trying to exploit by mentioning his faith without even considering that it's is a genuinely important part of who he is.
First of all, the frequency of shots near the basket so overwhelms that of shots anywhere else that the hexbins away from the basket end up being so minuscule that they're barely visible. So there must be some kind of frequency capping or logarithmic scaling somewhere in his charts. This is not the most egregious "lie" in his charts but it hides an interesting truth: 70% of shots are taken from 30% of the half-court (I'm making those numbers up but you get the idea.)
Secondly, I found that a player's (or even a team's) eFG% varies so much from bin to bin that you rarely get smooth color patterns like the ones that show up in his charts. His charts show orangered hexbins close to the basket that somewhat evenly and predictably get lighter and yellower as distance from the basket increases. But in practice, this is nearly impossible. Each hexbin would have to span hundreds if not thousands of shots--much more than an entire season's worth of data for a single player--for a pattern like that to appear. To me, this is almost deceitful because it tells a "story" that isn't there. eFG% is much more "random" than his charts depict. A player might go 10/20 from one location and 5/30 from the one directly adjacent.
> I believe the idea that these technologies is alienating is false.
You know, there's one side to "alienating" where the world shuts you out. But I think it's fair to say when people talk about headphones or Google Glass, they also mean you shutting out the world. You're describing a scenario where headphones basically make it harder for people to interact with you (correct me if I'm wrong), or make it easier for you to avoid that interaction. So I think these people are right in their sentiment that it makes the ocean between us a little deeper and wider but maybe the use of the word "alienating" is not quite right.Does that make sense?
No, you just stood on the sideline and waited for somebody to fail so you could come down off your branch and peck at the corpse.
Indeed, there is a lesson here. Don't expect anybody to pat you on the back when you put it all on black and win. Because, sure as shit, they'll be there to kick it in your face when you lose.
First of all, as others mentioned, your personal machine runs on Windows so right off the bat there goes your instant virtualenv, pip install.
Even on the Unix app server, you're probably behind a firewall that's tight as a duck's ass so chances are you're downloading the tar ball and making the package yourself.
Third, wtf are you doing littering the app server with all these binaries? And what is Python? I'm sorry, no, rewrite this in Java, please.
If you do manage to convince your manager and the rest of your team that Python is not black magic, the first time numpy breaks or some small issue crops up or you have to migrate to a new server and reinstall numpy but now there's a new version and... GTFO of here with that black magic.
I agree with you, developing websites on your MacBook Pro there's no excuse not being able to install numpy. In the real world though, having basic necessities in stdlib does absolute wonders.
But how can that be?! Building a large scale application with Perl would be like building a F111A Aardvark out of duct tape! Quite simply, because Perl is the perfect duct tape. Too many people (knowingly or not) think of Perl as a crappy version of Python when it's actually shell scripting on steroids.
You see, way up here, where projects are constantly in development, paradigms are constantly shifting, and people are building new and exciting things, Perl is an unwelcome high school acquaintance who shows up at the party and makes everybody feel awkward and bad. But way down there, where people are just trying to keep Sputnik up and running until the Soviet Union collapses, Perl is a rock star! If it's too "small" for Java but too "large" for .ksh -- guess what, use Perl.
In my opinion, if you want a scripting language with function signatures, little to no support for UNIX commands, real object orientation (Moose), yadda yadda yadda... just use Python. No one's going to blame you. Larry Wall's not gonna feel bad. You have a right to your impact gun and bolts.
Just leave my duct tape alone.