go vs rust vs c vs java usage reddit

Is Go easier to learn than C, C++, Rust?

reddit.com › r › golang › comments › 195h0us › is_go_easier_to_learn_than_c_c_rust

It's simpler than Rust / C / C++ and you're likely to get memory savings from making the switch from Node. Just as an example, I rewrote a couple discord bots I had in Node to Go for some POC on savings. Went from 90 - 120MB of RAM in the Node version to about 8 - 12MB of RAM running the Go version, along with lower CPU usage. I find it easy to learn and generally fun to code in. Definitely recommend having it in your programming toolkit. Answer from eekrano on reddit.com

reddit.com › r/rust › i don't understand why people compare rust and go

r/rust on Reddit: I don't understand why people compare Rust and Go

October 3, 2024 -

I think Rust is a different language from its design. I think it should be placed along the lines of C and C++ because there is no garbage collection. Why do people compare to Rust? I think the Go language should be compared to Node or Kotlin.

Top answer

1 of 5

468

You're trying to categorize languages based on aspects of their design. But both are general purpose programming languages, which mean that they can be used to write a wide array of programs. And sometimes, those sorts of programs can overlap. My current work project is an API server, in Rust. Many people would use Go for that as well. But Rust is working well for me. So, in that sense, we can compare them, even if they're very different languages.

2 of 5

193

Both languages see themselves as a better C. Rust embraces the C/C++ focus on low-level code / zero-cost abstractions, but improves over it with a safer type system, with some decidedly Haskell influences. Go embraces C's "simplicity", but improves over it with Python-style quality of life features. So the same starting point, but nearly opposite directions. Where C / Go / Rust compete against each other is the space for tools and CLIs. For example, the entire container and Kubernetes space tends to build its tools in Go – and the world is a better place for having avoided C here.

reddit.com › r/rust › rust vs go/jvm: dev speed + safety in practice

r/rust on Reddit: Rust vs Go/JVM: dev speed + safety in practice

June 24, 2023 -

Okay, we all know that Rust is theoretically faster, even if only by a little bit. That's great, but it's not actually my main consideration.

For those with extensive experience with Rust vs. Go/JVM-based languages, have you noticed any major differences in dev speed + code safety? If we want to focus on a specific category of apps, let's say web services.

Top answer

1 of 5

110

Complex software becomes easier to write/express, and hugely easier to get right, with Rust. Simple logic is quicker to write in other GC-based managed languages. Like if you just want to jot down a note, opening Word and creating a proper formatted template is too much work. You'd just open up Notepad instead. But once your document gets up to a certain complexity and size, it becomes exponentially more difficult to manage it in Notepad. Then you find yourself biting the bullet and transferring it to Word. You cannot say which is better. They serve different needs. The trick is complexity and security, not really the type of web services. Can your ws crash and just restart? Or must it stay up 24x7, no failures accepted? Is your ws very complex or simple one-liner? These questions determine your tech stack, not the app category.

2 of 5

I've done distributed business applications in Java and library development in Rust. There was one particular business application that was probably over 500k lines of code, and had been factored into 30+ different repositories (for maintainability, ostensibly). I cannot count the number of times we had issues in production because of a NullPointerException for some edge case that we didn't think was possible. Sometimes it was subtle changes in a RPC or library, and sometimes it was our own code that was at fault. I personally broke the entire financial reporting part of the application because I used an immutable list, and some method in a different repo was expecting it to be mutable without making a defensive copy. The Rust type system and ownership model would have prevented us from introducing a lot of those in the first place, and the way dependencies are handled in Rust would meant that we got compile-time errors instead of runtime errors for many other problems. You can write unmaintainable code in Java or Rust or any other language, but Rust can prevent you from introducing several entire categories of potential problems even if the code is bad.

Videos

42:14

YouTube

Java Is Better Than Rust - YouTube

Dilemma of programming Language Choices | C++, Golang ...

August 18, 2023

58:36

YouTube

RUST vs C++, Java, Go with Micah Wylde - YouTube

October 21, 2023

View all

reddit.com › r/golang › is go easier to learn than c, c++, rust?

