They want something that actually works, foremost. If the thing they sell doesn't work, then when someone figures out something that does work the thing that works will be preferred by the doctors.
One big difference is that go hides all access to creating threads from the user, while execution contexts allow you to spin up dedicated thread(s) to solve a particular purpose.
Execution contexts closing in to being enabled by default is a big one. As is the io_uring based event loop that is also finally getting merged (even though that one is also hidden behind flags).
Mine does and it works so well that I actually have to turn it off when working from home as a bunch of the third party servers at work doesn't have any support for it.
You are missing the business model - buy has-been platforms and frameworks and charge big bucks for maintenance. Customers eventually manage to migrate off you, but it is fine cause you buy some other has-been stack and then overcharge for that.
Also it is very easy to find situations where hash table lookups dominate a measurement, but where the answer isn't to make the lookup faster but to make fewer lookups.
Hmm. I kinda wonder how something like a regexp engine based on marpa would fall. It would probably be slower in the common well behaved cases, as well as preprocessing. But I wonder if there are any cases that couldn't be done in a O(n) way if you limit yourself to only one match (instead of finding all possible matches like it actually can do). Marpa definitely handles most degenerate regexp cases linearly (once you make the match generation not do overlapping entries), but there may be some regexp feature it can't handle?
Bringing a fully general CFG parser to parse regexps would be like hunting mosquitos with a nuke though..
Which is a thing that depend very much on team culture. In my team it is perhaps 15 min for smaller fixes to get signoff. There is a virtuous feedback loop here - smaller PRs give faster reviews, but also more frequent PRs, which give more frequent times to actually check if there is something new to review.
I'm actually somewhat surprised Iran is openly telling us they are using underwater drones for this. That piece of technological advance has gone mostly under the radar (!) so far.
I'm doing crystal bindings for pipewire and wayland clients. It is nice to be able to do so much with so little. github / yxhuvud / [pipewire_cr | wayland_client]
I'm not certain I buy it, but I find it a little hard to motivate the training being fair use if used to regenerate the project in a different licence.
We would have, if the expensive memory was a long term trend. It is not - eventually the supply will expand to match demand. There is no fundamental lack of raw materials underlying the issues, it is just a demand shock.
What you are asking for is to make a library definition replacement to .h-files that contain sufficient information to make rust safe. That is a big, big step and would be fantastic not only for rust but for any other language trying to break out of the C tar pit.
What Apple restricts and is legal are not the same. Apple is doing malicious compliance and the legal system ain't buying it. But it takes some time and iterations to shake out.
In many cases government texts are not covered by copyright, so it may not even be relevant here, regardless of it is is allowed to copy the data or not.