But how do you deal with communicating that some library you maintain has a behavior change? People already need to know to look at your code in order to read your comments.
This is kind of a fundamental issue with release notes. They are broadcasting lots of information, and only a small amount of information is relevant to any particular user (at least in my experience).
If I had a technically capable human assistant, I would have them filter through release notes from a vendor and only give me the relevant information for APIs I use. Having them take care of the boring, menial task so I can focus on more important things seems like a no brainer. So it seems reasonable to me to have an AI do that for me as well.
It dipped during the covid recession and then recovered to an all time high. Is this your first time looking at an economic chart? It doesn't need to increase every quarter for it to have a very strongly increasing trend.
You're looking at what percent of the total wealth pie do the poor get. But the pie itself is growing, and so is _everyones_ slice of the pie.
Maybe you think its an inherent problem that some people get a bigger percent of the pie than others. But its objectively untrue to say that the poor are getting poorer.
> They are illustrations of a general principle: the legal inheritance channel compounds while the biological one reverts.
All this pseudo-math relies on the fact that family wealth strictly compounds and does not decrease or revert to the mean. But that is not true. Economists study this, and the exact numbers differ but family wealth _does_ revert back to the mean in just a few generations. Wealth does not stay in the same family compounding forever.
Being able to avoid an extra copy is actually a huge performance gain when you can safely do it. You shouldn't discount how useful mmap is just because its not useful in every scenario.
You shouldn't replace every single file access with mmap. But when it makes sense, mmap is a big performance win.
This reads like complete nonsense. If HTTP is involved, lets just give up and make the system as slow as possible?
The HTTP request needs to actually be actioned by the server before it can respond. Reducing the time it takes for the server to do the thing (accessing files) will meaningfully improve overall performance.
Switching out to JSON will meaningfully degrade performance. For no benefit.
The differential on an EV is the same as on an ICE car. It does the same job either way, it doesn't care whether the power source is gas or electricity.
But on an EV, that's basically the only thing that needs somewhat regular "oil changes". Whereas ICE motors & transmissions also need fluid changes regularly.
Yeah I totally get that it optimizes for different things. But the trade offs seem way too severe. Does saving one round trip on the handshake mean anything at all if you're only getting one fourth of the throughput?
> QUIC is meant to be fast, but the benchmark results included with the patch series do not show the proposed in-kernel implementation living up to that. A comparison of in-kernel QUIC with in-kernel TLS shows the latter achieving nearly three times the throughput in some tests. A comparison between QUIC with encryption disabled and plain TCP is even worse, with TCP winning by more than a factor of four in some cases.
Jesus, that's bad. Does anyone know if userspace QUIC implementations are also this slow?
Aeron is very popular in large financial trading systems. Maybe since multicast is already commonplace (that's how most exchanges distribute market data).
The key is that blibbe is talking about switches. Modern switches can process packets at line rate.
If you're working in AWS, you almost certainly are hitting a router, which is comparably slower. Not to mention you are dealing with virtualized hardware, and you are probably sharing all the switches & routers along your path (if someone else's packet is ahead of yours in the queue, you have to wait).
The important distinction is that it is possible, and should be the expectation, that you can study beetles and publish the results without any sort of political motivation or bias.
In that sense, it is perfectly possible and reasonable to "take the politics" out of scientific research. Simply do the research and publish the results. There absolutely is a thing as "no politics".
Once the results are out in the world, politicians and pundits are going to talk about it. That doesn't make the science itself a political act.
I just think we are talking about different things. I hear what you are saying, but I don't think that bakeries being tangentially related to politically charged topics make them a political institution.
Bakeries also handle and store money, but that doesn't make them a bank. etc. The nature of bakeries as an institution is not political - they are not concerned with the organization of government and policies. They may interact with the government but that doesn't make it a political institution.
Can you define "institution" and "political" for me, then?
I would argue that there is nothing political about a local bakery, for example. Just a dude making some cakes. He may occasionally be forced to interact with the government, but his bakery as an institution has nothing at all to do with government organizations or political theory. By its nature, a bakery is apolitical.
Scientific research is apolitical. Even the act of studying abortion or transgenderism is not inherently political.
Just because scientists have to occasionally interact with political institutions does not make Science itself a political institution. Science is fundamentally apolitical.