matiasfernandez

At Stripe, we believe that the burden of proof is on he who denies, not on he who declares.

I got some banana bread at work today. Hell yeah.

So it goes to show that waiting for things is, like, worth it.

But there's a lot of bad things in this world, dude.

Like fucking skunks, dude. HELL NO.

Scratching your eye, but it's still fucking itchy. HELL NO.

The fucking Cubs, dude. HELL NO!

Fucking ligatures in fucking programming fonts, dude. HELL! NO!

BUT BANANA BREAD, ON FUCKING WORK, DUDE! HELL YEAH! HELL YEAH, BRO!

I don't mind the sluggishness as much as the dialog in Witcher games. I tend to prefer games with little-to-no required dialog and Zelda's interactions tend to be more mechanical than conversational.

I'm fine with lore, but as soon as I have to sit down and listen to video game writing while losing control of my character, I'm instantly bored.

“For example, one argument would be that the evidence I’ve presented here is consistent with a strategy of quickly shipping “version one” with poor performance, then starting work on a high-performance “version two” to replace it. That would be completely consistent with the evidence we see.

But even if that turns out to be true, it still means programmers have to care about performance! It just means they need to learn two modes of programming: “throw-away”, and “performant”. There would still be no excuse for dismissing performance as a critical skill, because you always know the throw-away version has to be replaced with a more performant version in short order.

That kind of argument is great. We should have it. What we should not have are excuses — claims there is no argument to be had, and that performance somehow won’t matter anywhere in a product lifecycle, so developers simply don’t have to learn about it.”

Or as Casey would put it: Discord is taking 3.7moo ("Moon Unit") to open. A Moon Unit is equal to ~2.7 seconds, the maximum ping time to the moon. Therefore, if Discord had their servers on the moon, nobody would know the difference.

I never have trouble with memory management in C by sticking to "grouped element architectures" with explicit lifetimes such as arenas, scratch allocators, dynamic pools, etc. RAII is mostly for "single element architectures" which IMO are not a good way to organize code because they tend to amount to thousands of unnecessary memory operations.

Instant response != Instant resolution. Getting support at Stripe is easy for easy things, but hard when it actually counts. Based on what we've seen here (and what I've personally experienced) getting your payouts paused while not being a fraudulent actor is not that uncommon. Any other provider would not be like "Your case will be reviewed by our specialized team at some point this week, or maybe the next, nobody knowns. In the mean time, please tell all those employees you need to pay next week to take a chill pill." Can you see how this can be frustrating? We process >$10M/YR with other providers and ~$2.5M/YR with Stripe. Our other providers show a lot more urgency when something serious goes wrong, while Stripe feels like they're too big to care if we leave.

Impressive work! Where is the net package getting worked on? Is it the "core_net" branch or do you have your own fork?

As an individual, you should have the right to access any information another person wishes to generate. AFAICT, Hacker News moderators are hiding posts they believe do not provide value to the site. This is fine, but you can still see a non-moderated feed using Algolia's Hacker News search website.

> We do not hold any user funds for any reason other than fraud prevention.

Ah yes, the things we do for "fraud prevention". I get that regulations might have Stripe's hands tied, but to say that the users posting their frustrations with frozen payouts are almost always fraudulent is a straight up lie. They might have triggered "fraud prevention" flags imposed by regulations on your system, but the majority are not fraudulent themselves (including me, who's had payouts frozen multiple times by both Stripe and Shopify, which I assume uses Stripe as a backend). We keep getting flagged and then "ok'd" by you guys almost twice each year. It's incredibly frustrating.