>>106869100
In realworld engineering, "if it ain't broke, don't fix it" rules the day. I think it's the fact that every low-tier poojeet or newfag-tier dev thinks they understand something better than the actual engineers, and so want to """plus""" it. And normalcattle who even care think this is a good thing too?

This probably leads to some kind of destructive niggerlicious-cycle of "if its broken, break it some more!111"

Or something like that.

>>106869100
Nina would say that actually

>>106869100
they think software cannot be finished
they are used to broken software needing constant security updates and bugfixes
/thread

>>106869100
baseddevs using external dependencies for shit that would take 15 lines of code to roll yourself

that's literally it. when every project has 50 dependencies, and each of those has 50 dependencies, you can see how the exposure to breaking changes in some upstream repo grows exponentially. someone else found a CVE that needed to be fixed, or broke an API, now thousands of packages downstream need updating.

>>106869100
I manage a project that provides bindings to a Linux API subsystem for a fairly niche programming language. It does very little and is essentially just a wrapper around existing ioctl commands with some basic error checking. I rarely need to make changes to it, only when the userspace API gets updated with new commands. The last time this happened was ~5 years ago, and honestly at this point it can probably be done by an LLM just based on how little the bindings themselves need to do.

I received an issue report last week asking if the project was abandoned and if they should fork the project and maintain it themselves. When I told them the situation of the project and that there's no need they started asking for features like buffer management, string validation, and even handling the device's file descriptor by using hardcoded paths in either /dev/, /sys/, or dbus API calls. Even though the project was "done" to me, it wasn't "done" for them.

I did manage to convince them to create a new library that simply used my project as a dependency with their features added on top, but ironically it appears to be abandoned now and they are no longer active on Github.

>>106869100
Updates are like events, they might restore some dialogue with a character you like, they might fix some important gameplay bug, might introduce a funny bug, might give better performance, might add new content or features. So as long as there's a pour of consisant updates it keeps a game's community more active and talking and makes them more likely to play the game too, similar with fanart, or fancontent in general and mods and such. A lot of modern games that have big consistent playerbases on steam either get updates all the time or other stuff like mods. i.e Skyrim, Fallout 4, Cyberpunk, Witcher 3, Baldur's Gate 3, Stardew Valley, New Vegas

>>106869791
Balatro comes to mind, which has been feature complete since its first release, modulo a rebalance patch I didn't much care for. It still gets updates literally just to change the card arts and it's enough to keep attention on it and attention is literally the only thing that separates "good" indie games from "bad" indie games.

File: updooter.png (186 KB, 1200x675)

186 KB PNG

>>106869100

File: 1739774643601601.jpg (43 KB, 632x601)

43 KB JPG

>>106869100
>I've noticed this weird modern trend with games
No, you haven't. People will keep playing good games if they are completed. They literally pay monthly subscriptions to play 30-year-old games.
>but especially with programs
Happens sometimes, and it's mostly planned obsolescence. Most software companies don't give out perpetual licenses and such, and on non-Windows systems, the OS devs make it impossible to run old programs. If users are satisfied with the software they have, and they can keep using it, they often keep using it if they're available and there aren't better options.

The word you are looking for is "libraries." If I open your meme library's github page and see that the last coommit was more than a year ago, I assume the project is abandoned (which is actually right more than 9 out of 10 cases). Of course, some of them may still be usable, but for shit where security is a concern, it's as good as dead.

>>106869937
>no you haven't
I can't believe it, things I've noticed aren't true
Are you the true god of this universe?

>>106869941
You may have noticed it with 1 or 2 flavor of the month online O N I O N S games or something, but there is no such "trend" in games in general.

>>106869937
>No, you haven't. People will keep playing good games if they are completed.
>i really want to play this game but is there a fan update patch that brings it up to modern tastes?
You really haven't seen people post the above about old games and then refuse to play it if there's no patch?

>>106869971
Honestly, not really. Not saying it never happens, but the biggest hurdle normalfags face is getting the game to run. If they can run the game, they're usually ok with it.
>old game available for free, playable with an emulator
:(
>same game but packaged with an emulator and sold as a subscription service by Nintendo
:O

>>106869100
still updating = beta
I'll wait for the final version to drop. What, you won't be selling it by then? Then piracy it is.

>>106869100
>this weird mindset of needing constant updates
thats funny because i get annoyed by constant updates so i will skip and disable reminders

>>106869100
In the corporate world, especially anything even adjacent to the defense or finance space, updates are required because the second anyone finds even a slight vulnerability in something, even a dependency, doesn't matter if it can't even be exploited the way you're deploying it or not, doesn't matter if you aren't even using or exposing the vulnerable feature or component, you get 30 days (sometimes less) to fix it or shut the whole thing down.

>>106870919
I suppose that makes sense, but i'm talking about innocuous stuff, the example I use is MPC-BE, a good video player that people recommend you don't use because there's no more updates

>>106870975
I suspect its cultural diffusion. Enough people work in those sectors that interact with other projects, or end up working in other sectors and bring that mindset along with them, or contribute to open source, and those ideas get passed around subconsciously and it ends up like that study with the monkeys and the ladder.

Probably also has to do with the fact that many software ecosystems like Python, Java, and Node.js, are just low quality, so if you ever stop updooting then you freeze the process of it slowly become less shit over time.

>>106869100
>>106869189
software cannot be in a finished state so long as the dependencies it requires keep changing underneath it.
Just take any linux software repo, look back to a commit snapshot dating back even 5 years and try compiling without getting errors.

>>106869100
I come back if it fixes problems that I had. Same reason why I want the newest KDE there are a couple of issues that still haven't been fixed and I am hoping it will be.

>>106869773
reddit type mods collecting projects and probably putting maleare and nagware for free money