Ive used it when I’ve found myself completely stumped with a problem, and I don’t know exactly how to search for the solution. I’m building a macOS app, and unfortunately a lot of the search results are for iOS — even if I exclude iOS from the results (e.g. how to build a window with tabs (like safari tabs), but all results comes up for iOS’ TabView).

My conspiracy theory is that AI is already running our tech companies, and that’s why everyone and their brother is pushing hard for AI integration, despite everyone knowing AI is nowhere near ready for public consumption.

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

I imagine the better argument (in my opinion) would be to not use generic names such as btn, as they are redundant and offer little self-documentation of their use.

Instead, I believe a combination of selectors and classes would be more meaningful, and encourage readability. For this particular scenario, I would go with a button selector to give all <button> tags a consistent basic styling, and use aptly-named classes like .cancel, .primary, and .destructive to add more styling for specific button purposes.

Then if I need to find all Cancel buttons, I can use a button.cancel query selector and only get Cancel buttons.

Learn CSS layers, use CSS layers.

What are CSS layers? I’m legitimately curious.

I once interviewed at a company that bragged about not using version control or FTP, and how everyone made their changes in production.

~I’m so very glad I didn’t get that job.~

Donkey Shame!

I do understand what blockchains are; my question is more to whether they are used outside of cryptocurrencies or not.

~I do also like your explanation.~

So I’m clear, does blockchain always refer to those *coin currencies? Or is it be used for other purposes too?

I’m going to try to replicate as much of Postman as I feel is useful - minus the AI crap and the whole third-party cloud services. I do plan on using iCloud for personal storage, and I’m thinking GitHub for team sharing (admittedly, that feature is a ways off, and I’m open to suggestions).

I’m using SwiftUI to build the app. I think once I get a stable macOS version, I might do an iPad version too.

I’m making my own version of Postman, but with Blackjack and Hookers — and for the Mac.

So basically Swift on macOS, except this made much more sense. 👍

But only for certain classes of people.

Codeberg is not just for static websites. It’s for FOSS projects. Their FAQ addresses this.

Changing the original intent versus submitting patches?