RU version is available. Content is displayed in original English for accuracy.
Advertisement
Advertisement
⚡ Community Insights
Discussion Sentiment
43% Positive
Analyzed from 1088 words in the discussion.
Trending Topics
#lines#file#code#rust#vibe#more#number#used#llm#tests

Discussion (42 Comments)Read Original on HackerNews
- there are now ridiculous vibe coded localisation in VS2026
- task manager started to not report cpu usage correctly recently (the number becomes stalled)
- file explorer display the "loading" icon infinitely on some directories
- and many other things!
Nautilus had that feature 10 years ago, good to hear they've reached parity.
Don't know what tech stack it is but I'm guessing electron judging by how buggy and slow it is
For example, until recently the main file for donet runtime GC was more than 50000 lines (it has since been split).
[0] https://android.googlesource.com/platform/frameworks/base/+/...
If you've ever used that tool you wouldn't ask this question, since it's obviously fully vibecoded.
Total: ~1,301,378 lines of Rust.
Production: 832,378 Unit tests: ~469,000 Combined: ~1.30 million lines
On top of the 832K LoC are mostly tests she answered:
> Yeap, 832,378 lines of production Rust. the +800K number is production only; unit tests are another +469K on top.
https://x.com/acolombiadev/status/2100660224298193081?s=20
No? That quote is clearly saying the opposite of your summary.
The +400k new lines were probably code comments the agents added to everything
Does this impresses/surprises anyone? Two folds: 1) I believe the most optimized JavaScript code could near the performance of this phase 1 port without optimizations. I would have gone with that first, many would think that would not be as cost efficient but: 2) optimizing the rust code will require 10x the effort of the 1 by 1 conversion, just because you now need idiomatic rust code that likely has nothing to do with a plain translation. So defeating the initial gain, there's nothing to do the bottleneck gets just pushed elsewhere
Greenlets were much faster.
Gil free python gets stuck on all sorts of python locks. It’s slow.
I’m guessing so it can interop easier with C/C++ codebases? Just a stab in the dark, I have no idea.
Though it's the same extension that can't keep its session timestamps straight, randomly hides sessions I was just in (then suddenly remembers them after going in and out of a session), and completely shits itself visually when using OpenAI's models, so maybe it really is just the latter.