Honestly, that just seems like a case that would just as well be solved by better naming. Get a linter, tell it to forbid one letter names, and then enforce naming that isn't idiotic when doing pull requests.
But yes, there are multiple ways to solve communication problems.
You are not wrong. But there is a new extension protocol on the way (dunno if done, very probably not rolled out if it is) that let programs solve this problem.
A gzip encoder has no business deciding whether a socket should wait to fill up packets, however. The list of relevant applications and libraries gets a lot shorter with that restriction.
FWIW, there are iterative SVD implementations out there that could potentially be useful as well in certain contexts when you get more data over time in a streamed manner.
For some reason the OS can manage to ask me about what windows I want to screen share, but not about if i want to share secrets between apps or not? I don't see how this require kernel support - it just needs people recognising it as a problem that is wanting to spend the time actually solving it.
> When your software team needs to pick a language today, you typically weigh two factors: language performance and developer velocity.
There are obviously other factors in play as well, or languages that are really good at both but weak in other areas (like adoption and mind share) would dominate. And I for sure don't see a lot of Crystal around..
Either that or just wait out the problem. As long as the linux gaming market keeps growing the incitaments for the hardware people to change their minds will increasingly be there.
What I feel is really missing from factories is the ability to do bulk inserts of a whole chain of entries (including of different kinds). That is where 95% of the inefficiency comes from. As an additional bonus it would make it easy to just list everything single record that was created for a spec
Neither did the dismissal of AI in the article. I'd classify it as "not even wrong" in that the factual parts are true, but the conclusions are utter nonsense as ChatGPT can be extremely useful regardless of the claims being true.
It'd be very interesting to see an OO language that passes around allocators like zig does. There is definitely nothing in the concept itself that stops that.
The point of structured concurrency is that if you need to do that in code, then there is a need of a predefined structured way to do that. Safely, without running with scissors like how channel usage tend to be.
Neat, I see how this can prevent a lot of frustration when it comes to making certain queries stay quick as complexity grows. I wonder if this means I can forget the trick to chose LATERAL queries all over the place for performance reasons.
Once an area has its shit in order regulatory-wise: yes. Here my house org will upgrade from 1- to 10-gbit next month, mostly cause it also bumps the wifi generation to the latest and the cost difference was neglible. Previous hardware was end of life , so we had to change stuff regardless.
Regulating lead in petrol was very much not uncontroversial when it was regulated. Same with asbestos - the industries involved fought really hard against it.
High prices are a sign of their competitors failing to compete. Are they using their standing to make competing with them harder, somehow? For example, they dont do Amazon style prohibitions of selling the product cheaper elsewhere.