Almost everyone I’ve seen using them on the web (myself included) does that. Very few people I’ve seen set them open.
(Lots of people use en-dashes set open instead of em-dashes set closed for the uses for which they are interchangeable as a matter of stylistic preference, though.)
I enjoy understanding what my programs do to the deepest level, so making or using AI are both boring; they remove the fun part of programming and leave only the boring parts (mainly debugging). I haven't liked the current ML field since the beginning (early 2010s in my case) for this reason.
I want a tool, not a slave. I don't want it to be "smart", but an extension of my body. A thinking body part is always more annoying to deal with, because you have to reverse-engineer what it's doing to get it to do what you want.
I don't think this reasoning applies to everyone. I think it's fine for other people to use ML algorithms. I just don't want them myself.
Also dont forget about deskilling. Right now its fine because you are able to debug. But it would get gradualy lot harder if you are not flexing that muscle.
If copyleft is desired, the EUPL is very similar to the AGPL, but isn't viral, so you can link it as a library to a closed-source program. It's also compatible with most open-source licenses.
Not sure if it's what the OP wants, but I think it's a neat license and I don't see it used anywhere.
I agree that abortion is evil, but in my perception, once someone gets to a situation where they're willing to murder their own child, it won't be a law that'll stop them.
This problem should be considered moral, not legal.
It feels like this is aimed more at intermediary programmers (and seniors with careless attitudes).
A lot of them have this bizarre idea that since bugs will happen anyway, there's nothing we can do to avoid them. Then they come up with some bad architecture, or poorly-thought-out convention, or use a problematic library, which makes it easier for logic bugs to happen later, when someone else changes a convention elsewhere that interacted with it.
There often is a way (usually multiple ways) to architect software to avoid bugs. What Rust does to memory bugs and Haskell does to state bugs, can often be done manually in other languages, for whole categories of logic bugs, by being careful with your conventions and making sure they are easy to follow correctly.
I.e. software can be designed to avoid bugs. That requires some thought many people don't care to put in.
> Stevens' power law is an empirical relationship in psychophysics between an increased intensity or strength in a physical stimulus and the perceived magnitude increase in the sensation created by the stimulus
If we're counting only programming languages (and not fill-out forms), Prolog had it in 1971, before ML. ASCII didn't include _ until its 1963 draft, so it's probably somewhere in that time.
I'll guess it's probably Prolog, but maybe Planner (Prolog's predecessor) had it too.
