Comment by shlant
6 days ago
OP: https://fly.io/blog/youre-all-nuts/#but-its-bad-at-rust
> (from https://lukasatkinson.de/2025/net-negative-cursor/)
looks inside
complaining about Rust code
6 days ago
OP: https://fly.io/blog/youre-all-nuts/#but-its-bad-at-rust
> (from https://lukasatkinson.de/2025/net-negative-cursor/)
looks inside
complaining about Rust code
Plus, looks like it just hard coded vales. I see this happen a lot with AI code. Even when I try to get it to not it still tends to do it.
Issues like that are simple and just create debt. Sure, it "works" now but who writes code not knowing that we're going to change things next week or next month. It's the whole reason we use objects and functions in the first place!
Yeah, only in Rust is the maximum value of an unsigned 16-bit integer 65535.
These aren't Rust-specific syntax foibles. It's not a borrow-checker mistake or anything. These are basic CS fundamentals that it's thoughtlessly fumbling.
TBH the critique is completely valid when cursor advertised shitty code on their homepage.
the rust code in question is the example on the cursor landing page though
The current image on the landing page might be even worse. It just updates Message to MessageV1. Why would you pay money for what's a string replacement?
The comment on the right says it'll help the user with protocol versioning. This is not how you do that...