Technology

63009 readers

3545 users here now

This is a most excellent place for technology news and articles.

Our Rules

Follow the lemmy.world rules.
Only tech related content.
Be excellent to each other!
Mod approved content bots can post up to 10 articles per day.
Threads asking for personal tech support may be deleted.
Politics threads may be removed.
No memes allowed as posts, OK to post as comments.
Only approved bots from the list below, to ask if your bot can be added please contact us.
Check for duplicates before posting, duplicates may be removed
Accounts 7 days and younger will have their posts automatically removed.

founded 2 years ago

MODERATORS

310

submitted 5 days ago by [email protected] to c/[email protected]

104 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 9 points 4 days ago (1 children)

Go is fine, but it has its flaws. I prefer Rust because:

memory safety is a compiler check, not a runtime check, so you catch issues earlier
locks contain their values, so you can't accidentally do anything unsafe
no nil (() is semantically different), so no surprises with contracts
everything is an expression, which lends itself really well to FP concepts
actual dependency management at 1.0
pretty much no runtime, so calling from another language is super easy
targets WASM and microcontrollers
no pointers (not exactly true)

It takes longer to learn, but I'm about as productive with both now.

[–] [email protected] 1 points 4 days ago

Thanks, "Comprehensive Rust" is readable so far, though I haven't gotten to the "fun" (memory management) parts yet.