manfre

2000 lines in a single script file is a lot to mentally process. Unlike a large utils.py (the junk drawer of a putting module), with a script there is often a wide range of functions and classes.

My best advice would be turn this into a more organized package that you install with pipx[0] on the systems that need it. The click[1] package is helpful too.

[0] https://pypi.org/project/pipx/ [1] https://pypi.org/project/click/

It showed me the reject all on top of the accept all. Clicking reject all left me looking at the accept all banner. Only options were "accept all" or bounce.

This doesn't speak highly of their frontend team with the "I am very smart" undertone other comments mentioned.

> three engineer-years (from engineers experienced working in CPython internals) between the acceptance of PEP 703 and the end of 2025

This means multiple devs over a period of less than 3 years.

Not sure about what Meta is using for Threads, but gunicorn and nginx are a common set up for Django in production.

Some will use `python manage.py runserver` in production, and they are using the defacto wrong set up. Don't ever do that.

With ssd and nvme drives being available for cheap, it's probably not worth devoting engineering resources to improve it. They still cater heavily to OEMs and many of those have stopped specing spinning disks for the boot drive.

This will probably kill the utm_source as a standard. Companies that want this will blob encode all the fields or rename when generating links and remap back on their reverse proxies.

If the fake abortion centers advertised with a similar, up front, "why you shouldn't" message, it wouldn't be unethical. Their current practice is fraudulent.

Discussion of Go toolchain wanting to add telemetry for these same reasons. This casts doubts on how well they're managing to do it.

https://github.com/golang/go/discussions/58409

That is my largest source of frustration with slack. It's an almost daily occurrence that results in me drafting longer messages in vscode.

> aggravating (e.g., self-checkout lanes...

self-checkout lanes are not viewed as a bad thing by many. Given the option of a self checkout or staffed checked, I'd choose self checkout. The negative aspect of self-checkout is that it's usually paired with the store being understaffed, instead of redirecting the freed up staff to other roles.

> In comparison I could just type git clone https://github.com/ggerganov/llama.cpp and make . And it worked.

You're comparing a single, well managed project that had put effort into user onboarding against all projects of a different language and proclaiming that an entire language/ecosystem is crap.

The only real take away is that many projects, independent of language, put way too little effort towards onboarding users.

After the chaos of Python 2to3, backwards Python's backwards compatibility has been amazing. The tool is created for developers and claims 100% code coverage. Determining if it works with any specific version of Python would be a trivial exercise of clone the repo, make an venv, and run the tests.

This is something that a dev should do when evaluating a new dependency even when it claims to support the version relevant to you. Sadly, many do not.

Below what you quoted

> doit core features are quite stable. If there is no recent development, it does NOT mean the project is not being maintained... The project has 100% unit-test code coverage.

You assumed the issue relates only to compute costs. Even with a small payload, bandwidth fees can add up quickly when millions of clients are polling.

> I assume some many continue to exist but employees will also have to get used to large pay cuts if that's a hard requirement for them.

Some companies are losing their more experienced employees when they force RTO. If they want to compete for this portion of the talent pool, they'll need to offer more than the other remote first companies.

You don't need to go back to a golden era. My last in person job had kegs on tap and a beer fridge. Many offices had liquor bottles. I drank drastically less when I went full remote.

I'm assuming you view that as a good thing for open source projects. Without a large, free platform like GitHub, many open source projects would not exist.

There are other source hosting options, but people don't want to host their own, pay to host their project, email patches, or create an account for every project.

I'm intentionally ignoring any of the sarcasm in your comment. The time needed for a db dump is always dependent upon the amount of data. This is true regardless of the db software or where it's running.

I can't speak for Andrew, but my contributions to Takahe tapered off due to work killing my motivation to code after hours. It's also been feature complete enough for how I use it for many months.

The biggest missing feature that others want is identity migration. I hacked in support to get my identity migrated to Takahe, but it's not something releasable to the general public.

Prevention is always more impactful than treatment/reaction. It's still important to improve the reaction because prevention is rarely 100% effective.

It's such a small subset that it would more accurately be described as a scripting language with syntax similar to python for single file scripts.

Reach out to the group and see if you could lead a more casual run distance as part of their Wednesday run. The run groups I've been a part of were receptive to things like that. The more important aspect of the run was the general finish time and not the distance.

2) from my experience maintaining open source packages, many would report issues with little to no troubleshooting. A very small subset would look at the project code. The pedantic v1 code is not the easiest to digest. Changing v2 to rust will likely not have much of a change with regards to user reports.

I really dislike when links are to a blog post or page that doesn't have a way of navigating to the main site. Needing to manually modify the URL is enough of an annoyance on mobile that I'm more likely to bounce.

> I don’t understand how this is an issue that needs anxiety.

Empathy. Some people have more of it than others.

A person should be able to explain the code they're adding to a repo at the time they are adding it. Whether or not they can explain it at some arbitrary point in the future is a different question/issue.

Setting up an email server is easy. Having messages sent from that server and appear in other people's inboxes is very hard.

Google knows it's you if you did all of that from the same computer.

> Since you ended up here, you probably agree that Rust is potentially an ideal language for Game Development.

The name and domain are generic enough that I imagine most visits are "What is this?"

Hard to tell if it's purely for the clickbait or leaning heavily on shortening the title.