> The ~foo as backup convention is not part of any standard.
Emacs does foo~ by default, not ~foo.
In either case, you're not really supposed to edit files in sites-enabled. That directory is expected to contain symlinks to files in sites-available. I'm not going to say with any certainty that one of the reasons for this indeed is that the pattern (which was used by apache as well - and perhaps other things before it) protects against accidentally reading backup files, but it's not impossible.
So there's definitely a case of holding it wrong if you end up with backup files in that directory.
I liked doing symlinks so the site configuration is with the rest of the site, but that was before containers when it was common to host a bunch of sites on one instance apache or nginx.
No. PyPy development was ongoing long before the first release. The first intact commit in the PyPy repo is from February 2003: https://github.com/pypy/pypy/commit/6434e25b53aa307288e5cd8c....
And that commit indicates there's been development going on for a while already. The commit message is:
"Move the pypy trunk into its own top level directory so the path names stay constant."
PyPy migrated from Subversion to git at some point. Not sure how much of the history survived the migration.
> Even just among devs, even just among devs who truly love programming, most would be doing very different work, and working for different organizations (or none at all) if money weren't the driver.
Somehow I can imagine that a world where a the brightest minds of a generation didn't spend their prime optimizing ad clicking wouldn't necessarily be a complete disaster.
Optimizing ad clicking is profitable and the thing that would [partially] pay for UBI. That stops happening and money/value stop being created. The market is not 0 sum.
It's good to talk about UBI, but people taking it seriously have no idea how to fund it.
ChatGPT has too many users for it to be possible to enforce any kind of rules consistently. I have no opinion on whether OP's story is true or not, but the fact that two ChatGPT users claim to have observed conflicting moderation decisions on OpenAI's part really doesn't invalidate either user's claim.
> Or just a long black expressed in a complicated way?
Presumably this. Coffee terminology is (apparently) not global. I've never seen the term "long black", and I visit cafés quite a lot. Wikipedia lists it as a thing primarily in Australia/New Zealand.
I'm such a user. Been mostly running on debian/stable since the 90-ies. At work and privately. I cheated when I got a new computer in the beginning of August this year and installed Trixie a couple of weeks before release.
My reasoning is quite simple: I really don't need the latest versions of everything. Were computers useful two years ago? Yeah? OK then, then a computer is obviously useful today with software that is two years old. I'll get the new software eventually, with most of the kinks ironed out. And I've had time to read up on the changes before they just hit me in the face.
Sure, it was a bit painful with hardware support some twenty years ago or so, but I can barely remember the last time that was an issue.
For the very few select pieces of software where stable doesn't quite cut it there's backports, fasttrack and other side channels.
Emacs does foo~ by default, not ~foo.
In either case, you're not really supposed to edit files in sites-enabled. That directory is expected to contain symlinks to files in sites-available. I'm not going to say with any certainty that one of the reasons for this indeed is that the pattern (which was used by apache as well - and perhaps other things before it) protects against accidentally reading backup files, but it's not impossible.
So there's definitely a case of holding it wrong if you end up with backup files in that directory.
reply