Scripting languages are often considered to be very high level and can commonly run without compilation. Making them great to automate tasks or create a simplified interaction/abstraction layer to a more complex program.
Then Python is not a scripting language.
Programming languages usually have much lower level access, and by extension they tend to be more complicated. In exchange for that, you get much more control.
Would you consider C to be more or less complicated than Perl?
FLAC is where it's at. Oddly, most of the head units that understand FLAC don't have CD drives at all. If it has a CD drive still, it probably only understands MP3.
Which is one response to the question of "why would you encode an MP3 at a high bitrate when you can just use FLAC?" It's because I had a car that didn't FLAC.
Yeah, once you know all the details, the distinction disappears. The term doesn't clarify understanding.
If I had to make a distinction, it'd be that scripting languages are meant to be a simple way to serve a specific niche. Things like SQL or Excel formulas. It doesn't apply to Python.
I'd say the term "procedural" itself is an issue. Pretty much any language can be done that way if you choose. IIRC, the creator of Clojure wanted Java to work more that way, and he did it by having a single class full of functions. It's not a natural way to write Java, and that's why he invented Clojure.
Procedural and OOP aren't mutually exclusive terms. Most OOP programs are ultimately procedural in nature. Often, the only difference is that the first argument to the function is to the left the function name and separated by a dot.
"Hashed emails". Besides the fact that they can match up a hash from one source to a hash from another source to link them to the same person (they never said they'd salt them), emails often have enough predictability to break the hash. Assuming they all end in "@gmail.com", "@outlook.com", or "@yahoo.com" will get you the vast majority of emails out there. Unlike a good password scheme, people don't shove a lot of random data into their email addresses.
That is not how Python works. There are very few languages that work by executing line-by-line anymore. Unix shell scripts are one of the few holdouts. JavaScript also does it to a certain extent; the browser starts executing line-by-line while a compiler step works in the background. Once the compiler is done, it starts execution of the compiled form right where the line-by-line execution left off. It helps JavaScript be more responsive since it doesn't have to wait for the compiler to finish.
If you bought a top of the line computer in 1990, it would barely have been able to run Win95. It wouldn't have been able to run Win98 at all. Conversely, even with Win11 obsoleting a lot of systems due to TPM, there are plenty of 7 or 8 year old systems that will still work with it just fine.
Win95 was a leap in complexity compared to Win3.1/DOS 6. It replaced a sloppy, manual memory management system with a sloppy, automatic memory management system. It created the registry system as we know it, and instantly got a reputation as a fast way to ruin your system.
Do you like files named "big long name.txt"? Because sometimes that will come out as "biglon~1.txt" or something like that. It was still using the same shitty FAT system, now with 32-bit extensions that technically allowed long file names, but had to shorten them for compatibility with older stuff.
Win98 added Active Desktop, which made your desktop part of IE. This meant that every time IE crashed, your whole desktop went with it. Didn't necessarily need to reboot to fix it, but it cleared out your background and a toolbar thing. In a way, it was an attempt to do what Electron apps do now, except with Microsoft proprietary web stuff.
Oh, and once it got USB support, it sucked ass. It had to reinstall drivers if you plugged your keyboard into a different USB port than you usually did.
Neither Win98 or ME would fix its memory management issues. That had to wait for Microsoft to get off their ass and release a home version of NT with WinXP (sorta Win2k, but that's complicated). This memory management issue was the root cause of most BSODs at the time.
People hated Windows at the time for exactly the same fundamental reason they hate it today: it's a clunky piece of shit. Win 7/8/10 was actually an attempt to simplify things in many ways, but Microsoft has fallen back to what they did before.
And then they hit the emergency shutdown, which is for when people have a plate in their head and they're stuck to the side of the machine. That one causes all the liquid helium to be quenched, thus needing to be refilled.
There is a slower shutdown that doesn't do that, but, you know, cops.
Every detail of that story was worse than the last, and it's 100% on the cops.
Edit: forgot another detail. The gun is probably magnetized now and might be unsuitable/unsafe for use anymore.
The US is allergic to it, but needs to get over it.
Aluminum wire was tried in the 1970s due to a spike in copper prices. The problem was that they just tried to swap it right in. Aluminum and copper have different rates of expansion. Over time, that would slowly loosen the connectors, and the wires would pop right out and cause a fire.
You can design connectors to handle both, and you'll see many electrical things today specify that they're good for aluminum or copper wire. It still has a bad reputation among electricians; they haven't unlearned the problem yet.
Now, one place it's more of a problem is in things like transformer windings. There are kilometers of wiring in any of them, so the higher resistance of aluminum is a problem.
Then Python is not a scripting language.
Would you consider C to be more or less complicated than Perl?