I have heard dreaded comments from *JS ecosystem users that the packages go to unmaintained state and there is just too much noise in the ecosystem. Very few pa

I have heard dreaded comments from *JS ecosystem users that the packages go to unmaintained state and there is just too much noise in the ecosystem. Very few packages thrive and live for longer periods... and eventually results in a lot of rewrites for newer engine support. Also, does it add to a non-maintainable code (or result in a complete rewrite) in a period of six months to one year? I don't code much of web apps as I'm a system's guy who still code in C where the created programs are running fine across OS versions without dependencies and many have crossed decades of use without resulting in any security issues. Most of them are for security and system's utility purposes and does some complex work on media and security pipelines. Also, many hours have gone into making them secure from the general RUST / GoLang fortification offering perspective as I am against using RUST or GoLang as I have got some experiences with them on the long term maintainability and support. Some of the created programs run fine with OSes older since the early day's of SUSE to the modern rolling versions of Linux (and almost all versions of Windows since Windows NT till date) without any modifications. It cannot be guaranteed with RUST or GoLang or with any other stack other than C... Sorry for the deviation though!