The "Mining sand" problem in the article refers to concrete-sand. This is completely different from, as well as scarcer than, glass sand.

Boeing is in serious do-do. It needs to convince the flying public they have clearly identified the problem AND fixed it. All while limiting their legal liability.

At the end of the day the real and serious question for flyers: "Probability-wise is the Max, flown by a typical pilot, significantly more likely to end up crashing".

I think that I would want an answer to that question, before booking a flight on one.

Uh, must mean "jumped by over 200% in 2018".
100% = 11
200% = 16.5
300% = 22

And how about the needless repetition: All the paragraph does is say three different ways that 18 3/4 long, or 5 1/4 shorter. No other actual information. Sheesh. Almost as bad as reading Reuters (and other) news where the same news article commonly appears 3 or more times in different "sections", with the exact same summary. Nothing like adding a bunch of filler rather than unique content. News these days has ended up in a bad place.

Jsish (http://jsish.org) walks a fine line with an implementation of javascript wherein type-checking is provided only for function signatures. This can improve module usability, without impacting the bulk of an implementation. And although Jsish is primarily embedded, it also provides in-Browser support that pre-processes just the function signature, rather than the entire code body (ie. like typescript).

Disclaimer: I am a Jsish developer.

It's sad that 30 years on, none of the existing config/build systems seem to offer even basic debugging capabilities.

Which is why on the Jsi project (jsish.org), the configure is handled by, well Jsi itself.

That is, a minimal interpreter is built with just enough language features to perform the configuration.
No external programs are used. If there is a problem, we can use the Jsi debugger to single step through it.

Try doing that with m4 (used by autotools), cmake, et al.
In fact, debugging is not possile when you are using:

bash
make
gcc/g++/ld/ar
autoconf/automake/libtool
m4
awk
sed
basename
chmod/chown
strip
grep
find
cpp
gdb
yacc/bison
lex/flex
tar/gzip/zip
man
cmake
lua
tcl
perl
python

Railing against Javascript is like refusing to speak english because it's a convoluted language filled with inane rules, exceptions and colloquialisms.

In exchange for manual memory allocation, C++ gives you automatic memory allocation: lots of it.

When resources are scarce (eg. IOT devices) this overhead can be a show stopper.

Something that C++ advocates seem to ignore:t there is no free lunch.

This week at work about half of us have started getting daily blue screens of death. I checked and there were now updates or SW installs in the last month.
I've worked there for 5 years and never seen anything like this. Is it a domain policy change or config change from Microsoft that's triggering it?

We mostly use Windows to run VM's for Linux development, so I'm no MS lover.

Perhaps you're not old enough to remember this, but browsers used to support Java and you could even embed languages like Tcl/Tk.
Unfortunately, this lacked the one thing browsers are good at: universality.

Writing maintainable javascript (still) requires a defensive approach. Using abstractions just bite. But the big disconnect occurs when calling a function with the wrong number or type of arguments.

In real life, I embed javascript (http://jsish.org) in C into high-end industrial devices, albeit mostly for diagnostics and testing purposes.

The only reason this flies is because Jsi has been extended to support type-checking of function calls. Standard Js itself is just too hard to maintain.

(Disclaimer: I am the author of Jsi)

Or even javascript and C: http://jsish.sourceforge.net/