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. 😬

Welp. Shit.

Thankfully Linux still yas Linus who seems to be a simple guy who doesn’t jump on hype trains. But there will come a day when he either no longer wants to deal with the responsibility, or he passes; in both cases, we will have to hope that whomever takes the reigns doesn’t pull a Tim Apple approach to management of the Linux ecosystem.

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

Thank you for confirming what I said. 😊

This may or may not help, but here’s my two cents:

Windows was originally built to be as user-friendly as possible because its target audience are non-tech-savvy people. It then evolved into being a business OS. So security was never its first priority.

UNIX was built for tech savvy people to do business-sensitive stuff, and required sophisticated security models. Linux was modeled after UNIX (Minix specifically), and thus inherited those same principles. It evolved to become more user friendly. But security remained a priority.

Now, that said, both Windows and Linux are configurable. You can make Windows more secure with effort, just like you can make Linux less secure with effort (and I don’t mean simply using root all the time).

There are diehards on both sides , and they will make excellent (or terrible) arguments for their favored OS. So you need to decide what works best for you and your use case and go with that. 😊

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.

So I’m clear, are you referring to the @layer CSS at-rule? Or, something else?

You’re absolutely right. My idea is to imply that developers should give their semantics actual thought and intention.

For your example, the X button can be called .dismiss, since typically that’s what clicking the X does; whereas cancelling something may have more meaning (e.g. cancelling a subscription, which triggers other actions aside of dismissing a modal window).