Anyone remembers Teleport Pro?

Really.. I was scrolling to find a comment complaining for this slop GH issue, which should be 10% of the size of what it is.

Surprised me it took so much scrolling to get to this.

Like, who reads all that crap?

I just stumbled onto this, which probably explains it: https://openrouter.ai/announcements/gpt55-cost-analysis

I guess parent argues that:

  - humans have a track-record of writing memory bugs

  - memory-safe languages prevent such by construction

Therefore, what's the justification of not using a memory-safe language (as opposed to an unsafe one)?

> what's the justification of not using a memory-safe language

Use Go, Java or Fil-C, and memory safety is achieved at the expense of runtime performance. Tracing garbage collectors make your programs run slower and use more RAM.

With Rust you pay with complexity. Rust has new, weird syntax (lifetimes, HRTB, etc) and invisible borrow checker state that you've gotta understand and keep track of while programming. Rust is a painful language to learn, because lots of seemingly valid programs won't pass the borrow checker. And it takes awhile to internalise those rules.

I personally think the headache of rust is worth it. But I can totally understand why people come to the opposite conclusion.

> because lots of seemingly valid programs won't pass the borrow checker

Some straight-up valid programs as well

Rusts memory safety constructs do also impose a (much smaller) runtime performance penalty. Every Arc / Rc is a memory safe abstraction with runtime cost since rust has no way to prove cyclic reference graphs are safe at compile time.

Interop.

How about they are pointing out a worrisome direction society might be taking, whereas work will infiltrate even more what used to be family or personal time, thus accelerating burnout?

Beasts of no Nation is a personal favorite!

> I beg to differ...I have a feeling the needle will indeed move, but it won't be a single big jolt. [...]

Then it seems you're not disagreeing with parent: they're saying "needle barely moved", you're saying "it will move".

They're talking about the present; you're talking about the future.

Technically, the parent is saying "the needle barely moved, therefore it will never move appreciably in the future".

Is that a good deal for the employees of Astro? They're now Cloudflare employees, which I guess looks good on your CV.

But do such acquihires usually result in higher salaries for regular (non-leadership) employees or? Also, what about NSOs?

> Now Astro is downloaded almost 1,000,000 times per week [...]

Are these numbers supposed to provide any sense of the popularity if you're not often looking at npm trends?

Hey OP, curious how much experience you have with Rust, given that this is the only rust repo I see in your profile.

This is my only public Rust repo — I have some ongoing private projects in Rust, so I'm familiar with the ecosystem (cargo, crates, the borrow checker experience, etc.).

That said, to be fully transparent: as I disclosed elsewhere in this thread, the Ferrite codebase is 100% AI-generated (Claude via Cursor). I direct the development, test, and iterate, but I haven't written the Rust by hand for this project.

So my Rust experience is more "ecosystem familiarity + reading AI-generated code" than "battle-hardened Rustacean." This project is partly a learning exercise — seeing how far AI-assisted development can go while picking up Rust patterns along the way.