Rendered at 11:48:26 GMT+0000 (Coordinated Universal Time) with Cloudflare Workers.
ale 1 hours ago [-]
> Disclaimer: This article was created with the assistance of AI and reviewed by the JetBrains RustRover team
Honestly there should be a filter for these types of articles. I’m not going to bother reading something another person did not even bother writing.
pizza234 54 minutes ago [-]
"AI-assisted" != "AI-written". People who have AI write their articles entirely surely don't mention it at all.
cdud3 2 hours ago [-]
You don't. This days run your C/C++ code through AI and fix the issues it found. That gives you more in shorter time.
faangguyindia 1 hours ago [-]
I rewrote my Haskell project in Rust.
memory usage dropped to half, execution speed is now 2x. Cross deployment is easy from silicon man to x64.
There are many low level optimizations available which i can exploit, compile is super fast for my project so development experience is better.
LOC dropped to half of the original.
Rust made life so much easier :)
ivanjermakov 2 hours ago [-]
Remembering times when JetBrains was about carefully crafted Java intellisense. And I don't think demand for such tools is gone.
zombot 2 hours ago [-]
For Qt apps written in C++ I don't see how that could work yet.
fukaiall 1 hours ago [-]
1. Hop around a few rust communities and fill yourself up with full love of rust and hatred against c/c++.
2. Ignore any technical tradeoffs and considerations but solely lean on your guts and hypes on the Internet.
3. Ask Claude to rewrite the entire codebase to rust. Boom! Now you’re allowed to show off yourself on LinkedIn and HW as a super great rust engineer.
imthias404 2 hours ago [-]
Its kinda hard to understand the point somebody's making, when its articulated/made up by AI. Slop.
pjmlp 2 hours ago [-]
Similar experience to applications written with Claude slop.
alex_suzuki 1 hours ago [-]
[dead]
himata4113 3 hours ago [-]
I've seen someone rewrite a wireguard proxy in rust for performance without realizing that it's just a daemon that interacts with the kernel to setup routing... But hey, at least the key generation is faster!
forrestthewoods 3 hours ago [-]
Step 1. Start with a library that is a fat wrapper around a massive C++ library that does all the hard work
Step 2. Rewrite only the wrapper using already written tests.
Step 3. Get internet points because an LLM Rewrote it in Rust!
ramon156 2 hours ago [-]
To be fair, big refactors like this need to be done gradually. This is obviously the first step.
Next step can be to port it using e.g. tractor tooling and have a bunch of unsafe calls you need to implement. It's a really fun puzzle. The goal is to have no more cpp dependency
scaredginger 3 hours ago [-]
They didn't need the disclaimer for this to be obvious AI slop
Honestly there should be a filter for these types of articles. I’m not going to bother reading something another person did not even bother writing.
memory usage dropped to half, execution speed is now 2x. Cross deployment is easy from silicon man to x64.
There are many low level optimizations available which i can exploit, compile is super fast for my project so development experience is better.
LOC dropped to half of the original.
Rust made life so much easier :)
2. Ignore any technical tradeoffs and considerations but solely lean on your guts and hypes on the Internet.
3. Ask Claude to rewrite the entire codebase to rust. Boom! Now you’re allowed to show off yourself on LinkedIn and HW as a super great rust engineer.
Step 2. Rewrite only the wrapper using already written tests.
Step 3. Get internet points because an LLM Rewrote it in Rust!
Next step can be to port it using e.g. tractor tooling and have a bunch of unsafe calls you need to implement. It's a really fun puzzle. The goal is to have no more cpp dependency