r/golang on Reddit: Is Go easier to learn than C, C++, Rust?

January 13, 2024 -

I am not a pro developer, but I code some small tools for myself time to time, in JS. But I hate how much memory and disk space node or even bun take up. So, I was thinking of learning a simple binary compiled language, both to just learn more programming and to use it for my little personal projects. From what I've read so far, everybody seem to say that Go is the easiest to learn between C, C++, Rust, and it's fairly fast and optimized. What would you say? Is that true? What would you recommend me learn?

Rust is definitely harder to learn, and I don't think it's even close. C++ is a much bigger language. I don't know that it's any harder to learn a subset of C++ like 99% of C++ programmers do. If you wanted encyclopedic knowledge of every corner of the language, it'd be harder to learn. Plus there's a lot of standard library, boost, etc. that's not exactly part of the language but it's definitely part of using the language. C is probably easier to learn, but a much bigger pain to actually use. Like the lack of strings, resizable arrays, hash/dict/map stuff, etc. You can DO all those things in C, but it's very "roll your own". Go is closer to "what if Python was performant?" Except also statically typed and also much less library support. Honestly, probably worth getting your feet wet with all of them. Somewhere past hello world, but not necessarily trying to become proficient in them. At that point, you'll know which you want to dig deeper into.

reddit.com › r/golang › why do you prefer go over rust ?

r/golang on Reddit: Why do you prefer Go over Rust ?

January 8, 2022 -

Please don’t say too simple answers like « I prefer it’s libraries » « it’s easier » or « it’s enough for me ».

Rust is regarded as a faster and safer language at the cost of productivity / complexity. Is it just that ?

Do you think Go is more a Java/python replacement or can be optimized as well to run very fast (close to Rust/C) ? Maybe is it as fast in I/O which would be the bottleneck in most scenarios ?

I’m doing my first Go program (for GCP) but I’m interested in Rust as well and I’d like pretty detailed opinions from both sides 🙂

(It can ofc be very well « it’s enough for me » btw, everyone has preferences but then some answers could just be a bit pointless if you see what I mean). I’m sure it’s a « yet another go vs rust » question and I apologize 😆

Top answer

1 of 72

179

Go has net/http in the stdlib It’s a lot easier to read Go versus Rust code Ultimately it depends on what you’re building, Rust has its place and so does Go.

2 of 72

Complexity has a real cost, in both readability and compile times. I would say it's one of the biggest reasons for Go's popularity over Rust. But at the end of the day, the reasons why these Go vs Rust questions are silly is because it shows that someone isn't thinking of different languages as different tools in their toolbox. Especially languages as different as Rust and Go. Also, there are like a million blog posts on this subject on Google...

reddit.com › r/rust › speed of go vs rust in practice/real world experience?

r/rust on Reddit: Speed of Go vs Rust in practice/real world experience?

June 23, 2023 -

Hi!

I don't want to start another language war, so let me preface this by saying I love both Go and Rust like they are my own.

That out of the way: Do you have practical/real-world experience with the performance of Go, and the performance of Rust in the same setting?

How many people worked on the codebases? Which one is newer?

I'm asking because I've got a feeling that for smaller companies, Go would in practice (not in theory) outperform Rust because Rust's design encourages the use of inefficient patterns -- like cloning a bunch where you could theoretically pass a reference

Top answer

1 of 26

For big/high load projects I think the discord use case is a good example https://discord.com/blog/why-discord-is-switching-from-go-to-rust BTW. I am pretty sure most small companies choosing Rust over Go is not because of performance but because of all the other set of advantages of Rust over Go.

2 of 26

Rust does not encourages useless cloning, it's an anti-pattern ( https://rust-unofficial.github.io/patterns/anti_patterns/borrow_clone.html ) and can be avoided 99,9% of the time, you just need time and experience to adapt to the way you develop in Rust. For the real world performance of Go vs Rust in Backend development, I have found that Rust outperforms Go by a factor of 1 to 3 times (depending on the exact use case) and uses less RAM. This performance difference should however not be taken into account if performance is not an issue for your usecases. Using Go instead of some other less performant language is already a sufficient gain in performance for most projects.

