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

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

Lazier way:

:w !sudo tee %

Donut regex when???

damn bleeding edge males

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.

First guy looks really happy he forgot the BBQ tools.

I mean, it will be. The AI friend is always available, always knows what to say, never fights with you, and never messes up (ideally).

However, all those things are part of the human element: and at the end, you’re still talking to a computer. The AIs are just trying to please you. A person can actually love you, and that’s something else. And I’d take that over the perfect chatbot any day.

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

Honestly, this is why I’m hoping the Vsuon Pro doesn’t flop. It really feels like it could open the door to a new era. Of course, that’s still years away, but you’ve got to start somewhere. Better now than never.

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.

Let me guess: Hannah Montana?

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.

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

IDK, I exit vim and promptly fall asleep.

I’ll point to how many functional languages handle it. You create a type Maybe a, where a can be whatever type you wish. The maybe type can either be Just x or Nothing, where x is a value of type a (usually the result). You can’t access the x value through Maybe: if you want to get the value inside the Maybe, you’ll have to handle both a case where we have a value(Just x) and don’t(Nothing). Alternatively, you could just pass this value through, “assuming” you have a value throughout, and return the result in another Maybe, where you’ll either return the result through a Just or a Nothing. These are just some ways we can use Maybe types to completely replace nulls. The biggest benefit is that it forces you to handle the case where Maybe is Nothing: with null, it’s easy to forget. Even in languages like Zig, the Maybe type is present, just hiding under a different guise.

If this explanation didn’t really make sense, that’s fine, perhaps the Rust Book can explain it better. If you’re willing to get your hands dirty with a little bit of Rust, I find this guide to also be quite nice.

TLDR: The Maybe monad is a much better alternative to nulls.