starlevel003

> By the way, could at least us developers use ISO dates instead of whatever our local conventions are?

2023-28 and 2023-39 aren't any more readable.

> Compute, and in the end, energy, has a cost.

making sure that nobody can see ads by ratelimiting them too hard really helps with this, or so I'm told

the post-1.8 codebase awfulness has nothing to do with the source programmer. hell, by 1.13, the game had practically been rewritten at least once over.

> I really don't understand how the need for indexing and search was overlooked.

It wasn't overlooked. The point is to make it difficult for outside users to access information unless they sign up.

> This "defund de police" bs has been one of the most damaging rhetoric's in American cities. People are being victimized left and right, robberies, rapes, gang violence, etc because some people know there are little to no consequences.

Police budgets haven't actually been defunded, and yet this still happens.

> * If you mean a thing that's meant to be deployed with a bunch of Python dependencies, then `requirements.txt` is probably still your best bet.

This is exactly how we got in this mess. Using ``setup.cfg`` or ``pyproject.toml`` for all projects makes this easy as now your deployable project can be installed via pip like every other one.

1. ``python -m virtualenv .``

2. ``source ./bin/activate.fish``

3. ``pip install -U https://my.program.com/path/to/tarball.tar.xz``