The article says they could have asked an AI themselves, but that is missing that I may have an agentic context with exactly the right information to answer the question well, which they do not have. For example because I worked on something closely related. Such an agent output is very useful, and taking the time to rewrite that to a short personal answer is not always worth it.
Do you think it would fundamentally be a mistake to thread data along with error type through the error return path, or is it just that it costs too much say from a calling convention perspective or some other technical reason? Is it related to ownership?
My feeling is that I consistently find on-point solutions for my Linux problems with a quick search. However if my Windows install gets in trouble my search will yield some DISM.exe invocation which doesn't help at all. A bit anecdotal, but this is my experience. I've always been able to fix my Linux installs.
Let’s not underestimate the scale of the search which led to us though, even though you may be right in principle. In addition to deep time on earth, we may well be just part of a tiny fraction of a universe-wide and mostly fruitless search.
XWayland is compartmentalized, and should not make life harder for anyone else in the Wayland world (except the ones spending time maintaining it). And Zink gives us a clean OpenGL implementation on top of Vulkan (so not contributing to complexity in the base stack). I'm fine with a long tail of software requiring XWayland+Zink, and I don't think of them as polluting my system.
Since it's trained on a vast a mount of code (probably all publicly accessible Go code and more), it's seen a vast amount of different bespoke APIs for doing all kinds of things. I'm sure some of that will leak into the output from time to time. And to some extent can generalize, so it may just invent APIs.
If it was first, it could have self-improved more, to the point that it has the capacity to prevent competition, while the competition does not have the capacity to defend itself against superior AGI. This all is so hypothetical and frankly far from what we're seeing in the market now. Funny how we're all discussing dystopian scifi scenarios now.
That's the theory. However, isn't likely that as things like the new Nova Nvidia driver is written in Rust, the things that depend on Rust are suddenly so important, that shipping with it disabled is unrealistic, even without a policy change. (I don't think this is bad)
And start treating the alliances as vital part of the whole, and stop betraying the fragile trust they are built on. Use Korean industry until the industry at home can catch up.
I’m talking of the typical left/right split. Where leftist policies tend toward redistribution of wealth to the benefit of broader swathes, while right oriented policies tend to at least lead to more concentration of wealth. Maybe it is an outdated bias, but until now at least my impression is that young people have had a greater tendency toward some form of humanistic idealism.
On the flip side, it seems evident that younger people tend to vote for the betterment of all, while older people tend to shift toward voting for «themselves».
Ideally arrays of primitive values like `long` to store the bytecode represenation for proper good performance. Then use bitwise manipulation to access "fields"
Given the accepted MAD doctrine, which kept the "peace" throughout the cold war, you would think nuclear escalation would be unthinkable as a means to stave off a conventional defeat on foreign soil.
Though if the evidence presented for this event is persuasive, then all they achieve by making the connection is to speculate on a natural cause for a biblical "miracle". I mean it can strengthen a view of the Bible as source of historical information, but not as the word of God.
If this event happened, I would expect it to leave long lasting trace in oral tradition.
Basically using "await" just means you are declaring opportunity for concurrency at the call site, but it is still valid to await a synchronous function.
And it is valid to call a function synchronously, even if it internally supports concurrency via await.
Soundness gives an important benefit: Performance, for a compiler capable of utilising the type information properly. It can omit run-time checks, and unbox primitives etc.
This shows that if you are making a not-very-fast compiler (most compilers these days), then the much maligned C compilation model has some serious advantages on modern and future hardware, due to its embarrassingly parallell nature.
The stocks they are borrowing for their shorts have really high interest now. They are bleeding money just paying interest. And now that goes for a couple of hundred percent of the stock float.
It seems like shorting alone can create this kind of systemic risk, with its infinite downside. One has to question whether it might be better were it not allowed.
Swift has the slowest compiler I have ever had the misfortune of using. The dev iteration cycle was unbearable for me in a Swift project the I inherited.
In Norway MSN Messenger was responsible. I remember all the people who were a couple of years younger than me starting with that, and ICQ never recovered.