2,041 karma · joined April 2, 2011
That said, it's also surprisingly finicky. The scripts have to be regularly maintained or things keep changing out from under you and causing problems. Especially if you need to support more than one platform (i.e. macOs and a Linux say...).
The way it went, there was a poor man who lived above a restaurant who subsisted primarily on rice. He discovered that by eating by his open window, the smells drifting up from the food cooking below would add flavor to his meager meals. When the restaurant owner discovered this, he became angry and demanded payment from the poor man who naturally refused. The restaurant owner pulled the poor man before a local magistrate demanding that the magistrate force the man to pay. After thinking for a while, the magistrate asked if the poor man had any money, which he did. The magistrate then directs the poor man to jingle the money and said that the payment for the smell of the restaurant owner's food was the sound of money.
I can't retell it nearly as well as the original, which is probably online somewhere but not anywhere I know about ... :(
That said, php's online documentation is one of my "gold standards" for what good language documentation should provide. (At least it was the last time I had to reference it.)
Service also needs to be cognizant of overall "load" on the environment. It might be ok to chat when there's no one else around, but not when ten people are waiting. It's a bit of a balancing act and so few people providing service really understand it.
(Ubuntu LTSs and macOs are an example ...)
Ideas can cross pollinate between languages, but not everything translates well.
To answer the other part of the question, you can think of a wave guide like a tuned pipe for rf to travel down. In alot of cases they are literally just empty tubes that are correctly tuned for the frequency fed into them.
The question seems to be:
"When is a fetus considered a separate life?" or perhaps "When does a fetus become a baby?"
That's a lot harder to define than you might think. (At least that's the argument ...) Pro-life people tend to see a cut and dried answer to that, where Pro-Choice people tend see it as a bit more ambiguous.
You know, this might have something to do with why I gravitate towards doing "user" (really other devs since I tend to work on internal tools more than outside facing products) support type stuff. Devs trying to figure out why something isn't working are usually grateful when someone can help them get things working so they can do their job.
This a thousand times over ... If you can train your users to do this any customer relationship will be better off!
Otherwise, I'd agree with your stance completely.
It get's complicated fast if you want to discuss more than very abstract generalities.
Yup, the very next question here should be: Show me the failing/in correct behavior.
This means: * There's a case the automated tests don't cover. * There's a misunderstood requirement on the QA or Dev side. * There's a broken machine or configuration in a deployment.