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.

Donut regex when???

Does it do it well, though?

damn bleeding edge males

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.

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.

No problem! Actually, System76 is currently working on rewriting the COSMIC desktop in Rust (or really, just writing a new DE in Rust). It’s a pretty ambitious project that should hopefully get released some time this year. I wouldn’t be surprised if the lead redox dev was working on it too: low-level Rust knowledge is exactly what they need.

I love how simple and small scale splitting an atom sounds. Then you get to doing it…

Well, think microkernels as the bare minimum. They give you just enough to write your own OS on top of that: only the bare essentials run in kernel space, whilst everything else runs in user space and has to communicate with the kernel. Compare this to a monolithic kernel, like the Linux kernel: here, the whole operating system is run in kernel space, which means that data doesn’t need to be moved between user and kernel space: this makes the OS faster, but at the cost of modularity. Redox doesn’t use the Linux kernel, it uses its own microkernel written in Rust.

Edit: A good example would be driver. In a microkernel, these run separately from the kernel and interact with it when needed. In a monolithic kernel, these drivers would be included in the kernel itself. They both have their pros and cons: if you’re interested, feel free to look it up.

That’s fair. I started with what everyone was using at the time, which just so happened to be Neovim. I’m also too lazy to switch/try anything else.

Plus, I’m not sure if Neovim simply extends Vim functionality. I know it’s a fork, but the codebase has changed so much I’m pretty sure many newer features of Vim need to be manually added to Neovim. Inlay hints in the middle of lines is already implemented in Vim: as for Neovim, it’s not here yet (well, it’s coming in 0.10, but I don’t use nightly so I don’t have it)

I mean, I’d just bind vim to nvim. If you still want vim accessible, bind it to something else. I don’t really see any downsides to Neovim: it’s decently backwards compatible, enough to use most old plugins, with the advantages of Lua config and a much wider repository of plugins.

You are a nerd with too much time

Original Article

Basically, it’s just some cool X11 magic that uses a matrix transformation to rotate the screen.

The worst of both worlds…