4 ms·
Man, this might be a dream, but it's one I'd love to see come to some form of fruition. As someone who's learned programming through self-study, the broad swat
by voidhorse 9y ago
Man, this might be a dream, but it's one I'd love to see come to some form of fruition.
As someone who's learned programming through self-study, the broad swath of tooling out there can be a bit of a barrier to picking up new languages and concepts, especially when the concepts related to building and delivering software are occluded by some of the opinionated decisions all the different tool sets make about how building projects should work.
Learning a new language and new concepts already takes a good deal of time, which may be a valuable resource if you're not in any official program of study and making use of free moments. This is only exacerbated by the frequent need to learn a whole new tooling ecosystem along with any new language you decide to pick up. A sort of rosetta stone of package management and build tooling would be a godsend.
- zimbatm 9y agoThat's the idea. Use bazel to describe and build the projects incrementally. The more languages are supported the less project-specific build systems have to be learned. Use Nix and nixpkgs to pull external dependencies (and bazel).