The difference is that it's trained and benchmarked on the MCP-standard. Which makes it much more reliable than if you create your own interface.
The difference is that it's trained and benchmarked on the MCP-standard. Which makes it much more reliable than if you create your own interface.
Then it asks me to switch my profile to American/$. But then in order to order I need to switch back to Germany/€.
It's just super cumbersome. Just let me view stuff from any region without switching profiles. If I order from that region you can tell me to switch profiles. But not just for viewing it.
In the same vein. Why is there no, I want this thing, but from a German seller.
Deleted Comment
For certain other kind of concurrent algorithms, you are in a world of pain and Rust's borrow checker simply refuses to compile a large set of otherwise correct programs.
I will very easily write a faster parallelizable program in Java, before I get the C one even remotely correct and then we haven't even taken into account every future maintenance cost. Also, the way C devs often hide the cost is simply.. less efficient code like copying stuff right and left, etc, which can actually be more "bravely" avoided in managed languages.
Even better in Rust. You get great memory safety guarantees from the borrow checker helping guide your parallelization, while still being fast and GCless.
It's the best of both worlds.
>Also, the way C devs often hide the cost is simply.. less efficient code like copying stuff right and left, etc, which can actually be more "bravely" avoided in managed languages.
I'd say Rust is again the easiest way to avoid unnecessary copies without sacrificing safety.
And here we are, 20 years later.
Not to say that it doesn't happen, but most forms of manual labor don't wear down, scar, callous, or otherwise alter one's fingerprints enough to break it. In any case, this is why we all use backup fingers and toes.
Just found 3 race conditions in 100 lines of code. From the UTF-8 emojis in the comments I'm really certain it was AI generated. The "locking" was just abandoning the work if another thread had started something, the "locking" mechanism also had toctou issues, the "locking" also didn't actually lock concurrent access to the resource that actually needed it.
Citation needed on that one.