Oh god. I still have nightmares about that time I had excel formulas in Portuguese, I refuse to think about SQL.

Really curious in what scenarios people would be writing enums with months and weekdays.

Because short of developing yet another library to handle date and time, everything else is likely a disaster waiting to happen…

Clearly, the answer is uuid.

Are they all your phones, or different house members? Can you “pool” your photos together?

We’ve been doing this with all our phones for a long time using nextcloud. I’d like to use a more photo-oriented app, but the last I tried it, it just wasn’t there yet.

Can’t rotate or do basic edits in web app, dead to me.

Also can’t really sync and share with rest of household. Auto sync to phones is also a must.

I was seriously unimpressed with its features, and I’m not bothering with it again anytime soon.

The elusive Chocolate Starfish.

This is the same approach as “add one more lane” to a congested highway. You know it’s not gonna work.

Just get a saucer.

This isn’t hard, you’re just trying to make it to be.

Memcpy from a file to a screen buffer is as much a UI as pouring water in a pot is a soup.

This.

Also, upgrade to Linux.

Really cool way of picturing an IP dataframe!

Like if you’re dropping it at a post office and praying it’ll get to where you need it to, which makes it rather remarkable that it actually does get there.

“This comparison appears to be unintentional”

I’m guessing that someone who figured out how to keep a high score box centered on screen using assembly will figure it out to do it with CSS.

The reverse, not so much…

deleted by creator

I’m ashamed to admit how many times a basic english spell checker in my IDE has saved my bacon.

I wholeheartedly agree that monopolistic practices should be nuked instantly, but I disagree that this was ever well enforced. Microsoft got away with murder in the 90’s before they went to court and even then, feels like they got a slap on the wrist…

I think that this particular case is very far from that, but it does start to smell the same.

In what world is assembly more readable or easier to understand?

Let’s Encrypt Expiry Bot just entered the chat.

But WHY are you trying to make a case for a bad practice? Don’t enable this kind of bullshit, please.

If there’s an error, don’t say it’s 200 OK. Give me something, a 4xx, or at least a 500. Sure, add all you want to the body, but respect the goddamn headers!

This fucks up so many things - starting right with API specs and documentation, s23 (or any other code this crap spits out) are not a part of the pdf file, which is the ONLY available documentation for this 3rd party service. If it serves any internal purpose, I have no clue, but for me it’s useless.

Log analytics is a mess, and you can forget about auto-generating a client, of course…

This is just a huge red flag for me, if their public interfaces look like this, I dont want to know whats under the hood, and I’m actively lobbying for us to change to another provider.

I may have run in your acquaintance work, stuff along the lines of

200 OK

{ error_code: s23, error_msg: "An error was encountered when performing the operation" }

If you happen to run into him, kindly tackle him in the groin for me.

Thanks!

Oh yeah, I remember using tortoiseCVS briefly.

Mercurial and Bazaar also showed up at around the same time as git, I think all spurred by BitKeeper ending their free licenses for Linux kernel devs.

An interesting shot to the foot, that one.

BitKeeper was a proprietary version control system that somehow (and with a lot of controversy) ended up being adopted by a big chunk of the Linux kernel developers, while others were adamant against it.

In any case, they provided free licenses to Linux devs, with some feature restrictions (including not being able to see full version history) only available for premium clients, while Devs who worked on open source competing systems were even barred from buying a licence.

When someone started to work on a client that allowed access to these locked away features, they revoked the free licenses, and a host of solutions started being developed immediately. Linus Thorvalds himself started work on git, and that eventually got adopted by the whole Linux ecosystem and, nowadays, the world.

As for BitKeeper, it’s been dead for years now.