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.

he’s gone off the rails in the last 6-12 months - complaining about needing more linux devs

It’s also ironic in light of his history of loudly bashing linux and linux game development.

I can’t think of anything good to say about Tim Sweeney.

I might give Backpack Battles a try. It doesn’t look like my usual style, but I heard there’s some good strategy under the surface, and I like that it’s made with Godot.

Are there any 5.5 physical sourcebooks? Were they ever planned at all?

I haven’t been following One D&D news, but I got the impression they were focusing on a subscription-only model, so I’ve been planning to stick with my 5e books or switch to an ORC-licensed system.

how discouraging
should have used an asterisk
not a comic book

After decades of license strangleholds by the likes of MPEG LA and Microsoft, it’s refreshing to see open codecs adopted in mainstream hardware and APIs. Hooray for progress!

I just learned about that as well. I hope Larian dilutes or buys back Tencent’s shares.

I struggle to think of a buyer that would be worse for the players than Tencent.

On the bright side, Hasbro’s last big D&D blunder prodded the community into developing alternative gaming systems and licenses, so I think we’ll be in good shape to carry on without the brand if this happens.

Booming Blade’s damage scaling is the same as Toll the Dead, but with a smaller damage die.

However, since its effect depends on a weapon hit instead of the elf spellcasting ability (intelligence), I suspect it will proc more often than Toll the Dead for most melee Fighters. Seems like a good choice if you want to your cantrip to be for combat.

On the other hand, since a fighter has plenty of weapons for doing damage, you might consider picking a utility cantrip instead. How often you use it would depend on your play style and DM, of course, but in my experience, all it takes is a little imagination to get tremendous value from utility cantrips.

Here are someone else’s thoughts on the wizard/elf cantrips. Keep in mind that they’re probably considered in the context of a wizard casting them, rather than a fighter, but the points noted there are worth considering regardless.

It’s written correctly. “All but” in the sense used here means almost. “All but certain” means a hair’s breadth from absolute certainty.

(Also, “lose” is the word you were looking for; not “loose”.)

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.

So with normal use it should be fine for a few decades.

Considering that “normal use” can be so very different among different people/applications/climates, I don’t put a lot of stock in assessments like that, but it is at least one prediction to compare against when we see what happens in practice. Time will tell.

I’m curious how long the current gen OLED consoles will be in use before they develop screen burn-in.