The issue this is referring to is because the user cannot paste into a text field. And the user was not rude about it either.

So instead of fixing the actual problem, the developer went nuclear and removed the validation. A dick move in my opinion given the developer’s attitude.

~It’s more sad than funny. 🤷‍♂️~

It was down earlier today. Came back up right around when I posted this.

It’s all subjective and based on your personal level of interest. From a technical standpoint the time needed is based on how fast your computer can compile everything, how fast you read and understand the instructions, and how much effort you want to put into it.

So yeah, a weekend could be reasonable.

Or they’re bored. I’ve done Linux From Scratch before. It’s fun. It’ll teach you a lot about building and maintaining a distro.

Do it. Take a weekend, and indulge yourself.

Ahem.

That just made this 1000x funnier. Thank you!

Oh god. That is so me. Always with the “if only” mentality. If only ________ then I could do ________.

And of course, it never gets done. 😅

This is the equivalent of a woodworker building jigs and other tools with their thousands-of-dollars of equipment.

Source: me. I do this. 😬

The point isn’t whether it’s needed or not. It’s not about space or features. The point is that a major player made a design decision and bucked the system. And while there may still be some phones with audio jacks, the majority of mainstream phones don’t. That major player is still successful, and other companies followed suit.

Can we agree this is what should happen to HDMI. No?

🤦‍♂️

There would be uproar, but like the audio jack on phones people would come around. All it would take is one big enough company to pull it off, and the rest would follow.

This wouldn’t work to scale. If Valve paid to license the spec for the Linux kernel, it would have to pay for every person who downloaded the driver, which is far more than the amount of people who buy the Steam Cube.

Unless of course you’re suggesting that the kernel driver for the new spec become closed source.

If you haven’t already found it, you need to change your global git config (~/.gitconfig):

git config --global init.defaultBranch main

(or whatever you want to call it; e.g. daddy would work too)

For any existing repositories you want to run the following command in the existing repository root (./.git/config):

git config set init.defaultBranch main

When I see these generation-hating comments — specifically older generations hating on something the younger generations do — I can’t help but think about whose fault it is for whatever slight the older generation feels.

Who created digital clocks? Who created iPads and iPhones? Who created video games? Every single generation has their own slang that each previous generation fails to understand (not because it doesn’t make sense, but because the previous generations are too lazy and/or stubborn to learn).

/soapbox

I put my ticket numbers in my tickets, but i also try to describe the change too (e.g. “Fix bug where xyz happens due to zyx action”). Also, atomic commits: commit only related changes.

Yes, it takes longer to commit large changes, BUT you can easily merge the commits, and rollback only what needs to be rolled back.

Git commits with message saying “pushing changes” and there are over 50 files with unrelated code in it.

So is /dev/null.

If you have an evening (or all weekend), and really want to blow your mind, look up Low Byte Productions on YouTube and look up their JavaScript videos.

Here’s how I approach old and slow:

1. Older software is mature and battle tested. It’s been around long enough that the developers should know what they’re doing, and have built a strong community for help and support.
2. Slow is okay when it comes to accuracy. Would I love to back up my gigabytes (peanuts compared to some of you folks out there with data centers in your attics) in seconds? Yes. But more importantly, I’d rather have my data be valid for if I ever need to do any kind of restore. And I’ve been around the block enough times in my career to see many useless backups.

I believe it was more because in database terminology there were masters and slaves for replication. Version control came under fire soon after.