i’m not sure how i ended up writing an essay re: your post but the gist is i feel that your approach is not fit for tt-rss and its development. the end.
i also feel that library culture and everything related to it breeds terrible developers as illustrated above so i don’t want to personally partake in it but that’s really beside the point.
this is literally what you’re proposing - this whole thing is complicating stuff for no reason.
the tools you’re talking about might be great for some bootcamp nu-developer whose hello world app has 3500 dependencies because of cancerous npm culture there’s a library for every little thing. tt-rss doesn’t suffer from this problem and development approach. there’s a manageable amount of third party code which is like 90% dojo, that is precompiled in a certain way and bundled for a reason.
e: tbf it also might be justified for some fuckhuge software project with many developers which tt-rss is not and never will be. it’s a niche tool for nerds, everyone else uses twitter.
for tt-rss the end result would be either complicated deployment with more required external dependencies or me needing to generate easy to deploy tarballs so normies who have no idea about any of those tools (not only composer and npm but css compilers that you proposed) could unpack tt-rss on their shitty hosting and it would work oob.
please try to understand that tt-rss is not my job. it’s vastly easier for me to not deal with any of this shit, partly because i’m not functionally retarded and can just edit the stupid css file or w/e in vim if need be. also, i don’t feel that switching, for example, autoload systems just because i could probably use it for this one external library and it’s “more modern” while i have stuff working right now is justified.
i can easily see how the whole thing might feel archaic to some starry eyes 20 yo kid (not implying it’s you) but that’s what works for me.
see, there you go implying again. and yet somehow not everyone has difficulties with their contributions and ideas being accepted.
you said legacy, not me. by definition, “denoting or relating to software or hardware that has been superseded but is difficult to replace because of its wide use.”.