This is something often repeated by OOP people but that doesn't actually hold up in practice. Maintainability comes from true separation of concerns, which OOP is really bad at because it encourages implicit, invisible, stateful manipulation across disparate parts of a codebase.

I work on a Haskell codebase in production of half a million lines of Haskell supported by 11 developers including myself, and the codebase is rapidly expanding with new features. This would be incredibly difficult in an OOP language. It's very challenging to read unfamiliar code in an OOP language and quickly understand what it's doing; there's so much implicit behavior that you have to track down before any of it makes sense. It is far, far easier to reason about a program when the bulk of it is comprised of pure functions taking in some input and producing some output. There's a reason that pure functions are the textbook example of testable code, and that reason is because they are much easier to understand. Code that's easier to understand is code that's easier to maintain.

Answer me this: are they or are they not consistently in support of Russia/China? Because I've seen it a lot from them (and blocked the instance soon after joining Lemmy when I noticed the pattern).

Is it just some big joke that went over my head?

Yeah, this person posts a lot and is weirdly consistent in how much they fuck up post titles.

Same story for Nebraska. Most of the population lives in Omaha or Lincoln which both lean blue, but Republicans gerrymandered the fuck out of our districts so we're a red state. And it matters a lot more here since we're one of two states that split our electoral college votes by congressional district. Like recently Lincoln overwhelmingly voted for a Democrat for our district in a special election, but Republicans naturally redrew the fucking maps to include counties that are fucking north of Omaha (like 120 miles away). Look at this shit: https://www.google.com/maps/place/Nebraska's+1st+Congressional+District,+NE/@41.2698636,-96.4887192,8z/data=!4m6!3m5!1s0x87915d2ef259455b:0x74cb97568fa3047a!8m2!3d41.5312936!4d-97.2652858!16zL20vMDl0eHky?gl=us

Been using vim+tmux for the last 8 years and still going strong. Wouldn't ever give it up. Vscode's pretty lackluster in comparison.

What's the difference between "vitlök" and "vit lök"?

:syntax off and it works just fine.

In my experience, your average software developer has absolutely terrible security hygiene. It's why you see countless instances of private keys copy/pasted into public GitHub repos or the seemingly daily occurrences of massive data breaches.

My undergrad in CS (which I should point out, is still by far the most common major for software engineers) did not require a security course, and I'm fairly confident that this is pretty typical. To be honest, I wouldn't have trusted any of my CS professors to know the first thing about security. It's a completely different field and something that generally requires a lot of practical experience. The closest we ever got was an explanation of asymmetric vs. symmetric encryption. There was certainly no discussion of even basic things like how to properly manage secrets or authn best practices.

Everything I know now as a senior software engineer about software security has come from experience on the job. I've been very fortunate to work at some places that take it very seriously (including a government contractor writing cybersecurity software for the Department of Defense) and learned a lot there. But a lot of shops don't have a culture that promotes good security hygiene, and it shows in the litany of insecure software out in the wild today.

Let's not get wrapped up in wild conspiracy theories like Republicans are so prone to do. No one is intentionally doing this. It's poor regulation, oversight, and controls. Simple as that.

That just sounds like a shitty editor, tbh. Pretty basic functionality.

I've yet to find games I can't play on Linux these days.

Yikes, pretty bizarre considering stateless endpoints is the gold standard.

Re: persistent process, that doesn't seem like a big deal, to me. It's pretty normal since you often want to keep some common stuff going, like metrics. Unless you're doing something crazy it should really take next to no resources while idling.