I once worked on a C program. It has been the worst experience of my programming career, right next to updating excel's vb macro to meet newer business needs.

I once worked on a C program. It has been the worst experience of my programming career, right next to updating excel's vb macro to meet newer business needs. The mere fact that I could not build the project on my local machine (windows) and have to login to a Unix (IBM AIX) was baffling. Yep, Unix, not even linux. And because it was a business critical program which worked, business refused to make any drastic changes to it unless they were absolutely necessary, even if it was a bug fix to a frequently occurring issue. And I maintained it till 2018 when I left that job. I am pretty sure it is still there in same state. So, I understand the build tool woes, and cross platform issues. however, I understand it to mean that package manager is not feasible in current environment, not that it does not add value. Recently there was a post on zig, which aims for providing a standard build tool for C (& zig), and later, a package manager for C (and zig) So, I think such efforts are not only beneficial, but will become reality in future