celticmusic

> Rust is the language that the C++ Committee would make if they could start over.

Bjarne has explicitly refuted this opinion.

I refused to get on FB for many years, until I was finally convinced to do it. I never did more than post funny pictures I found around the internet.

And then the next political cycle hit and I straight up quit. I found the political ads more offensive than anything, and I've never been back since.

FB is a terrible place, ignore the poster you're responding to because they very well could be putting on airs while you're trying to be more honest about things. That's the nature of social media, of which HN is included.

I know, imagine if social security went away because hezbollah was killing people. Definitely need to pay attention in case that happens!

[flagged]

> People have been complaining about what you're complaining about for thousands of years. What I find truly puzzling -- given the supposed madness of crowds -- is that things are going so well.

The people doing the manipulating are generally getting what they want, why would they try to pull the system apart?

What's hard to fathom about Python insisting on a GIL to ensure all C extensions play nice?

What you just said is 100% incorrect and I strongly recommend you read back over what I wrote and think about it a bit more.

You render a UUID into the browser form and send it along with the submission however you want (post input, http header, etc). Then the server both requires the UUID to be there and passes it along to stripe.

Stripe will not allow an idempotent key to be reused w/i 24 hours.

You can use anything for the idempotent key and Stripe will actually track that along with the charge object so you can use something more meaningful if it's useful for your business.

edit: and if you generate a key that's more meaningful I'd be careful about leaking important/private data.

I grew up poor with some bouts of homelessness, and this isn't my experience at all.

Anyone judging you for not having an iphone isn't moneyed.

I think it's more about recognizing that structure is like cement in that once it's laid down, it holds things in place and can be a pain to pull up and change.

For this reason, it's better to prefer as little structure as you can reasonabley get away with, not more. Now, this is a nuanced view, a senior person can absolutely insist on more structure up front and avoid issues, but they'll have a good reason for doing so that doesn't involve "it's clean code".

But in general, you want as little structure as you can get away with. It's a lot easier to change something that hasn't been abstracted to death with guesses about what the future is going to hold.

I think part of the issue is a perspective thing. If I spend a day throwing something together and it sits for 6 months, great. I got ROI from that code. If 6 months in new requirements come in and I decide I need to rewrite it, who cares. It worked day in and day out for 6 months off a days worth of effort.

Too many people view code as needing to be long lived and unchanging.