/tech/ - Technology

>>6667 (OP) 
There was a discussion on dependencies and api stability. The two sides of the problem are
>backward compatibility
>old trash
There is are standards which makes program written decades ago still compile and work today. Then there is the burden of keeping old trash which makes creating anything new difficult. Any interface that was thought to be good ideas may not be so good in the future. I have no idea if there is a best answer to balancing them.
This is another one of those patterns that happen everywhere. Maybe we are at a time where the life time of what was invented run out, and something else will take the throne. This won't be  a painless process.

Because the first good build system (Meson) was only made recently and hasn't picked up as many users as it should. Most programmers don't know programming itself and are too dumb to know better or they're in a state of learned helplessness and still think build systems are like mail clients which have never been done right. Also, nobody is taught how to write build definitions correctly and few can figure it out by themselves.

Maven seems OK for Java

>Download pdf related.
>"Excel is a build system in disguise. Consider the following simple spreadsheet. ..."
WTF is M$ smoking??

>>6674
In their model, anything that maintains a key value store with respect to being up to date is a build system.

>>6674
It makes sense. The tables are build instructions rather than values, which are then processed to make the final result. 
I guess the distinction is that a function either just returns you a result or needs to be called, whereas the build instructions generate automated results.