I was a happy perl user for a long time, probably until sometime in the early 2010s. I am a sysadmin and perl was a great tool for what I needed to do.
Jim Weirich was a heavy perl user for a long time, and we were both involved in the Cincinnati perl mongers group. He found ruby and fell in love. He thought Ruby would be a good fit for me and we had a long conversation about why he preferred it to perl. It took me a few years, but I eventually took his advice. As usual, Jim was right, and I haven't written any perl since then.
> No Effect from Legalization: The rate of drivers who tested positive for THC did not change significantly before or after legalization (42.1% vs. 45.2%), indicating that legal status did not influence the behavior of those who chose to drive after use.
Ohio recently passed a marijuana decriminalization bill.
I had some containerized application software break and start misbehaving in odd ways which was indicative of a deeper incompatibility issue. Possibly GPU related. No time to debug, had to roll it back.
This was complicated by the fact that the machine also hosted a MySQL database which could not be easily rolled back because the database was versioned up during the upgrade.
Wait, the containerized application broke because of a host upgrade? That's some leaky container you have there.
This sounds like a business setting, so this sounds like a good opportunity to advocate for testing hardware, a testing budget, a rollout plan, and a sound backup strategy.
My experience as a long time Linux user (since 1997, so admittedly stuck with some bad habits from when things were actually hard to get working) has been that things are kind of confusing if you deviate from the golden path, but if you are on the golden path you won't ever notice that it is turned on.
The laptops I have gotten from eg Dell with Linux pre installed have just worked. Machines I have upgraded through many versions of Ubuntu (lts versions of 16-24) were weirdly broken for a while when I first turned secure boot on while I figured it out, but that seemed reasonable for such a pathological case. Machines I have installed Debian on in the last few years have been fine, except for some problems when I was booting from a software raid array, but that is because I was using 2 identical drives and I kept getting them confused in the UEFI boot configuration.
I have not used them on machines with nvidia, vbox, or other out-of kernel-tree modules though.
Wow, I thought for sure they would have retired it by now. I remember having a birthday party there when I was a kid (90 or 91?) and thinking that it was the coolest thing ever. It made up for them not moving the planetarium from their old location when they moved the museum to Union Terminal, which I (at 9) recall making me really sad.
It has had a digital retrofit (no more giant reels of film paying-out into the projector to watch while in line for the next show) but is otherwise pretty much unchanged.
We took a "behind the scenes" your years ago and got to see the projection dome from the outside. That was pretty freaky.
We use them for a few dozen domains. DNS only, though, and they are all set to auto-renew.
I basically only have to interact with them when we need to make DNS changes. The web UI seems fine, especially in the advanced view, but our biggest zones are managed through opentofu, so I can see how changing a large zone would be frustrating.
I don't think that one was ever "acceptable". That being said, literally every term after/including "African-American" in that list is socially acceptable. Not sure what they're going on about.
I'm not so sure. It sure gets used a lot in "Huckleberry Finn", even by people who aren't being malicious. (From my recollection, anyway. It's been ages since I read it.)
Jim Weirich was a heavy perl user for a long time, and we were both involved in the Cincinnati perl mongers group. He found ruby and fell in love. He thought Ruby would be a good fit for me and we had a long conversation about why he preferred it to perl. It took me a few years, but I eventually took his advice. As usual, Jim was right, and I haven't written any perl since then.
tl;dr: for me, ruby killed perl.