Jim

Yes it can be an issue because the GPS doesn’t know where you are and thinks you are on an aboveground street. Freeway tunnels can have multiple exits too.

Yep, this is the convention. Unfortunately, I’ve never been able to enforce it. Encouraging good git commit messages is probably the bottom of the things I can coach. I’d be happy if commits were properly squashed/rebased and that we all followed the same PR merge strategy.

Rocky Linux have said that they can rebuild using publicly available sources in UBI containers and cloud images.

https://rockylinux.org/news/keeping-open-source-open/

Though reading the article, I don’t know if SUSE is simply rebuilding or forking. In any case, it’s cool to see SUSE committed to open source principles.

I think Tumblr’s brand just got ruined. They were known for their nsfw material and now they don’t know what else to do with their lack of users.

"I can read this Perl scrip"t should translate to “I’m lying”.

Yes but karma makes it worse. It incentivizes getting getting upvotes because you don’t want to “ruin” your karma. Expressing controversial opinions, even if they don’t generate downvotes, are discouraged with karma. Even OP says he gets a dopamine hit by seeing the karma number go up.

I don’t like karma. It incentivizes short, meme-y posts since those are things that get gets a lot of karma.

Totally agree with the dope domain name. Not going to lie, a big reason for picking programming.dev was to be /u/jim@programming.dev

It’s not about what it is today but what it can be. I agree that there are a bunch of problems, but the future does look bright.

I think you’ve succinctly described what I hate about GPL. I could never put my finger on it except that it’s a pain the butt.

Story time:

There was a long data pipeline that produced wrong results. The wrong results were subtle but reproducible. Each run was about an hour long in dev, and there was no intermediate data set. It takes some input, runs for an hour, and produces an output.

The code was inherited and was a bit of a mess. Instead of digging through the code, I re-ran the pipeline through from about 6 months ago when we knew there was know bug. It was about 100+ commits since that time.

Mind you, the bug could’ve been anywhere in the codebase as far as I was concerned.

Took about a day of git bisect to narrow it down… to nothing. I found out that running code from the first commit from 6 months ago also produced incorrect data. Oops. That’s weird though because the code was running correctly back then.

A few days of debugging later, and I eventually found the culprit: a dependency package got bumped a couple weeks back. Some sort of esoteric parser had a bug but didn’t fail. It incorrectly parsed some data after the bump. Going back a version fixed the bug.

So yeah, git bisect killed about a day of my time.

Lots of people here lamenting about this. But the truth is that good code is easy to modify/delete.