It would, but it would be platform-specific and an external dependency. It was my first thought too until I started planning out it working cross-platform.
That personal risk includes having yourself or loved ones thrown in prison without any contact to the outside world for however long the dictatorship sees fit.
It’s a very sad history of oppression and corruption that has forced many Venezuelans to pull up their roots and risk their lives leaving their own country. It would be a dream come true to see this dictatorship overthrown and replaced by a democratic system of government that serves the people.
I really think that Rust has one of the best designed/inspired type systems.
If I had to rewrite a Python project, I would consider Rust or another statically typed language before choosing to continue in a dynamic language with types bolted on. I hope the situation improves for dynamic languages with optional types, but it still feels weird and bolted onto the language because it is.
I'm a professional .Net Core developer, but I'd throw my hat in the ring for Swift on this one. While obviously not exactly a 1:1 with Rust, there is definitely some common benefits between the two. Though, from what I understand of Rust (very little), its typing system is slightly more strict than Swift's which is slightly more strict than C#'s.
Ahh this might explain the behavior I observed when running npm install from a freshly checked out project where it basically ignored the lock file. If I recall in that situation the solution was to run an npm clean install or npm ci and then it would use the lock file.
I disagree. The BLS head was either incompetent or corrupt. The two are not mutually exclusive so they easily could have been both. Firing the BLS head was the obvious choice and it sends the right message to all involved that we will not accept this margin of inaccuracy when it impacts our economy. We need a BLS head with the balls to raise hell when the numbers are not reflecting reality.
reply