reddit.com › r/golang › why everyone keeps comparing go with rust?

r/golang on Reddit: why everyone keeps comparing Go with Rust?

June 25, 2022 -

hello im new here, i actually never used Go but im interested to learn more about it, i started using rust recently and i always see people compare Rust with Go and i don't know why? because as far as i know, Rust created the ownership system that differentiates it from any other language, which makes it special, so i wonder what is so special about Go that other languages don't have!

Top answer

1 of 23

Both are novel C-replacement-languages. Because C is seen as old and hard to use. Go takes the approach of making the language small, easy to learn, and easy to use by introducing some C++ concepts (interfaces) and easy threading (go routines) which they see as critical to modern micro-service based architecture. Rust takes the approach of improving the use cases that make the language difficult, which it sees as memory leaks, race conditions, memory handling, etc. Go usually fixed these things in “proven” ways, like garbage collection, whereas rust did them in very novel ways like the borrow checker.

2 of 23

Because if you want to build a performant, safe static binary in 2022 you’d use either Go or Rust. Both have a lot of similarities and a few major differences. They overlap in a lot of use cases, but you can easily make a decision between them depending on your priorities. Both are excellent languages.

reddit.com › r/softwarearchitecture › c++ vs rust vs go

r/softwarearchitecture on Reddit: C++ vs Rust vs GO

September 22, 2021 -

I currently write code in C#, using Console Application, Blazor, or WebForms

Question 1:
I'm looking at going into a low-level language. My interpretation of what a low-level language can actually do (like C++, Rust and GO) is quite limited. What can these kinds of languages offer which C# can't? Although I'm pretty much fluent in coding in C# I still struggle reading about the technical side of languages, so I'd prefer noob-friendly answers like C++ can make an application dedicated to cheese graters, whereas C# would be better creating an application dedicated to cheese.

Question 2:
I'm looking for a language that is still going to be big in 20 years - these three seem to be the biggest, Rust and GO being newer, but C++ still being in applications like Googlebot (backend) despite being ~40 years old. Which would be the better option for a newbie, and why?

Top answer

1 of 3

Go isn't really low level. It has a runtime and GC. It's basically a popular alternative to Java and C# for web services. I remember reading that it isn't that fast, as claimed. Rust is much closer to being a low level language. It doesn't have a runtime or GC and that means it's more suitable for lower level programming. I think it's a good stepping stone toward the lowest level which is the C language. My company mainly uses C#. We choose Rust for a couple projects because it can export a C like FFI. This means basically every language can import that library. It's high level and modern with great package management while accomplishing low level FFI without losing memory safety. C++ will never go away, it's too deep in very important projects. It's definitely low level, but not as low level as C.

2 of 3

What are building ? Who will use it ? Is it for fun ?

reddit.com › r/golang › why should i use go over rust, java, or python?

r/golang on Reddit: Why should I use Go over Rust, Java, or Python?

December 23, 2023 - ... I’ve worked with both node ... also small binary and one of the easiest build systems i ever encountered ... go is not SIMPLER than Rust....

Find elsewhere

Google Bing Mojeek

reddit.com › r/csharp › c# vs rust vs zig vs go vs java for data processing

r/csharp on Reddit: C# vs Rust vs Zig vs Go vs Java for data processing

October 5, 2023 -

Last week, I posted this benchmark in the rust and golang subreddit and the community made suggestions that sped up the code...So I thought it'd be fair to post it here to get some feedback.

I made a direct port of the go version for c# and it's not performing as expected. It's getting beat by dart, swift, f# etc. so there's obviously something wrong. Nothing sticks out to me though so I hope someone here can optimize it.

nb: This is my first time writing c#.

Repo: https://github.com/jinyus/related_post_gen

Top answer

1 of 5

