matthewmercury

You are indeed very lucky. It sounds like your illness is well managed. Congratulations. For many people, their chronic illness is a great deal harder than yours, though you may find it hard to put yourself in their shoes if you haven’t suffered. Not everybody has a team to advocate for them, but perhaps you can’t imagine what that’s like. I thought I could offer a window into the existence of someone less fortunate, but I can’t gift you with the empathy to look.

I’m not trying to defend pharma ads, but: you probably don’t have a serious chronic illness.

If you had, say, rheumatoid arthritis, you would have probably tried a dozen different meds over the years in various combinations: Enbrel, Humira, methotrexate, etc. So if you saw a commercial for an RA medication that you know didn’t exist last year you’d take notice because this may be the one that finally lets you walk without pain again. You’re already scheduled to see your rheumatologist every 3 months because the medication you’re currently on is eroding your liver. Maybe you want to ask if this new med might be better.

I concur, you estupid

It’s because my job involves managing and operating systems that are only accessible through ssh or tty sessions. I spend hours every day in a terminal, on a remote session, frequently editing files for stuff: crontabs, configs, etc.

I learned vi because when I was coming up, university systems only had ed, vi and emacs, with pico on the servers that had pine for email. I learned vi because it was more powerful than pico (and because I couldn’t get the hang of emacs key combos). I read the help files and learned how to use it, because it was foundational.

Every Unix-like system has a variant of vi. Many of my container images don’t, but it’s trivial to install and use anywhere if needed.

It’s just a more powerful tool than nano, and consequently more difficult to use. Which is fine, man. It’s okay for you to use a basic text editor on the rare occasion you have to edit something in a terminal. You don’t have cause to learn how to be productive in an advanced editor, and that’s fine.

For what it’s worth, when I’m writing and testing python, I use VS Code.

See, you’ve realized your blunder, now. Tell us what editor you use in the terminal, ReCursing, the one that is better than vim. We’d love to know.

This is such bad reporting about cannabis that it makes me think The Atlantic probably has very poor standards for all their articles.

What’s the superior choice to vim, then?

Fwiw, I see Jack Black and Renee Elise Goldsberry for these roles.

Stockholm Syndrome was never real, it was made up to explain a situation where hostages recognized an injustice and refused to perpetuate it, so cops called them crazy. So sure, if you call me crazy for my affection for a tool that has served me well for decades, I’ll consider you a cop.

This sounds about right. My only quibble is about sick computers and web apps. Twenty years ago I felt good because all I needed was a text editor and a web browser. Nowadays, the hungriest apps on my desktop are Firefox and VS Code.

I use VS Code on the desktop nowadays, but vi will always be my editor of choice in a terminal. Many of the reasons it was powerful and ubiquitous 30 years ago are still valid, so it’s still powerful and ubiquitous. And I’ve been using it for thirty years, so why would I switch to a training-wheels editor?

Get a good dehumidifier with a drain hose option so that you don’t have to keep emptying the tank. It will produce some heat, so placement is important, but it will pull moisture from the air more efficiently than the AC and that will improve the cooling.