For a lot of architectures its also irrelevant. I use sync code and I use async code in my architecture. But more like independent subsystems. They are sync internally and only few places have connections to outside systems or IO. Those can be async.
I do understand though that it can be annoying for library authors, especially those that need to interact with the FS/Network etc.
An active bug from 12/12/2018 that Google and the Chromium team just dont want to fix for 'reasons'.
First time I stumbled over this bug myself I thought that will be fixed soon. When Microsoft started using Chromium I thought "for sure now they will".
Turns out there is something nefarious going on. There is no other explanation.
I liked pi.dev but why is registering endpoints and models not as simple as possible ? Or am i missing something ? I always have to fiddle with the config file.
Of course its newsworthy if the company making the most electric cars in the world has setup a factory to produce semis and produced at least one after years of testing with actual customers that say they are very happy at seemingly very competitive pricing.
To say its NOT newsworthy betrays a bias against Tesla which I would assume has nothing to do with actual facts.
As someone who never liked writing anything C++ since 2000+ (did like it before) I cannot agree with this. C++ and Rust are not comparable in this sense at all.
One can argue Rust is what C++ wanted to be maybe. But C++ as it is now is anything but clean and clear.
Considering that I doubt most normal office-user people even use features in Word other than changing fonts etc I doubt that will be a big issue anyway.
considering cameras can create reliable enough distance measurements AND also handle all the color reception needed for legally driving roads it was always a ridiculous idea by a certain set of people that lidar is necessary.
Dont get me started on the number of times Signal/formerly Skype opened up a dialog in-the-midst of me typing and me accidentally accepting a call because i happened to write 'space' at that moment in time
That depends a lot on many factors and thus I dont like generic statements like that which tend to be more focused on a specific database pattern. That said everyone should indeed be aware of the potential tradeoffs.
And of course we could come up with many ways to generate our own ids and make them unique, but we have the following requirements.
- It needs to be a string (because we allow composing them to 'derive' keys)
- A client must be able to create them (not just a server) without risk for collisions
- The time order of keys must not be guessable easily (as the id is often leaked via references which could 'betray' not just the existence of a document, but also its relative creation time wrt others).
- It should be easy to document how any client can safely generate document ids.
The lookup performance is not really such a big deal for us. Where it is we can do a projection into a more simple format where applicable.
I do understand though that it can be annoying for library authors, especially those that need to interact with the FS/Network etc.