one of the things about, like... building to last, building something that's meant to serve a community's needs and not be replaced from scratch every five years
-
one of the things about, like... building to last, building something that's meant to serve a community's needs and not be replaced from scratch every five years
-
is that the things that make something good for that purpose are directly at odds with what many of us have been taught to expect, even demand, from corporate advertising
-
we can't keep adding things constantly
-
we can't change things that work fine just because somebody wants to, there has to be a reason that the change is worth the harm it causes
-
if we do give in to those pressures, what we wind up with is something that's too big to be maintained as a community project, something that can only exist in a corporate setting
which puts us right back where we started
-
people advocating for constant feature churn and re-architecting don't usually say it as "let's throw everything away and do it again"
nor do they say "let's force everyone to learn a new way to do the same thing"
-
they usually say that if we don't keep up with the latest features that people have come to expect from the corporate platforms, we can't compete with those platforms and we will lose out on innovations
-
and uh
we aren't trying to "compete"? there is no money changing hands here, or at least there better fucking not be, we will regard it as malfeasance if we find out someone took a kickback to add features to fedi infra
