I'm a fan of using just as a command-runner as well, but took a slightly different approach to making it pip-installable! I created the `pyjust` package (https://pypi.org/project/pyjust/), which literally just packages the `just` binary in platform-specific wheels, and then unpacks it onto the PATH by leveraging the `scripts` directory unpacking.
Why do this you might ask? My rationale here was that I use `pipx` to install some python CLIs, and it was nice to be able to lump `just` in with that, as well as to be able to declare it as a "dependency" and pin specific versions for distribution.
I love this! I use pipx all the time, and this is perfect workaround on a computer that either does not have Rust and/or requires me to manually download from the repository.
Great idea, and I am wondering if there are more utilities I could/should wrap in a similar fashion. A cross platform brew.
simonw got me interested in the idea after I ran into one of his blogposts talking about how ziglang does it, and then studying ruff + maturin helped me reverse engineer how to accomplish this without any python intermediary in a "python package".
I put together a cruft template (https://github.com/justin-yan/templates-cruft/tree/main/pack...) since I had the exact same thought as you once I got it working - why not do this with a bunch of different tools? I did it with a couple of my favorites (just, lazydocker) but haven't gone back to clean things up/make things a bit more systematic. So it's a pretty messy weekend project (caveat emptor) but hopefully it's a helpful starting point if you want to try it!
Taking a different line of questioning: Does anyone have any insights or resources on the non-tech stack a one-man SaaS should use?
At various points, I've looked into opening a single-owner LLC to hold some small side projects I want to put on the internet for fun, but the number of decisions and amount of overhead has always seemed pretty daunting.
I've struggled a bit to find resources helping to describe what section 230 protections are actually for, however. Many of the examples explaining section 230 protections seem to revolve around things like defamation in Youtube comments or product reviews, but I'm having trouble making the leap from that to why messengers are so concerned about this bill. Why do tools like messengers need section 230 protections to begin with? AFAICT they still have to submit to things like national security letters, so what does section 230 buy, say, Whatsapp or Signal?
not to mention that the TBD requirements have to be approved and voted on by congress to become law.
that said, there is also some text that changes specific wording in other existing laws that may have an impact on future court cases, e.g.: “(2) CIVIL REMEDY FOR CERTAIN ACTIVITIES RELATING TO MATERIAL INVOLVING THE SEXUAL EXPLOITATION OF MINORS.—Conduct by a provider of an interactive computer service (as defined in section 230 of the Communications Act of 1934 (47 U.S.C. 230)) that would violate section 2252 or section 2252A if that section were applied by substituting ‘recklessly’ for ‘knowingly’ each place that term appears shall be considered a violation of section 2252 or section 2252A for purposes of paragraph (1) of this subsection.”.
We could be charitable about what 'recklessly' means, but given the tendency of pre-digital judges to misunderstand technology - I can understand why there is a pushback against this kind of language.
"What do you mean you don't keep a history of your clients' internet activity? I would construe that as reckless behavior."
The Atlantic has an effort to break this tracking down on a state-by-state basis (https://covidtracking.com/data/) which definitely has some interesting nuggets and gives some color on how they arrive at their numbers on a per-state basis.
Opening this gives a glimpse into the nightmare that must be collecting and organizing these statistics. You can see that every state has a different method for presenting infection and testing stats. I can't imagine how hard it is going to be to get to consistent data over the whole world.
Why do this you might ask? My rationale here was that I use `pipx` to install some python CLIs, and it was nice to be able to lump `just` in with that, as well as to be able to declare it as a "dependency" and pin specific versions for distribution.