It's low friction.

Why using GitHub for the donnos tho

Is it just me, or is the "among others" in the title made it sound like an outbreak, instead of referring to other projects?

Get well brother.

As a son of a specialist physician, I know full well how hard it can be to connect the dots between random symptoms and a problem that's actually in the brain. It's not rare for such confirmed diagnoses to become case presentations (which is how I know 😉).

I don't think this is ai written. It seems like a very stream-of- consciousness diary rather than an attempt at making anything understandable.

Actual programmers using it as a proper tool should produce output indistinguishable from actual programmers not using it at all. That there even is (often) a visible distinction is a big part of the problem.

Notably, it even explicitly says in the proposal that it shouldn't require any policing. Instead, obvious cases are more important.

From the policy in the PR:

The policy's guidelines are roughly as follows:

It's fine to use LLMs to answer questions, analyze, distill, refine, check, suggest, review. But not to create.

LLMs work best when used as a tool to write better, not faster.

We carve out a space for "experimentation" to inform future revisions to this policy.

So... No, it isn't.

Note that there are times when using a LLM to create code is allowed. Reading the doc explains the nuance.

is this a blanket ai ban though?

I actually had lots of fun writing a clojure compiler in rust that would target wasm. This allows to write it all in rust and then get it to self-host bit by bit.

Nice! I hope they follow through.

One thing I appreciate about Rust is that the developers seem to move thoughtfully and apply a fair bit of rigor. It may appear they move slowly at times, but I like their approach.

Yeah, that totally makes sense.

Agreed, but hopefully they're being used more for "Let's pause for now while we figure out a good way to filter out true AI-Code-Kiddies slop from actual programmers using it as a proper tool" rather than perm bans

This looks really cool, skimmed chapter one looks really well laid out.

My dude rewrote the project in Rust 25 minutes after writing it in Python. Impressive.

no allocation churn under heavy alt-screen TUI workloads (vt100 0.16 leaks tens of GB under multi-hour claude-style streams; this does not).

Interesting stress test you got there.

Probably worth cross-posting to !bevy@programming.dev 🙂

Nice little demo!

Screenshots would be good...

Cool. Thanks for clarifying that up. I may check it out (if I ever have the time).

Hi! Sorry that happened. Feel free to ping an issue that was closed silenty but should not have been. I'll have a look.

Fully decoupled. I have a close eye on Rust web frameworks but so far they seems not as production ready as good old TypeScript. Leptos is the one I would like to use if it become more mature in the future.

Congratulations.

I should probably look this up instead of asking, but how decoupled is the registry and backend code from the web frontend?

Is it possible for an external project to, for example, develop a fully functional alternative in Rust/WASM?

I wish feature requests won’t be closed silently as completed