> nobody needs or wants a unix shell account in this day and age
> I do. But I do not need just any Unix shell account, I need old and weird ones! I develop and maintain a portable utility (rlwrap) that is aimed at users of older software
Thank you, personally. I've used it in several contexts not just old systems, for example rlwrap is recommended with Clojure (okay, perhaps that's a comparatively small audience).
+1. I switched to using Nushell as my daily driver around mid-2023 (0.84.0?) and use it in preference to other interactive tools. I do keep at hand jq, yq, and mlr because I need to exchange stuff with colleagues who don't use Nu.
> I know there are industrial processes where heat is efficiently recycled, but I agree there are serious practical problems, particularly if the molten glass must be cooled quickly.
My experience working with glass is that you _don't_ want it cooled quickly. It will shatter or get internal stresses that cause it to shatter later. You anneal it in a slowly cooling oven over time. Some steels and brass can be annealed slowly and that heat could, I suppose, be captured. Tempering probably not.
> Still, even somewhat lower grade heat can be upgraded back to high grade heat with high temperature heat pumps.
Which requires energy and incurs losses. If you have energy, assuming electricity, that's cheap enough to scavenge low-level waste heat you probably don't need to recapture the heat.
> What they'd want to do is try to recover and reuse heat. In principle, there's no reason "new" heat has to be added each time they heat a batch of glass, if heat can be transferred from cooling glass back to the input materials.
Have you worked in any industrial or craft setting involving molten glass or metal? Walked around a workshop? There's no way the heat is going back into the process.
> Bosch I presume?
>
I would bet on that too. I have an older 300 series that is not WiFi and app enabled. It works great. I was suggesting "dumb" device models to someone and it was damned difficult to find which SKUs had misfeatures and which didn't. Same model, possibly same SKU (there are #s for different retailers), but two years newer had "smart" features.
> Seasoned electronics guys can probably solder anything with a cigarette lighter and a scrap piece of metal
This made me laugh. In college in the late 80's I repaired a roommate's not-quite vintage C64 fastloader cartridge with a bad wire bodge using a lighter and the tine of a dining hall fork...
Apropos, I have one of my grandmother's boxes of recipes on index cards somewhere. She was a great cook but her notes are, aside from being in mixed German and English, nearly useless because the amounts are "some", "a bit", "a spoonful", "a glass", or "a handful". Whose hand? She was tiny, a 1950's size 8 would have been a tent on her. I save it for the memory of those meals.
Whatever you think my opinion is of Perl you're probably wrong and the tone of your advocacy is kind of odd.
Awk is older and as a part of POSIX the version found on unix-like environments will be (outside of extensions) compatible with others. If one or one without the extensions you want isn't present you can choose an implementation, even one in Go and it'll work.
Perl, and I've been writing Perl since Perl4, doesn't have those characteristics. It's a much more powerful language that has changed over the years and it is not always present by default on a unix-like system. Because the maintainers value backward compatibility, even scripts written on Perl5.005 have a fair chance of working on a modern version but it's not assumed (and you shouldn't assume anything about modules). Because Awk is fossilized, you can assume that.
> granted, he'll probably fuck up his first two or three pretty good without haynes or chilton
Given the assumptions, inaccuracies, and mistakes I've seen in some Haynes and Chilton manuals they'll probably fuck up with them. Factory manuals are usually worth the price (Honda's are, KTM's not so much).
> Would you write your own JSON parser, is it that easy in LISP?
I only dally with Lisp(s) but probably not, I'd reach for a library in quicklisp.
However, in Janet (https://janet-lang.org/) there's a PEG parser and I wrote a JSON parser for fun in 134 lines that passes most of the test suite by Nicolas Seriot.
So I'd say it's reasonably easy for a better-skilled programmer than I am.
> I do. But I do not need just any Unix shell account, I need old and weird ones! I develop and maintain a portable utility (rlwrap) that is aimed at users of older software
Thank you, personally. I've used it in several contexts not just old systems, for example rlwrap is recommended with Clojure (okay, perhaps that's a comparatively small audience).