We used to have several companies in the US that mined and refined the materials. They shut down because they couldn't compete with China, but if supply became constrained over a long period of time they could restart operations.
It's one reason the Chinese threats of cutting off rare earths is not quite as scary as the media makes it out to be. They can't do it for too long before alternatives get spun up and they lose their leverage entirely.
Future generations will blame us for damning them out of rare earths to build yet another cellphone. This is like us today with severely diminished whale populations just so Victorians could read the bible for another 2 hours a night. Was it worth it? Most would say no, save for the people who made a fortune off of it I'm sure.
That makes no sense whatsoever. We are not consuming rare earths; only moving them from one place to another.
Arguably, future generations would find it easier to mine them from former landfill sites, where they would be present in concentrated form, than from some distant mine in the middle of nowhere.
Will the NIMBYs of the future allow for rare earths processing in long defunct landfills that in the future are surrounded by residential development? These urban landfills even today really aren't far from civilization. In fact they have been enveloped by civilization in many cases.
I mean as it is you can't even recycle most things if they are the least bit soiled since it is not economically viable to implement a cleaning process. We are doing a whole lot of assumptions that our future members of our species will have solved a way to reliably get pure rare earths from a mixed up slop of everything in a landfill. Whatever they possibly figure out is going to probably be far more challenging than ore refining processes we use today.
It might be cheaper/easier to try and capture an asteroid than to refine a landfill.
> Future generations will blame us for damning them out of rare earths to build yet another cellphone.
We’ll be out of many elements before we run out of rare earths. They are not actually that rare, they are mostly inconvenient to extract because they are distributed everywhere as minor elements rather than concentrated into ores. Things like cobalt, nickel, the platinum group metals, or even copper, are more worrying from a sustainable production point of view.
I owned a Jeep 4XE, and I was glad the day we sold it, and I'm doubly glad today. The electronics and software were crap, and the powertrain was simply insufficient. At one point, they issued a notice that amounted to 'it might catch on fire, keep it away from your house.'
Do you mean to say that two non-dependant tasks in an Airflow DAG aren't able to concurrently execute? Thats not my experience. I'm also confused by the use of 'static' in this context.
That's the point: non-dependant tasks can run concurrently in Airflow. In sh/BAsh/dgsh dependant tasks can also run concurrently, as in tar cf - . | xz.
>You have two options: fail open and let the request through, or fail closed and block the request with a 429.
If the metaphor of a software circuit breaker is meant to emulate an electrical circuit breaker, then it seems to me that these two are inverted. Whenever a physical circuit breaker is open, it is not dangerous and not passing current.
Agreed, and I don’t know why you’re being downvoted. If someone told me their virtual circuit breaker “fails open,” I would assume that it stops processing data upon failure.
Heh, glad to see it, was gonna post this.
Now you have it, do you want to use it. (bluff call time LOL).
Being a bit facetious, don't get too offended at the joke, people. But yeah, Xonsh is the "python(ish) shell" option if that's what you want.
Which works fine.....until it doesn't. Many non-trivial builds require custom logic, and trying to do that in maven was painful the last time I tried it.
If you have any complexity, programming against a good abstraction (Gradle is not good good, but decent) beats finding the magical incantation of configuration to get the tool to do what you want.
I think folks just get used to Maven-induced constraints (this applies to SBT, Bazel, others too). When you free yourself from that you realize: builds just aren't all that hard, it's often the tooling that becomes a real limitation.
Of course, sometimes the limitations are good: preventing you from doing "the wrong thing", or encouraging cacheability, etc. But as with any abstraction layer - getting a model that fits across so many disparate use cases can be very challenging.
That is why maven offers a plugin model for your custom logic that can be written in Java/Kotlin and a well defined lifecycle model where you can configure your plugin declaratively.
You can also download custom CLI tools and invoke them as part of a well-defined build lifecycle.
And then fail to do proper incremental builds, leaving you with no choice but a faulty build or clean installing on every occasion.
At the very least, I would move to Gradle which does have proper knowledge of your build graph. But Mill is also a good choice and fills the same niche, with the added benefit that imperative-looking ordinary scala code will simply become a parallelizable, cacheable build graph.
reply