295 karma · joined July 16, 2016
Then again I haven't seen the court filings so maybe that's exactly what they did and Namecheap is just mentioned as an additional defendant.
Either way, I would also expect Namecheap not to reveal anything unless they are compelled to by court order or another legal obligation.
This whole thing was a feedback circle of increasing hostility between the community/contributors and this developer. At some points the developer was very unresponsive, leading to disappointment from the community, but then some very uncalled for personal attacks came from the community. I think the developer received some justified criticism, but I still understand his perspective, putting work in and getting abuse back sucks.
What I'm saying is, don't limit yourself to Mutexes, there's a whole zoo of synchronization primitives and each of them has a specific use case that it's ideal for.
Recently I've dealt with a lot of synchronization in Rust, and I would say it's been as pleasant as it could be, considering the subject matter. Deadlocks are still possible, but at least the compiler stops you from accidentally unlocking a Mutex too early.
I don't entirely disagree, but most environments (or "paradigms") simply hide all that away from the user. Which is generally a good thing. Chances are you _are_ using a lot of those primitives in any given parallel or concurrent program, but you're only aware of one or two of them. For example, a channel for message passing between threads (or tasks in a cooperative multitasking context) might contain a Semaphore and an atomic reference counted pointer which in turn contains atomic integers. See [0] for an example.
And while concurrency and parallelism are not the same thing, you often end up having to consider the same synchronization problems in your code whether it's concurrent or parallel. Cooperative multitasking does involve true parallelism when the scheduler uses multiple threads on a processor with multiple cores. Code is not just being executed concurrently there, it is (possibly, not guaranteed to be fair) executed in parallel.
[0] https://docs.rs/crate/tokio/0.2.9/source/src/sync/mpsc/chan....
In most of Europe (probably all the EU countries at least, unified regulations yay) shops need to put the price per 1kg/100g/1L/100mL on the tags, depending on which is most appropriate for the product.
It's usually not much more code than I would have written with an error handling library and it's fully transparent, understandable for anyone with a rudimentary understanding of Rust. And I get to have one less dependency.
Usually it would look like this in Rust:
fn get_user(&self) -> impl Future<Output = User>;
This isn't exactly the same functionally, but for most use cases it works just fine. The difference is that this uses static dispatch instead of dynamic dispatch and therefore can't support dynamically returning two different structs that both implement Future, it has to be one type.
While Amazon should have been more explicit in telling people that submitting a clip means someone will watch it, it's not exactly unexpected.
The title suggests something much bigger.
That's a rather weird characterization in my opinion... H&M stores in roughly their current form have been around a lot longer than Forever 21. H&M is also 4-5 times the size of Forever 21 by revenue.
[0] https://www.marinetraffic.com/en/ais/home/centerx:9.973/cent...
Similar with bringing a bottle of a brand that the store sells into the store - how are they supposed to know if you brought it in or if you just took it in the store and opened it there on the way to the cash register? (which, by the way, is not super uncommon either and generally tolerated)
German police are not allowed to collect fines on the spot, it's a corruption prevention measure.
I don't think most US cities would ever get to a point where public transport and bicycles are much faster for a lot of regular routes (like in some European cities), but the gap can be closed if there is political and financial support to improve the infrastructure.
RflEttÜAÜG
However things like tupperware didn't seem to work that way, the product was actually mostly sold to end customers which makes it a legitimate business and not a pyramid scheme.
Even if we suppose that is true and a fair comparison (which I wouldn't), the way failure modes are handled is key. If there is uncertainty about the sensors that control the feature which controls the avionics the system needs to halt. This is like keeping the lane control active when the computer vision algorithm used to detect the lanes is uncertain about where the lane is. Chances are it'll steer you into the next available tree and kill you.
There may or may not be something inherently problematic about the way the MCAS works, but more thorough training would likely have lowered the chance of these accidents happening - having the same type rating was one of the root causes for the lacking training