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.

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?

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.

Lazier way:

:w !sudo tee %

Does it do it well, though?

Maybe I’m just lazy, I’ve only invested 10-15 hours total into my config.

Once I got it working, I’ve never bothered to really even touch it. (I probably should, it’s most likely months of out of date…just like my NixOS config…)

Next time I make changes will probably be when I update to 0.10 for inlay hints and set that up along with attempting to fix that error message that randomly pops up every time I start Neovim.

Also probably not the typical Neovim config experience, but I’ve configured it enough to get of my way, now I just want to write code.

For an artificial supreme intelligence, it sure does suck at spelling.

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.

You should try it. Quick and easy way to get some fresh air…

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.

Let me guess: Hannah Montana?

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.

It’s surprisingly possible (and easy) too… a little bit of tinkering with X11’s compositor API would probably do the trick.

IDK about Wayland tho :/

LMDE and PopOS are my consistent recommendations to newcomers. If one doesn’t work, the other will.

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.

Original Article

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

IDK, I exit vim and promptly fall asleep.

The worst of both worlds…

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