Trailing slash lets you do this though:

For example, in the case of <div/>Some text, browsers interpret this as <div>Some text</div>, treating the slash as ignored and considering the div element to encapsulate the text that follows.

Don’t see it. Could somebody give me a pointer?

Also, researchers asking ChatGPT for long lists of random numbers were able to extract its training data from the output (which OpenAI promptly blocked).

Or maybe that’s what you meant?

I’m both, I say fuck all the time. I fuck on and off the clock.

On the other hand, TAI does not take into account the variations in Earth’s rotation speed, which determines the true length of a day. For this reason, UTC is constantly compared to UT1. Before the difference between the two scales reaches 0.9 seconds, a leap second is added to UTC.

On average, Earth has been slowing down a bit over the past decades, so UTC is currently running 37 seconds behind TAI.

The Earth is a sphere, which means there’s no easy way to project it onto a flat surface. One of the methods used to project the Earth’s surface on the map results in certain places (such as Greenland) to be stretched to huge sizes, sometimes appearing as big as Africa (look up “Mercator map”). The joke here is that while we expect him to make a comment about the map’s projection, he instead comments on how Greenland on the physical map is only a few inches, as opposed to its actual size.

So yeah, subverted expectations, peak Dad joke

Donut regex when???

Does it do it well, though?

damn bleeding edge males

Whose firstborn child stubbed his toe on the rock well over 542 times, leading to the renaming of it to “Fuck Rock”.

I did this with many languages. Spoke Hindi, but convinced people I could speak the other related languages (Telegu, Marathi, etc.) by just saying random things in my little fake accent. Usually ended it with some small “sharp” words (like “tittu”, just sounds “sharp”) to really sell it.

First guy looks really happy he forgot the BBQ tools.

AI’s not bad, it just doesn’t save me time. For quick, simple things, I can do it myself faster than the AI. For more big, complex tasks, I find myself rigorously checking the AI’s code to make sure no new bugs or vulnerabilities are introduced. Instead of reviewing that code, I’d rather just write it myself and have the confidence that there are no glaring issues. Beyond more intelligent autocomplete, I don’t really have much of a need for AI when I program.

I’ve got to know: where’s the video?

They’re both pretty on par for the most part. If it’s too much of a hassle, there’s no real need to switch.

Now that Gitea is owned by a for-profit company, people are afraid that they’ll be making anti-user changes. This, Forgejo was born. It pulls from Gitea weekly, so it’s not missing anything. It’s also got some of its own features on top, but they’re currently pretty minor. Also, most of the features end up getting backported back to Gitea, so they’re mostly on par with each other. However, many features find themselves in Forgejo first, as they don’t have the copyright assignment for code that Gitea does. Additionally, security vulnerabilities tend to get fixed faster on Forgejo. They are working on federation plans, however, so we’ll see how that pans out.

Overall, there’s no downside of switching to Forgejo, and you’ll probably be protected if Gitea Ltd. makes some stupid decisions in the future. However, at the moment, there’s no immediate advantage to switching, so you can stick with Gitea if you’d like.

It’s very much intended. Cinnamon was forked from GNOME 3 when it was released. It was intended to preserve the old GNOME 2 layout, but ended up evolving into the Cinnamon we know today.

National Guard listens to the state by default, as each state has its own National Guard. However, the federal government can intervene at any time and give them new orders.

I guess they’re just choosing not to do anything? IDK.

I mean, in extreme lag scenarios it’s more useful, as hitting three keys and waiting is easier than trying to guess where the mouse cursor is as you try to hit the icon.

In cases where you’re already typing (personally, most of the time) it’s more convenient. As many of us are programmers here, it’s quite annoying to switch between keyboard and mouse all the time, and keyboard shortcuts allow us to be much Fmitt efficient in our work. (I mean, I use Neovim now and I’ve never worked this fast and smoothly).

Of course, I know nothing of how you use your device, but generally keyboard shortcuts are preferred to clunky mouse interactions.

This advice is so beautiful, it makes me want to jump off a bridge.

Commit more often. Maybe work in a different feature branch, and don’t be afraid to commit your half-working crappy code. If it’s a personal project/fork, it’s totally acceptable to commit often with bad commit names and small unfinished changes: you can always amend/squash the commits later. That’s how I tend to work: create a new branch, work on the feature, rebase and merge (fast forward, no merge commit). Also, maybe don’t jump around working on random features :P