Tmux is basically perfect software. It gets right out of your way.
It'll never come out of my development stack, or workflows.
Writing code isn't everything. Almost every time I start an apt command or something that might run a little while, I regret it if I'm not in a tmux session.
When kids break the rules about screen time, there are consequences.
Not Dad fiddling with the settings, but instead Dad teaching a lesson about respecting the rules, and doing what you said you would do (children agree to obey the time limits in order to have access to the device).
How Dad should teach the lesson varies by family and by child.
I started last year. I had most of the tools already. I picked 90s ford trucks as my platform: cheap, plentiful, variety of models, known to be reliable, easy enough to work on with simple tools, parts still readily available, lots of YouTube material for any job I need to do.
I bought a couple and I've already had to do a lot of work.
It turns out, it's not that difficult. The systems are simple, each on their own, with few exceptions. When you isolate systems, you can just learn one at a time without pressure to be a whole mechanic. I still reserve the right to send it to the shop if needed.
I haven't had to rebuild an engine yet, but I've been all around the wheels, tires, axels, AC, fuel system, timing, vacuum lines, trailer wiring, brakes, coolant system, and of course I service all my own fluids.
I put it off way too long. My advice is to start now, if you think you'll like it. And you can start with mowers...a whole lot of the tools and concepts transfer.
That's true. And answers that seem obvious later, aren't obvious when you're young or less informed.
My personal example: I had to do a lot of research, distillation of sources, and so on, in about 2001, to figure out the answer to a simple question:
Can a person truly be a professional poker player--that is, be able to profit consistently in a proveable way, not some kind of lucky tournament win and then you masquerade as a pro--or is that a bullshit dream held up by a few desperate gamblers?
I recall it took about a week before I felt confident about my answer and I had to overcome my own bias.
You called them out for being slow; turns out they weren't. You called them out for un-merging your work; turns out they didn't.
Now you keep saying you had other bad interactions, but you haven't even said what they were. I have a feeling that if you named them, shortly later I'd read a comment about how it wasn't true. Again.
If the library didn't match your needs, that's fine. Who cares? That's happened to all of us many times, right?
I want them to report the facts, not their opinions.
Reporting that corporate called it attacks is good. I do prefer direct quotes.
However, when they quote one word, the journalists are inserting their own opinion about it. I want to make my own opinions based on the facts. I don't need the reporter to draw the conclusions for me.
Tmux is basically perfect software. It gets right out of your way.
It'll never come out of my development stack, or workflows.
Writing code isn't everything. Almost every time I start an apt command or something that might run a little while, I regret it if I'm not in a tmux session.
I could sooner do without vim than tmux.