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.

Donut regex when???

damn bleeding edge males

First guy looks really happy he forgot the BBQ tools.

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.

You are a nerd with too much time

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.

I thought it was TS/JS too, but the way those braces are below the if statements makes it feel more like C#.

And maybe he published it on GitHub?

That’d be funny. Seeing mass-repo-creator and then 4000 random repositories below it.

The Voyager post says “0 comments”, but there’s a comment clearly visible at the bottom(of the voyager screenshot).

/s

I have an exercise joke, but it doesn’t really work out.

And it has 333 upvotes! We must maintain this at all costs…

Alternatively, you can save a key and use :x (And :q! to quit without saving)

Yeah, that’s such a Vim user thing to say :P

Remember kids, always use protected branches.

To steal the top comment on that video: “That’s what the compiler does. It takes .c files and turns them into .o files.”

An independent and unique individual. Who cares what others think? You do what you do.

It’s actually a common misconception. Here’s a good article which debunks that. TLDR there’s no true historical evidence that this ever happened.

Probably more software dev.

I originally got it for some robotic projects, but ended up not needing it. Thought maybe I could put it to good use, so here I am.