←back to thread

269 points amazonhut | 4 comments | | HN request time: 0.631s | source
Show context
ramon156 ◴[] No.45248373[source]
Cool stuff! I can see some GPT comments that can be removed

// Increased for better learning

this doesn't tell me anything

// Use the constants from lib.rs

const MAX_SEQ_LEN: usize = 80;

const EMBEDDING_DIM: usize = 128;

const HIDDEN_DIM: usize = 256;

these are already defined in lib.rs, why not use them (as the comment suggests)

replies(5): >>45248872 #>>45249589 #>>45249956 #>>45250796 #>>45251881 #
1. ericdotlee ◴[] No.45249956[source]
Do you think vibe coded rust will rot the quality of language code generally?
replies(2): >>45250350 #>>45251392 #
2. adastra22 ◴[] No.45250350[source]
These things will be corrected over time.
replies(1): >>45250603 #
3. yahoozoo ◴[] No.45250603[source]
How do you mean?
4. 6r17 ◴[] No.45251392[source]
For AI you definitely need to clean up and I think even targeted learning on some practices would be beneficiary ; for users ; it depends on the people, and I'd argue that vibe-coded rust can be better than just "written-rust" IF the important details and mind of the user are actually focused on what is important ; Eg ; I could vibe-code a lock-free well architect-ed s3 - focus on all the important details that would actually make it high perf - or write some stuff myself 10x slower - which means I will have 10 x less time to work on the important stuff.

However what you asked is wether the vibe coded rust will rot the quality of language ; this is a more difficult to answer to, but I don't think that people who are uninterested in the technics are going to go for rust anyway - from the signals I feedback people are actually not really liking it - they find it too difficult for some reason and prefer to blanket with stuff like C# or python.

Can't explain why.