Docker’s secret that most “getting started” tutorials seem to miss is docker-compose.yml. Who wants to type these long-ass commands to start containers? I always just create a compose file, and then docker compose up -d.

Dockerfile is for developers, you shouldn’t need more than a docker-compose.yml for self-hosting stuff.

I use famous programmers. First Linux server was Torvalds, first mac was Woz, currently in service I have Kernighan (one of the inventors of C), KJohnson (Katherine Johnson was a programmer for NASA) and Shamir (The S in RSA).

A great point in favour of maps is that each iteration is independent, so could theoretically be executed in parallel. This heavily depends on the language implementation, though.

shove some text into stdout

That’s not what this operator does normally, and if you try to “shove” something into anything else (an int into a variable? a function into an object?) you’ll get surprises… Basically it’s “special” and nothing else in the language behaves like it. Learning hello world in C++ teaches you absolutely nothing useful about the language, because it doesn’t generalize.

C, in contrast, has many instances of complex functions like printf (another commenter mentioned variable arguments), and learning to call a function is something very useful that generalizes well to the rest of the language. You also learn early enough that each different function has its own “user manual” of how to use it, but it’s still just a function call.

this std::cout << "hello world" bullshit is in no way intuitive. You’re using the bit-shift operator to output stuff to the console? WTF? Why 2 colons? What is cout? And then these guys go on to complain about JS being weird…

No, C is where it’s at: printf("hello world"); is just a function call, like all the other things you do in C.

Meanwhile I actually studied computer engineering, but can’t legally call myself an engineer (yay Québec).

In most jurisdictions the protected title is “professional engineer”, but here it’s just “engineer”.

I disagree. Before I had to copy and edit a huge-ass script (100+ lines) in init.d where 80% of it was concerned with PID files. I just want to start a process on boot, why is it so hard?

Now I can look at the documentation and write a simple unit file myself. It’s like 4 lines.

I might’ve very well glanced over it, but the point is that I missed it when it’s probably the most important one. Why is it added when you do ctrl-f but not when clicking?

EDIT: Actually, it doesn’t show it until you actually type in the box:

It shows you all the filters except the one for the channel…

Having tried it, search is horrible. You have to look up the help to even know how to filter the search to a specific channel, by default it searches the whole server. I never managed to find anything, I had to ask again instead…

I use pancake, works pretty well. It’s paid, but only a one-time payment and you get the code.

EDIT: here’s the link: https://www.pancakeapp.com/

At the level I care about, which is “I want this daemon to start when I boot up the computer”, systemd is much better. I can write a ~5 line unit file that will do exactly that, and I’ll be done.

With init, I needed to copy-paste a 50-line shell script that I don’t really understand except that a lot of it seemed to be concerned with pid files. Honestly, I fail to see how that’s better…

Last time they charged for an OS update was with Mountain Lion, which was also the last “big cat” OS. That was in 2012, and it was only 20$. The last OS release that was over 100$ (or even 50$) was Leopard, in 2007, at 130$. Back then, the only way to get it was on a CD, which is obviously much more expensive to manufacture and distribute than a download…

I don’t bother correcting people if they think I’m a guy online.

There are no girls on the internet anyway ;)

For baseboard heaters, I have the Sinopé line of ZigBee thermostats, with home-assistant on my home server. Baseboards are kind of particular in that you have one thermostat per room, so at 350+ for a Nest, it’d be cost-prohibitive as I have like 15 thermostats in the house. Also, they’re line voltage, meaning that they directly switch the full power of the heaters, so they need to be well made.

I’ve had my Sinopé thermostats for 2+ years now, and I’m very happy with them. No clouds involved here.

I really like GL.iNET’s line of routers. They come with OpenWRT pre-installed, too!

I run my instance via docker-compose, and it’s just a matter of setting network_mode: host on the container (in the YAML).