I created a PR to make the CSharp implementation use AOT (ahead of time) compilation on .NET 8. This made it significantly faster on my machine. I didn't investigate your benchmarking harness, so I don't know how to wire it into your benchmarks. You might need to modify the RuntimeIdentifier in the related.csproj to target your local platform, if you aren't on win-x64. I didn't modify the logic of your implementation at all, just converted it to use AOT. This avoids the overhead of the JIT compilation that happens on first run. This was a good excuse to figure out the System.Text.Json source generator stuff, which I'd never used before. Edit: for some shameless self-promotion I did a similar comparison of AOT recently: https://github.com/markpflug/data-convert

2 of 5

I've checked a few implementations, and as far as I can see, none of them include the warmup stage, so essentially, this is a huge disadvantage for jit runtimes against AOT and V8. For example, java jit solution probably would be way closer to java GraalVM, if not even faster. I suggest you add a requirement for a warmup stage for every benchmarked unit.

reddit.com › r/golang › golang or rust

r/golang on Reddit: Golang or Rust

July 1, 2022 -

Hi, Recently, I’ve decided to learn a new programming language. However, I can’t decide between rust and go. Could you simply say what are the advantages of golang over rust?

Top answer

1 of 5

It took me less than a week to become productive with Go. It took me three months with Rust. One of the hardest parts of learning Rust is not Rust itself but the Rust ecosystem. Rust’s std lib is much smaller than Go’s, which results on having to use many third party crates. It’s not uncommon to have dozens of third party crates in a Rust project vs a couple in a comparable Go project.

I found this to be a very frustrating part of learning Rust. What third party crates should I use and which can I trust. Allot of cognitive overhead is sucked up making heads and tail of a fragmented ecosystem.

At the end of the day, both languages are very good but they are designed for different purposes. I’d recommend learning Go and then Rust.

2 of 5

They are quite frequently used for vastly different reasons.

Both Go and Rust compile to native code. They can both be extremely fast and performant.

Go has a smaller base language syntax. Its focus is on speed of compilation and speed of development, readability/maintainability of code, and it has language features specific for safe concurrency. It's garbage-collected, so you don't have to worry about memory management at all. It has rich support for web-based programming tasks built into the standard library.

Rust has a large and robust language with a much deeper (read that as "more useful" or "more cluttered", depending on your needs) syntax. Its focus is on non-garbage-collected memory safety and speed of code execution. Compile times can be MUCH slower than Go, but depending on what you're doing execution speed can be MUCH faster, especially if you are calling any standard C/C++ libraries.

If you're looking to do standard business or web apps, want a simple to learn language with incredibly fast development cycles, and have no need to call C/C++ libraries (or don't care about a few hundred millisecond call time), I'd say pick Go.

If you want to do game development or embedded systems development, care about compiled code size, and must squeeze every possible drop of performance out of the hardware while not caring that compilation times can end up higher than C++ code, then choose Rust.

reddit.com › r/golang › rust vs go

r/golang on Reddit: Rust vs Go

