Yeah, you use whichever you want and just worry about it less.

Go to their GitHub and look at issues and their comments first.

I’m currently doing this with an angular project that’s a bit of a clusterfuck. So many layers.

I’m still having to break it down into much, much smaller chunks and it’s not able to do much, but it is helpful. Most useful thing was that I started with writing a pure SQL query with several joins and told it “turn this into linq using existing entities”.

I think they’ll completely replace ORMs.

Part of it is cultural and habit and that is something you can just decide to change. It helps if someone brings it up, like this post, or you might not even think of it.

I bought a $10 power strip / surge protector last week. It was the first time this occurred to me. I pulled out the manual to throw it away, and it was only my experience in writing technical documentation that made me stop and consider actually reading/skimming it.

Maybe I’ll change this habit. Maybe I’ll start reading these things.

Of course some of them aren’t meant to be read. But you can usually tell pretty quickly,

Doesn’t xmpp require a constant connection?

Looking at and/or incorporating Navidrome might be helpful.

At least for the first year.

Sometimes you even get to show off the cool, useful shit you built for them!

Sometimes I’ll copy paste the error message back to them. Apparently it works better when it’s in a text message.

Rust is straight up better than C. It’s safer and less prone to errors.

It’s not feasible to convert the entire Linux codebase at once. So your options are to either have a mixed codebase, or stick with effectively Cobol into 2020.

It’s not impossible. There are a lot of crypto grifters who have been prepping to scam the American government.

I realized immediately, read the comment, and then went back to look for a deeper meaning. It wasn’t there.

I realized immediately, read the comment, and then went back to look for a deeper meaning. It wasn’t there.

Also, do we just trust all these random libraries? Not just about malicious code, but also what kind of quality/usability are you including?

Big companies do not want to trust open package repositories. They attempt to take countermeasures (but how much can you do?)

The huge benefit of the standard library is that I can always trust it, and it will always be the idiomatic way to do things.

it was easier to reinstall than it was to figure out how I broke it in some new novel way.

I came to the same conclusion. But I couldn’t get it to reinstall. It kept wanting to use the old partition. (2001, maybe Ubuntu?)

So I knew how to solve that. If the linux installation is wiped, then it’ll surely allow me to reinstall fresh. So,

rm -rf /

Begins deleting files…

“Wait, my Windows partition is under that, isn’t it.” Ctrl+C frantically, it won’t stop. Pull the plug.

I did get my files back. Just, you know, without file paths or file names. Do you know how many DLLs and worthless text files there are, by the way?

At the time, everything HTTP was supposed to be public.

Especially on mobile.

Mumble is another strong, open source, self-hosted option.

you really shouldn’t be using variables with the same name but different capitalization in the same sections of code anyway.

It’s a standard convention. Notice step #3 here: https://scottlilly.com/learn-c-by-building-a-simple-rpg-index/lesson-08-1-setting-properties-with-a-class-constructor/

Edit: Step #4 is a different standard convention that also applies here.

It turns out that the easiest thing to program isn’t always the best application design.