jupp0r

This will synchronously block until ‘chat.ask’ returns though. Be prepared to be paying for the memory of your whole app tens/low hundreds of MB of memory being held alive doing nothing (other than handling new chunks) until whatever streaming API this is using under the hood is finished streaming.

I don’t know why “number of companies using language X” is a metric that is used here. Wordpress is serving 43% of websites on the internet as of 2025, so we should all be learning PHP!

You are probably writing this in a browser with Rust code in it.

Here is an amazing discussion of that problem and a description of several metrics that answer your question: https://spectrum.ieee.org/amp/a-better-way-to-measure-progre...

This solves the problem of slow transport between your frontend and your backend, but it will still incur a lot of unnecessary load on the database as well as compute on your backend (which isn't normally a problem unless you're using something really slow like Rails).

"you can do them in parallel" - not in Rails.

I personally don't think there's much value in writing assembly (vs using intrinsics), but it's been really helpful to read it. I have often used Compiler Explorer (https://godbolt.org/) to look at the assembly generated and understand optimizations that compilers perform when optimizing for performance.

That’s why the JVM has been using JITs since 1993 while it’s a renaissance inspiring marvel for Ruby in 2025.

Is it? To me it seems like Ruby is declining [1]. It's still popular for a specific niche of applications, but to me it seems like it's well past its days of glory. Recent improvements are nice, but is a JIT really that exciting technologically in 2025?

[1]: https://www.tiobe.com/tiobe-index/ruby/

When people say these apps are IO bound, what they actually mean is that they are memory bound. While Rails is waiting for IO due to its lack of concurrency support and the ubiquitous use of global variables in the ecosystem, a passenger worker is taking up >300mb of memory for a medium sized Rails app. Server memory limits the amount of workers you can have waiting like that, which in turn limits overall throughput per server.

It would be really helpful to know what government you are referring to.

Tritium begs to differ.

You are probably writing your comment via lots of software written in C++. It's a great language with lots of flaws introduced by legacy decisions that would be made differently today.

You could argue that their job is to get this approved ASAP if it's in the interest of the nation.

That's what they told Columbus.

I'm not convinced new legislation is even needed to fix this. All of these agencies are controlled by the executive branch of the government.

Absolutely. Being able to get mass to orbit at orders of magnitude less cost than competing nations (China, Russia, India, ...) is of paramount strategic importance. This touches communications, intelligence, space exploration, orbital resource extraction, moon bases and all sorts of other things that have tremendous economic, military and societal impact.

There are environmental concerns, I get it, but this feels a little bit like delaying the Manhattan project for a year because the test detonation would endanger some birds in the desert.

They need to apply for a license for each launch.

It's absurd how these licenses are not fast-tracked by the government. This is one of the greatest technological assets the US have over other nations. It boggles my mind how the US government is shooting itself in the foot here if you compare it against other national security projects run by the government itself.

(2013)

For this to be a tangible benefit for any particular investor, a lot of unlikely conditions must be met.

That doesn't make sense unless investors own the same building that the company in question is renting office space in.

There is no system in existence that would provide a 90% interception rate. Existing anti ballistic missile systems are designed to intercept smaller attacks with low single digit warheads, no MIRVs and no decoys not a full scale attack.

There is circuitry to prevent this.

I think all you do is connect the inverter to any wall outlet. Basically a male-to-male power chord.

You can also dilute it with lots of seawater

Except something like an EMP or other large scale breakdown of infrastructure.

I would be surprised in the general case. Realloc does have side effects and the size parameter can be known at runtime only, etc.

Just to clarify: false positives in the sense that memory safety is violated intentionally as described in the article with relation to realloc and similar hacks, which would normally not cause problems.