What's the long-term game-plan for "smart" / connected appliances? My Whirlpool refrigerator was left by the previous owner when I bought my house in 1993, so it's at least 32 years old, and we got our Kenmore washer and dryer in 1993. All three still run great. On a related note, my 2001 Civic and 2002 CR-V are still running well. Thankfully, none of my appliances/cars have this crap. Are companies planning on supporting these "smart" / connected features and touch screens for 30+ years? History so far says nope.

Yup, 'cause the Taliban is known for giving up easily and being lenient to people breaking morality decrees. /s

Related Rick and Morty - er, Summer ...

So, just close your eyes and think of Erlang -- or something like that? :-)

Fast, good, cheap - pick two.

Or, hire another programmer.

And... Trump gets editorial control and preferred feed placement, Pam Bondi gets warrant-less access to all user data, Stephen Miller gets control of (shadow) banning people and Karoline Leavitt is in charge of "fact checking" ... And JD? Nothing, no one likes him. :-)

The answer is another question: Better for who?
If Trump had his way, there would be no data from anyone, just his say-so -- and we can all imagine how that would go...

In this case, you both may be correct.

Won't a lot of space be taken up by the signs (or stickers) labeling it "lab-grown coral"?
Surely ocean life deserves the right to choose between natural and lab-grown... :-)

I know this was modded Funny, but actually... There were a few stand-alone Awk scripts in that project, but most Awk usage was smaller/simpler calls from Bash/Ksh scripts. I do routinely use awk one-liners, even on my systems at home.

Perl has been my go-to scripting language for a long, long time -- since the '80s. And knowing it means I don't have to use Python. :-)

It's good tool for a lot of things, but just one of many. On the last large cross-platform (Windows, Solaris, Linux) project, I used many different languages: Assembly (x86), Bash, C, Cmd, Java, Ksh, Perl, Postscript, PowerShell, Python, SQL, Tcl/Tk, VBScript -- whatever was best for the particular task on the particular platform. That said, using Perl often allowed the same script to be used across all platforms instead of similar scripts in different languages.

And... Emacs. (yes, I'm old) :-)

Well... Some people will be surprised.

Bet they don't have cool names like Alligator Alcatraz and the Speedway Slammer. /s

Any bets on if that "unspecified cybersecurity agency" was the one actually doing the hacking and it's a 3-letter agency? [Not UCA :-)] /CrazyNotCrazy