I get the sentiment, but I think Rust does a pretty decent job even in the prototyping phase. I’ll run snippets in Python or Lua, but that’s mostly for data mangling, like generating code from a data format or preparing test data.

So far it works pretty well.

Wait, so saving a ton of money by using a language that reduces production bugs is now a bad thing?

I’m a senior sw engineer, and I don’t get paid because I know the vagueries of whatever language we’re using, I get paid because I can lead a team that solves problems. I don’t really care what the language is, but I do care that it’s relatively easy to on-board someone in case we have turnover or something.

I don’t know about you, but I’d rather be highly paid because I’m able to be really productive instead of highly paid because I’m literally the only shot the company has of fixing the bug.

the lack of OOP

Rust absolutely has OOP, that’s what Traits are for. It just doesn’t have classical inheritance, so you structure your patterns a bit differently.

That said, I lean more into functional-inspired style anyway, which tends to work pretty well w/ Rust.

Can confirm, I’m a senior and I didn’t have much trouble with Rust. After a couple weeks, I was writing useful code. After a month, I generally stopped cussing at the compiler.

I’m still finding odd surprises here and there, but it’s honestly no big deal. I’m about as productive in Rust as I am in Python, which I use at my day job, though I use them for very different domains.

The only reason most of these places that do that though, is because they wrote in COBOL to begin with decades ago, and didn’t want to switch away to something more modern as other languages gained functionality and popularity.

And it would’ve been much cheaper to rewrite once some years ago than to keep paying people to maintain it.

And in many cases, rewriting something improves the code substantially by finding bugs and fixing architectural issues. Old code doesn’t mean it’s correct, it’s just old, and just today we had a high severity bug from code that was never properly tested and sat unchanged since near the start of the project.

not even c++

You dodged a bullet. I much prefer writing in C to C++.

That’s pretty awesome of Tony Hawk.

What does this have to do with personal finance?

OK. I thought that was just poor grammar, which is fairly common on the internet. Carry on.

I feel the same way about cryptocurrency, but with scams instead of jobs.

That’s not a bug though, AI just doesn’t know what a finger is. You can fix some of these problems through iteration, but it’s still not going to know what a finger is.

I guess I’m old school. For me, “zeros day” was always about the time the developer had before the exploit was in the wild. In the old days of physical media, there’d usually be a window between an exploit found on pre-release software that had already been shipped, and the dev could get a fix ready in that time (day 1 patch, like in video games). But if it was found on released software, they’d have zero days to patch it before people are impacted.

The severity has always been a different thing entirely, which is based on:

• type of exploit - privilege escalation vs code execution
• ease of exploit - does it need another exploit to work?
• whether it’s in the wild or theoretical

A zero day could be any of those.

We still call disk partitions disks, even though that’s not really accurate anymore. An NVME drive with a C, D and E partition

I don’t? But then again, I’m a Linux guy, so lettered “partitions” aren’t a thing for me, there are drives (physical), partitions, and mount points (where on the FS does that data live). I haven’t used Windows in a significant way for over a decade.

Yeah, it took some getting used to, but it was a lot of fun.

BitWarden

Yeah, the level of effort required is extremely low, and it’s really nice for things like sharing passwords with an SO for things where separate logins don’t work.

So yeah, I use Bitwarden. I plan to self-host soon (vaultwarden), I’m just figuring out how password sharing works before I go and switch my SO’s stuff over. But it’s audited, FOSS, and generally the dev makes decent decisions (though I hate the new UX overhaul).

I self-host a bunch of stuff too. I am transitioning from Nextcloud to OwnCloud Infinite Scale now that I posixfs is in experimental status (I only use file hosting from Nextcloud anyway). However, my password manager has been very far down the list for me, because the level of effort required exceeds the value I’d get from it, especially compared to other things I can set up.

The hard thing to teach people is that, you don’t actually need to know those 50+ passwords, nor should you care what they are.

Exactly. Use literally any password manager that uses MFA, and set up MFA (Google Authenticator works, I personally use Aegis). I also recommend BitWarden, but there are several decent options available.

The most important thing for them to know is that passwords should be different between services, and you can and should automate that.

I’m the opposite. I loved the more realistic feel of GTA IV, which really fit the vibe of Liberty City and the more gritty story of Niko. I don’t like GTA Vs whole vibe.

My tier list of GTA:

1. SA
2. IV - feels unique
3. III - for nostalgia
4. VC
5. V

I hate pretty much everything about V and ended up hate-finishing it so I could properly complain. It lost most of the satire, all main characters were unlikeable IMO, the map felt empty, and the story sucked.

And then there’s my instance:

• sh.itjust.works - pretty chill, and things tend to work pretty well

I’m not sure what else to say about the culture.

It’s absolutely risky, but sometimes the risk is low enough that it makes sense, like you’re at a relative’s house and setting up access to some self hosted stuff. I use it sometimes on a new install/work computer where I don’t want to set up the password manager long term.

The USB drive works in all those cases, but I rarely bring USB drives with me, especially since I only need to access it like 1-2x/year.

Yeah, pretty much. A segfault happens when you access memory incorrectly, and Rust is all about correct memory access.

Nice. I wonder if they’d be open to rewriting portions in Rust to catch these types of issues with the compiler instead of the user. I’m willing to help if someone else gets the devs on board.

Sid Meiers Pirates

This game rocks.