CanadaPlus
If coding teaches you anything well, there's no bound to the different ways you can screw up. Don't use bad languages on purpose.
I did know the difference, but I didn't realise it ran one line at a time! I had kind of assumed it at least did one pass through everything before giving output. Thanks.
I'm familiar with the early history, I've dabbled in it in modern times, and of course I've seen all the ways it's bad memed about ad-infinitum (and have to agree).
I didn't really think I had to be able to write a book on it to say it doesn't deserve the use it gets, and I don't think it's outrageous to imagine that there's a connection with the hasty genesis. So, I mentioned that off-hand. If it's actually unconnected my bad.
Alright, thanks for the help with terminology. I'm a bit confused about changing types at runtime. I thought a compiled or interpreted language stopped having types at runtime, because at that point it's all in assembly. (In this case of course it's scripting, which someone pointed out to me elsewhere)
The standard itself is 7-bit, since wires were deemed more valuable than endpoint logic for the teletype machines way back then. If you're running it on an 8-bit byte machine you could do it either way, although I'm not sure what the point in parity checking individual characters is. Modern software uses 0.
TIL. Obviously I've avoided using it much.
So how does that work? Is there a few implicit conversions that are allowed, but if you really write something weird it will complain?
I'm going to say that's the exception that proves the rule, assuming they were structural parts and not a minor controller chip for de-icing or something.
The company themself announced it without being prompted, and if whoever introduce these unapproved parts into a small number of engines is caught there's going to be real hell to pay. The stuff that stops you from falling out of the sky is serious business, and is largely treated as such.
On the other hand, a software function that's hacked together and inefficient will just fly below the radar, and most people will prefer two cheap outfits to one that's actually well made for the same price, so quality goes right out the window.
Actually, that's a good point, in scripting fatal type errors can happen at runtime. I guess Python is the right choice then, given it's maturity and popularity, and then you can code the complex stuff in whatever you want via WASM like other people mentioned.
I guess the internet just grew that fast. The first arrival took all and locked everybody in.
Now, we have just two browsers that are widely used, so maybe we do have an opportunity to go back and fix it. Go sounds like it's a pretty popular choice for statically typed, imperative high-level language.
Good point.