4 ms·
A brilliant insight I came across once was that a low barrier to entry can prevent standardisation and quality. The original example was that in LISP it's so e
by jiggawatts 5y ago
A brilliant insight I came across once was that a low barrier to entry can prevent standardisation and quality.
The original example was that in LISP it's so easy to add Object Oriented functionality that it's a mere afternoon's work for a graduate student. For comparison, it took Bjarne Stroustrup several years to extend C with objects to create C++. Hence there are only about 4-5 such languages out there, of which only two are popular.
This means that every C++ program is object oriented in the "same way", whereas random OO LISP modules are incompatible and you can't merged them into one cohesive program or reuse the components nicely.
It's almost trivial to come up with a build system. Like you said, it boils down to not much more than interpreting a simple sequence of steps, typically doing nothing more than just triggering shell execution directly or indirectly. A basic build system is a few days work for a talented programmer! Heck, a mere shell script will do in a pinch...
Notice however how the industry is slowly consolidating on Docker and Kubernetes. I suspect that one reason for this is that these are hard technologies. Not just anyone can "whip up" a container build and orchestration system in a short period of time.
Hence, there's only a handful of container systems commonly used in the wild, which has resulted in standardisation. Precisely the type of standardisation that you (and many others) have been craving.
TL;DR: The most complex system will become the CI system standard to rule them all because it's complex.
- lispm 5y agoANSI Common Lisp was the first standardized OOP language (1994) with its integrated Common Lisp Object System. The project to specify this object system took several years and a group of core designers, plus a larger feedback group.
- jiggawatts 5y agospecification != implementation
- lispm 5y agoThe design & feedback was driven together with a portable implementation: Portable Common Loops. The team developed that implementation to validate their design ideas and to get practical feedback from a broader community.