Mercurial has comparable features (though maybe not obvious to someone accustomed to git) without the usability problems that still plague git nearly two decades later. Hg’s interface was made with humans in mind. Git’s was made to cut you.

(And it has cut so very many people that it’s consistently among the most popular topics in Q&A forums, and has even inspired comics.)

Thankfully, git’s early cross-platform shortcomings were eventually fixed, so that’s at least some progress. I hope its UI and docs eventually get some love, too.

I wish Mercurial had won.

deleted by creator

The interface is the best I know of, a lot like pre-Microsoft github. Especially important to me is that It doesn’t intercept my browser’s built-in shortcuts like github now does, or require javascript or bury things under submenus like gitlab does.

The promise of federation is appealing, too.

I plan to use it for new public projects, and might even move my old ones over.

disallow list of known bad email providers.

Imagine giving someone your phone number, and having them say you have to get a different one because they don’t like some of the digits in it.

I have seen this nonsense more times than I care to remember. Please don’t build systems this way.

If you’re trying to do bot detection or the like, use a different approach. Blacklisting email addresses based on domain or any other pattern does a poor job of it and creates an awful user experience.

(And if it prevents people from using spam-fighting tools like forwarding services, then it’s directly user-hostile, and makes the world a worse place.)

Checking MX in your application means you needlessly fail on transient outages, like when a DNS server is rebooting or a net link hiccups. When it happens, the error flag your app puts on the user’s email address is likely to confuse or frustrate them, will definitely waste their time, and may drive them away and/or generate support calls.

Also, MX records are not required. Edit to clarify: So checking MX in your application means you fail 100% of the time on some perfectly valid email domains. Good luck to the users and support staff who have to troubleshoot that, because there’s nothing wrong with the email address or domain; the problem is your application doing something it should not.

Better to just hand the verification message off to your mail server, which knows how to handle these things. You can flag the address if your outgoing mail server refuses to accept it.

By the way, please don’t write regex to try to validate email addresses. Seriously.

Amen.

There are libraries for that; some of them are even good.

Spoiler alert: Few of them are good, and those few are so simple that you might as well not use a library.

The only way to correctly validate an email address is to send a message to it, and verify that it arrived.

how discouraging
should have used an asterisk
not a comic book

https://en.wikipedia.org/wiki/Uniform_Function_Call_Syntax

These come to mind:

• Elixir to expand the way you think about problems (and maybe your career).
• D to bring familiar conveniences closer to the metal.
• C to understand (and maybe contribute to) a vast ocean of existing software.
• Python for development productivity.

Is this a proposal to make Nim compile to Assembly instead of C?

No, it’s for stuff that happens internally to the compiler.

https://en.wikipedia.org/wiki/Intermediate_representation

I’ve given up on Nim, though, because the creator / project lead is more than a little problematic, and I don’t think that can be fixed.

Perhaps Nimskull will develop into something useful eventually. For now, there are plenty of other languages to try.

I bought one during the clearance sale for the price of shipping, assuming that it would be abandoned but maybe still useful as a low-power linux server. I guess I ought to set it up and take advantage of it.

Thanks, Valve, for not letting these things become instant e-waste.

“Systems that break email already exist, so let’s add more to the world.”

Please, no.

My (least) favorite in this category is email addresses. It’s astonishing how many developers screw this up by trying to validate an email address by some means other than sending a message to it.

My understanding is that it got a big surge of users at a time when it wasn’t really intended for the public, and is now having growing pains.

C++ was my language of choice for a long time, but I can’t say I’m with you on this one. If I’m going to use Vec, I had better know what it is already. Littering the code with a special double-glyph operator when a dot would do is just needless noise to me.

(I won’t criticize you for liking it, though. Cheers.)

I’ve seen an argument that defederation would just hurt the fediverse, and that even an exploitative giant like Meta should therefore be welcomed.

I think that’s like arguing that we should get rid of antitrust laws, which we have for good reason.

As a policy, it’s bullshit. But here are the relevant sources:

https://en.wikipedia.org/wiki/Never_trust_anyone_over_30#“Don’t_trust_anyone_over_30”

https://en.wikipedia.org/wiki/Logan's_Run_(film)

I would expect any random headset to plug into the headset and microphone ports and Just Work, and ditto for USB

For the most part these days, they do. But OP asked about wireless.

or Bluetooth headsets that report themselves as the appropriate device class.

The problem with Bluetooth is not the operating system or drivers, but Bluetooth itself. The spec famously lacks provisions for good quality stereo output with good quality input at the same time. This is why many wireless headsets use a (non-Bluetooth) dongle.

I’m a fan of static site generators, but unless I’m missing something, this won’t replace the most important part of Bandcamp: a platform for selling music.