November 6, 2020 - Neither are primarily functional languages (like Scala or Elixir, for example), and neither are exclusively object-oriented (like Java and C#). Instead, while both Go and Rust have features associated with functional and object-oriented programming, they're pragmatic languages aimed at solving problems in whatever way is most appropriate, rather than forcing you into a particular way of doing things.

reddit.com › r/learnprogramming › language choice for open source and gsoc preparation: go vs rust vs java

r/learnprogramming on Reddit: Language choice for open source and GSoC preparation: Go vs Rust vs Java

December 21, 2025 -

Hi everyone,

I already have a good foundation in Python and I’m preparing early for Google Summer of Code–style open-source contributions.

I want to invest time in ONE additional language that:

Is commonly used in active open-source projects
Allows faster onboarding and meaningful contributions
Is useful long-term beyond just interviews

I’m considering Go, Rust, and Java.

I’d really appreciate advice from developers who have contributed to open source or mentored students: Which language has helped you contribute most effectively and why?

Top answer

1 of 2

As a Java dev, my vote is either Rust or Go

2 of 2

Rust is definitely not the mature framework of something like Java or even Go. It’s rough around the edges and its developer support can sometimes leave a little to be desired. That said, I have built and worked on some super fun open source projects with it, and recruiters definitely reach out a ton about it. End of the day, you’ll have a blast no matter what you chose. With the advent of AI programming, coding is becoming less about syntax of language, and more about high level design and Architecture and depending on your project needs, different languages have pros and cons TLDR: Learn concepts, not syntax. Have a blast building cool stuff

reddit.com › r/rust › why go and not rust?

r/rust on Reddit: Why Go and not Rust?

September 16, 2019 - ... Go is fast enough that you probably have issues other than code slowing you down (which is where parallelism though channels works well enough too). It's Java speed without the jvm.

reddit.com › r/golang › second programming language to learn rust vs go. which one will make me grow more as developer ?

r/golang on Reddit: Second programming language to learn Rust vs Go. Which one will make me grow more as developer ?

May 25, 2021 -

Hi guys,

I am Python dev for almost 3 years. Mainly working in data engineering field. As I am self taught developer, and Python is my first language I want to expand my skills, and knowledge.

Two languages that I am considering is Rust and Go. I saw some threads about Rust vs Go, but most of them were regarding finding job in given language. I am totally not interested in learning for job, I am interested in learning to become better developer.

And I would love to get some advices, which language have a lot of concepts that I can't find in Python, and which will mabe change my perspective and in the end will make me better dev (also in Python)

What's your opinions ? Maybe there is a better candidate for 2nd language to expand skills.

Top answer

1 of 44

155

Rust Will be a very deep dive coming from Python. Start with Go, and look at Rust after doing a few projects in Go

2 of 44

I'd say that go is the more pythonic of the two, that is an "easy" language that can be used for little, medium and big projects. It shines for microservices, and has a battery-included feeling like python has. Rust is more "exotic", and it is meant as a C for the 21st century, fast, secure and low level. Just my 2c

reddit.com › r/programming › should c programmers learn c++, go or rust?

r/programming on Reddit: Should C Programmers learn C++, Go or Rust?

July 31, 2018 - In my opinion the main promise was that Go was simpler than C/C++; and Java is boring to no ends. Note that none of them went to Rust, so the use cases are not the same.

reddit.com › r/rust › rust vs go: a hands-on comparison

r/rust on Reddit: Rust Vs Go: A Hands-On Comparison

September 27, 2023 - Heap allocation in Go is not cheaper than in Rust. Go GC is not compacting. Compacting GCs like Java do have some edge if your app wants to allocate gigabytes of garbage, because they allocate by a pointer bump.

reddit.com › r/golang › go is better than rust (for networked server side applications meant for scale)?

r/golang on Reddit: Go is better than Rust (for networked server side applications meant for scale)?

January 30, 2023 -

Stumbled upon this post on https://lobste.rs/

Any thoughts on the opinion that Go is better than Rust for (i) networked server side applications and (ii) enterprise scale applications ?

P.S: I am not the author of this blog post.

Top answer

1 of 19

I read it two days ago and the conclusion I got was: Use go if you want to use go Use rust if you want to use rust

2 of 19

I always take "language X is faster than language Y" comparisons with a grain of salt. These comparisons are always based on optimal implementations, but in the real world, the implementation won't be optimal, it will be idiomatic. I'm sure that Rust would outperform Go on multithreaded workloads if you compare the theoretically optimal implementations in each language, but I bet the easiest Go implementation would outperform the easiest Rust implementation. To me, this is where Go really shines. The path of least resistance in Go tends to lead towards performant, stable, maintainable code.

reddit.com › r/rust › rust vs go

r/rust on Reddit: Rust vs Go

October 19, 2022 -

I’m right in the learning process for Rust so please forgive my warlike header :) Charter 12 of the book done and I think I understood lifetimes now, after reading the 10.3 about 3 times… The sentence „…Rather, we’re specifying that the borrow checker should reject any values that don’t adhere to these constraints…“ made it. Ahh you’r not specifying any lifetime, but enforcing the refs to have a specific lifetime. Got it.

Ok to my question. Right now we are building a relative large web project at work in go. I do the backend mainly. I am very interested in Rust, on the one hand, because I like to learn new stuff, and on the other hand, because I’v been reading a lot about the safety of Rust. So I started to rewrite the backend also in Rust in my free time, just to have a better understanding of the language and a living example I can compare to. Works great till now. I have the webserver up and running with actix, jwt is in, sqlx for database and of course serde for json.

