heretoo

I tried FreeCAD but all versions crash within minutes of using it, making it unusable.

It would be nice if I could scale the UI. Some text can be scaled with GDK environment variables, but not the icons.

Except that lead's toxicity has been known for thousands of years.

> Now we just have to get a handle on all the leaky stuff at the edges of every “functional core”, because there lay many dragons

My gut is telling me erlang might have tackled this.

> It sounds like you're making the mistake of thinking that TDD means writing the tests first.

Actually, Kent Beck, who coined the term TDD, has the following to say in his book "Test Driven Development":

"In Test-Driven Development, we Write new code only if an automated test has failed"

This implies that in TDD the test is written first.

Regardless of any definition, test-first and test-last are just two ends of a scale we can use.

It wouldn't surprise me if the original reason is the pervasive use of jupyter notebooks in ML, which don't adhere to normal python conventions, and are affected by slow imports only when those sections are explicitly evaluated.

Side-effects in imports are, in my opinion, unnecessary, losing some of the benefits of static analysis, running with different parameters during tests, compiling to native code (if those tools exist), slowing things down, and more.

Libraries could have an initializer function and the problem would go away.

You could consider Clojure. It is backed by the java ecosystem, which is substantial. Not quite the same as python's "batteries included" approach.

What if the warrant canary is from the developers of the encryption software? See truecrypt -- assuming it was actually a warrant canary.

Where "cross your fingers" is equivalent to the "warrant canary has not been revoked" when encryption is involved.

Another options is "nsjail". I landed on it having considered at firejail, apparmour, selinux, bubblewrap.

Not in the community edition, but the enterprise edition appears to be quicker than JIT because of profile guided optimisations.

The window doesn't close at 39 for either of you. From personal experience, I know.

So, if we followed this advice, none of these technologies should have ever been used in the first place, because popularity takes time to establish.