Dark Arc

It is not; it’s a distinctly British-influenced if not outright British term.

https://en.m.wikipedia.org/wiki/Waste_container

Interesting, though I’m not sure that it would really be lemmy at that point, no?

ActivityPub in a certain sense is not Plebbit … and I’m not sure how compatible these ideas really are.

It would’ve been fine… If Google had stuck to it and marketed it, it would’ve worked out. I’m convinced interest rate hikes are what actually killed Stadia.

Also it wasn’t even Netflix like… You’re right about one thing though, part of the reason stadia didn’t do well is 90% of gamers think it was some laggy Netflix for games thing.

You’re ignoring that simple principles make great guidelines for not overthinking things.

Name some great “simple principles;” everything has nuance and trying to distill things into “well it’s just this simple principle…” is a great way to get catastrophic mistakes.

And you’re doing so in the context of an article about the dangers of overthinking things.

You did not understand the point of that article if you think it’s about the dangers of over thinking. The issue with DRY is that it leads to making refractors without thinking about whether or not the refractor makes sense. That’s the exact issue the author is warning about, think about whether or not dry makes sense.

That has ABSOLUTELY NOTHING to do with how many times the code has been repeated. It has everything to do with why it’s repeated.

You’re coming across like one of the rookies who need this warning.

I’ll toss that right back at you bud. You don’t seem to understand the actual problem.

Consider counting to three, before applying DRY. It works.

It does not. I literally fixed a bug today because the same algorithm, doing the same job, was used in two different places formatted differently, exactly two, and they got out of sync resulting in memory corruption.

That’s what DRY is intended to fix. Not “I have three [or whatever number] things doing the same thing so now I should DRY this code up”, I’ve seen HORRIBLE refractors from DRY applied to 3 things; absolute spaghetti inheritance hierarchies that were “DRY.”

I hate talking about DRY because it’s this principle that so many people think “oh I’m doing it correctly; I’m doing good things!” and they actually make the code SO MUCH worse.

EDIT: Here’s exact quotes from the article (emphasis theirs):

Applying DRY principles too rigidly leads to premature abstractions that make future changes more complex than necessary. Consider carefully if code is truly redundant or just superficially similar. While functions or classes may look the same, they may also serve different contexts and business requirements that evolve differently over time. Think about how the functions’ purpose holds with time, not just about making the code shorter.

You’re both saying the same thing though.

We’re not quite saying the same thing though because …

It’s not a 2 vs 3 issue. You can have an infinite number of instances of the same logic and it still not be a case for generalization because it’s not actually general … it’s just an infinitely large program. You can also have two copies of the same code that should be reduced because they are general (e.g. you have the exact same algorithm for generating a UUID copied into two different spots). If you’re thinking about it in terms of quantity you’re already doing it wrong.

It’s not fixable by “just” copying something.

Those two points are really important points.

The code in the article isn’t complicated enough that I’d bother. It even ends up with about the same number of lines of code, hinting that you probably haven’t simplified things much.

I think it’s a good example of the problem though. People take that same idea and apply it too liberally. The point isn’t that specific code, it’s about not apply DRY to code that’s coincidentally identical.

But otherwise, I disagree with the article. If it’s complicated enough to bother abstracting the logic, the worst that can happen in the above situation is that you just duplicate that whole class once you discover that it’s not the same. And if that never happens, you only have 1 copy to maintain.

That’s… Not at all true in practice. What often happens with these “DRY” abstractions when they’ve been improperly applied is you end up with an inheritance hierarchy or a crazy template or some other thing. You’re really lucky if you can just copy some code and find your way out of the weeds.

There are plenty of bad abstractions in the wild and novices applying DRY is a common source of them.

It should be about concepts but it’s more often applied to duplicate algorithms by inexperienced people (which is a huge mistake).

I’ll save you a read… A developer that worked on the game for a while but left the studio thinks they could’ve made the game with fewer loading screens even in their engine. That’s pretty much it.

I’d also recommend taking a look at Threema.

I think their product direction is a bit better. Particularly as Signal still shows a message that they don’t back sync messages before you paired devices “for your security” … Threema also doesn’t back sync messages in their beta multi device setup, but that seems to be more less of a product stance and more of a “we just don’t do it yet.”

Threema is definitely missing some features like emoji reactions, stories, and a builtin cryptocurrency (which depending on your stances might be pros or cons).

Both apps have definitely gotten better over the years; I think Threema’s multi device support has really drained resources on their side so there hasn’t been as much outward feature work. I’m hoping it won’t be terribly long until that changes.

Then not to be aggressive about it, but go get qualified or stop spreading FUD honestly…

Gamers do this stuff – what feels like – all the time now. I don’t get the DLC hate. Not every instance of “give me more” needs to be an entirely new full price game.

Yeah I was about to say … anyone that’s got a problem with UE5 should take a look at Remnant II.

Like radically insidious man.

That seems incredibly unconvincing on its own. It sounds like this person had a lot of alt accounts, probably was doing ban evasion, and kept posting things that violated the TOS.

That’s literally a passkey.

I’m hoping Godot becomes a serious competitor but I’m also thinking CryEngine 6 might be a true UE5 competitor. It’s basically the WIP engine for Hunt Showdown and Crysis 4.

That’s adorable!

I really think the blue sky is bad stuff is overdramatic xbox vs PlayStation kind of stuff.

The fediverse needs a lot of work, blue sky is a different and interesting model that’s different from what we’ve seen so far (even if they haven’t let people start hosting their own blue sky instances).

I say let them complete…

I really wish more people took security seriously. Something that is not receiving security updates is not working just fine.

Just make sure your network firewall is good I guess. That’s the only proper way to run outdated stuff and even then it’s sketchy.

Also it’s an operating system not a browser.

Because it will run jellyfin, with fewer system resources, and still get security updates (that you can configure to auto install at the correct time) for … free.

You also won’t at some point find yourself running such an old version of Windows that jellyfin no longer updates unless you buy the latest version of Windows.

You can just go download Ubuntu desktop LTS and do everything by just opening a terminal, plopping that one liner, and letting it run: https://jellyfin.org/docs/general/installation/linux/#repository-automatic

I’ll flip the script and ask “why in the world would you use Windows for something that doesn’t require it?”