What I learned till now in Rust is superb. Errorhandling with ?, unwarp/expected, Enums!!!, structs with initial values (nice nice), fully integrated generics and so on. All really nice features. But till now, the only security advantage I see is Null-Pointer, the match expression, that forces you to handle all cases, and the handling for maps and slices which work much cleaner with the borrow concept and can be a nightmare in go. Go has no dangling pointers, so the borrow and lifetime concept is just not needed.

So, what big security features do I miss? I know I am only half the book, but it seems like the whole borrow and lifetime concept, which makes the language really safe (compared to C++ or C), is owed to the non-GC feature, but if one is OK with a GC, there do not seem to be that much advantages over go, security wise.

As written, don’t take this as a flame post. I’m neither a Go fanboy nor a Rust hater. And our next project will definitely be in Rust, I’m luckily in a position where I can decide that. I’m just interested in your opinion, since you for sure have much more expirience in rust than I do.

Top answer

1 of 5

214

So, what big security features do I miss? Safe multithreading (no data races) without additional overhead. Very few languages or runtimes offer that and GC won't automatically help here.

2 of 5

114

Ownership and the borrowing system prevents more issues than just simple memory safety. Think about this infamous example : func appendAndChange(numbers []int) { newNumbers := append(numbers, 42) newNumbers[0] = 666 fmt.Println("inside", newNumbers) } func main() { slice := []int{1, 2, 3} fmt.Println("before", slice) appendAndChange(slice) fmt.Println("after ", slice) fmt.Println("original slice is intact") fmt.Println("------") slice = append(slice, 5) fmt.Println("before", slice) appendAndChange(slice) fmt.Println("after ", slice) fmt.Println("original slice is modified") } It works in a pretty mysterious, for newbie, way and even experienced gophers are often confused about why two calls to appendAndChange behave differently. Sure, that code is of “don't do that” variety, but that's precisely the point: where in Go (C++, Javascript, etc) you have to follow the written (and, sometimes, unwritten) rules to ensure that your data is safe… in Rust it's the default. And, of course, if a programmer never makes any mistakes then program would be correct in any language. The biggest bane of software development, something that often requires days-long debugging sessions is a shared mutable state. When one part of your program changes the variable and the other part of your program doesn't expect that (the whole confusion about slices in the example above is of that variety, too). Rust forbids shared mutability by default. This prevents way more errors than just memory issues. If you have the right to modify some object then you know that no one else would be able to look at it while you are doing that this forms the basis of Rust's fearless concurrency among other things. And when you deal with a shared mutable state via Rc or Mutex… it's very explicit in your code, you couldn't accidentally miss that. Also: things which you said are just “nice”… they make your program more robust, too. It's also a safety aspect. In Go if you get some reference you can never be 100% sure if it may or may not be nil… but in Rust it's not an option. Even if you have Option then it's your decision to do unwrap and accept the danger of crashing in that place. In Go you can never be 100% sure whether a certain variable is nil or not… because the only tool which guarantees “no nil dereference” safety are your eyes. And that's quite unreliable tool. And that's the pervasive theme: Rust tries to ensure that you would handle errors properly, but gives you opt-out for cases where you don't need that while Go gives you tools which work properly… as long as you “hold them right”.

reddit.com › r/programming › rust vs go in 2023

r/programming on Reddit: Rust vs Go in 2023

August 27, 2023 - If you're writing a little command-line tool, say a more enhanced version of cd which remembers all your previous directories and can go back to a specific one, then your choice is either Rust, Go or C/C++, because it needs to execute with no user-observable difference in performance.

Medium

medium.com › @dexwritescode › comparison-between-java-go-and-rust-fdb21bd5fb7c

Comparison between Java, Go, and Rust | by Dex | Medium

July 2, 2023 - Here Java uses two orders of magnitudes more memory than the Go and Rust counterparts, just sitting in memory doing nothing. That is a huge waste of resources. Lets hit the API with requests using wrk and observe the memory and CPU usages, and ...