Our great sponsors
pants | jk | |
---|---|---|
34 | 9 | |
3,059 | 398 | |
2.5% | 0.0% | |
9.8 | 0.0 | |
6 days ago | about 1 year ago | |
Python | Go | |
Apache License 2.0 | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
pants
-
Monorepo + Microservices + Dependency Managment + Build system HELL
Does pants/bazel can help me?
-
Go Dependency management in large company projects - How do you do it?
Hyper-large tech companies managing hyper-large monorepos using Bazel (google), buck (Facebook), please (thought machine), pants (Twitter, Foursquare & Square) enjoy them but also have a lot of resources devoted to running and maintaining it.
-
Reason to use other Build Tool than Make?
Yeah there's definitely some alternatives out there. Pants is another one that has a lot of traction.
-
Is it possible pickle a function with its dependencies?
You should look into pex, or itβs parent build system pants. A PEX (Python EXecutable) file can package up all your code including dependencies and run on another machine of similar OS with just an available compatible interpreter.
-
Maintain a Clean Architecture in Python with Dependency Rules
Before clicking on this, I expected to see import-linter [0] which achieves something very similar but with, in my opinion, a bit less magic. Another solution in a similar spirit is Pants [1], though this is actually a build system which allows you to constrain dependencies between different artifacts (e.g. which modules are allowed to depend on which modules).
To Sourcery's credit, their product looks much more in the realm of "developer experience" -- closer to Copilot (or what I understand of it) than to import-linter. Props to them for at least having a page about security [2] and building a solution which doesn't inherently require all of your source code to be shared with a vendor's server.
[0] https://github.com/seddonym/import-linter
[1] https://www.pantsbuild.org/
[2] https://docs.sourcery.ai/Product/Permissions-and-Security/
This has also been recently integrated in pants.
- Blazing fast CI with MicroVMs
-
Visualize your dependencies with GraphMyRepo.com
This was the fix: https://github.com/pantsbuild/pants/pull/16896
-
Better CI/CD caching with new-gen build systems
A build system is a program that orchestrates the execution of underlying tools such as compilers, code generators, test runners, linters and so on. Examples of build systems include the venerable Make, the JVM-centric Ant, Maven and Gradle, and newer systems such as Pants and Bazel (full disclosure: I am one of the maintainers of Pants).
-
Using URLs for dependency management
Pants allows you to override an artifact's URL: https://www.pantsbuild.org/docs/reference-jvm_artifact#codeurlcode
jk
- Jsonnet β The Data Templating Language
-
The Curse of NixOS
People have tried: https://github.com/jkcfg/jk
But yeah I agree. The thing is, if all you need is robust determinism why do you need a full functional language with currying and other complex concepts?
Google had the same problem for Bazel, and their solution (Starlark) is way easier to understand.
-
Pants vs. Bazel: Why Pants may be the right choice for your team
If I were writing a build system today (and I did just write one actually to test out some ideas) I would use Typescript for the language with something like jk to provide hermeticity. Typescript has many advantages, especially over Python, but mainly:
-
The Perfect Configuration Format? Try TypeScript
Great little writeup ! After mangling YAML, HCL, JSON for years as an ops engineer, I have come to the same realisation. In fact, I have put this into practice in production pipelines by using: jkcfg[1] for the last couple of years. Two data points: 1. Zero developer support contract rate around YAML syntax and templating issues 2. High number of contributions in our private typescript configuration library from developers. Using typescript as an ops frontend has made operations a lot more approachable to folks.
Recently I took what learnt in the last 2 years using jkcfg/typescript and taken it to Deno in form of an opinionated port of jkcfg called: dxcfg[2]. Its early days, but I would bet on Deno/typescript for future ops configuration.
It's possible to sandbox most languages, and with some work you can probably make them deterministic too.
Here's an example: https://github.com/jkcfg/jk
That beats having to learn an entirely new language.
Why? The only reasons I can think of are:
* They can be non-deterministic (do a different thing each time you run them).
* They can be non-hermetic (access stuff in the environment you don't know about).
* They can do naughty security things.
* You can't present GUIs of them because they aren't declarative.
All but the last one don't exclude programming languages. Here's an interesting project to make hermetic deterministic Javascript (Typescript support is planned):
For the sorts of places where you don't have a GUI for the settings anyway (which is the common case) I think it makes loads of sense. It beats making the kind of declarative programming languages you see in YAML files.
-
Cue: A new language for data validation
Maybe Javascript? A lot of web tools support Javascript config files. There's this nice-looking effort to provide a hermetic execution environment for them: https://github.com/jkcfg/jk and if you use Typescript you get an extremely good static type system too. Plus the language is already very well known with loads of tool support and documentation.
Definitely what I would use today.
-
Boa release v0.13
You may be interested in jk. If you don't want to use a special purpose configuration language (jsonnet, cue, dhall, etc), this is a nice alternative that uses js in a hermetic runtime (but see their open issues for progress on that). They seem to also be adding native typescript support so you could even have type checking built-in.
What are some alternatives?
Bazel - a fast, scalable, multi-language and extensible build system
megalinter - π¦ MegaLinter analyzes 50 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally.
please - High-performance extensible build system for reproducible multi-language builds.
vm2 - Advanced vm/sandbox for Node.js
Buck - A fast build system that encourages the creation of small, reusable modules over a variety of platforms and languages.
pyflow - An installation and dependency system for Python
dhall-lang - Maintainable configuration files
pyupgrade - A tool (and pre-commit hook) to automatically upgrade syntax for newer versions of the language.
megalinter - π¦ Mega-Linter analyzes 49 languages, 22 formats, 21 tooling formats, excessive copy-pastes, spelling mistakes and security issues in your repository sources with a GitHub Action, other CI tools or locally. [Moved to: https://github.com/oxsecurity/megalinter]
hof - Framework that joins data models, schemas, code generation, and a task engine. Language and technology agnostic.
Poetry - Python packaging and dependency management made easy
FlatBuffers - FlatBuffers: Memory Efficient Serialization Library