Which is better out of Go or Rust?

Which is better out of Go or Rust?

Other urls found in this thread:

youtube.com/watch?v=WVZ7yMvxImo
nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/
barrucadu.co.uk/posts/etc/2016-08-25-three-months-of-go.html
twitter.com/NSFWRedditImage

Rust. Garbage collectors have no place in systems languages. RAII is GOAT.

What are you trying to do?

@59486093
neither they are both terrible languages B)

what is goat

Is that scale in pounds or kilos?

Rust is a marginally better version of C++ with no future.
Go is a marginally better version of C with a bright future.

>RAII is GOAT
>Being unable to control variable's lifetime/being forced to resort to stupid tricks is GOAT

Rust for performance + safety
Go for ease of learning

Your post is marginally above the acceptable bait range

youtube.com/watch?v=WVZ7yMvxImo

@59486171
you are so dumb B)

Go is even slower than Java kek

Go has a niche in networks programming where it excels.

Rust is the best of the two if you're looking for a good general purpose systems language.

more than counterbalanced by the fact that Java programmers are slower than Go's

>implying Go's any better
get rekt nomad.so/2015/03/why-gos-design-is-a-disservice-to-intelligent-programmers/

>The key point here is our programmers are Googlers, they’re not researchers. They’re typically, fairly young, fresh out of school, probably learned Java, maybe learned C or C++, probably learned Python. They’re not capable of understanding a brilliant language but we want to use them to build good software. So, the language that we give them has to be easy for them to understand and easy to adopt.
– Rob Pike

>Rust is the best of the two if you're looking for a good general purpose systems language.
Not really; it's destined for irrelevance, as it *still* doesn't have a killer app in the current year (e.g. Rails for Ruby, Docker for Go). Furthermore, C++17 has done a lot to close the usability gap between the two languages.
You don't have to believe me; just compare the number of job postings for Rust with the ones for Go. There's a difference of 4 orders of magnitude.

C++ is forever doomed to be unsafe cancer due to legacy libraries/code compatibility. Don't even try to argue there

>le killer app
Servo.

Which is better out of dog poop or cat poop?

that argument applies equally to Rust, as most of its bindings for existing libraries/frameworks are written in C

>most of its bindings for existing libraries/frameworks are written in C
Rust is not C compatible unlike C++

Docker can be found in literally every Fortune 50 company.
Servo can only be found on the semen-stained T420s of HN-addicted autists who spend their Saturday nights writing meme libraries in Rust.

Are you upset?

I don't like Go, but it has a purpose and they're trying to make it more suitable for that purpose. Rust just wants to be everything like a hipster version of C++.

Given that I were forced to use one, I'd pick Go. As it stands, I can thankfully use neither.

Cat poop obvs.

>THIS mad

poor way to concede the argument

Neither.

Go doesn't really fill any niche that we need filled in the world of programming languages, whenever I look into it I can only ask myself why anyone would use it when there are so many better alternatives.

At least Rust is actually attempting to fill a gap, to say it is succeeding is debatable, but it is certainly trying.

You were arguing? Dumb frog poster

Anal
devestation

>Comparing Rust with Go
You don't know any of the languages OP. You are just here to shitpost, just admit it.

Satania is made for anal.

given that Java rekts the shitty LLVM backed garbage Golang, probably Rust

also speaking of Go
what the fuck does Go do that Java doesn't?

the JVM is faster than the binaries Go makes and unlike the Go binaries, jars/wars/ears/class files are actually 100% portable as long as a JRE or greater, is available on the targeted platform.

WHY

>what the fuck does Go do that Java doesn't
Have a good design.

Rust.

Go is for retards who can't program.

those kind of people are what makes a project successful

how is interface{} abuse and no generics good design?

effortless concurrency

certainly better than this shit

It lowers compile times and simplifies the language per their original goals.

People got along fine without generics for decades.

Threadly reminder that Sup Forums belongs to Maki

but that's wrong, you hag

Kill yourself.

don't bully her! she's just confused

maki maki gimi the faki

I think you mean Horo or Amu.

How is C++ C compatible?

>tfw you will never get a deathgrip handjob from satania

>Japan
What do you think?

>systems language
>RAII
You fucked up.

The fuck?
The only things Go has in common with C is the lack of abstractions, and ALGOL syntax.
Other than that they couldn't be farther apart.

C++ can natively interface and build with C, no complex FFI needed.

source level compatability was a fucking mistake

For those of whom have forsaken the TRUE queen of Sup Forums, I have only the upmost pity.

>true queen of Sup Forums
>not pic related
I don't even care if you kill yourself, you are worse than an animal.

source level compatibility is why C++ took off at all

yet every other language does completely fine with a FFI and separate toolchain

Sorry wrong pic

Literally subnigger tier
Even rats are better than scum like you.

stay mad newfag

>projection

lain is older.

One fuck with a script to make a post every day trolling Sup Forums does not equate to the queen of Sup Forums. Only one comparable is yuki

Fucking gross you furfag

>tfw too intelligent to use go

>Only one comparable is yuki
So what're stating is that you have pleb taste and all of your notions should be regarded as entry tier shitposting? Okay gotcha.

it's Sup Forums culture man not personal preferences.

Which is better, chlamydia or gonorrhoea?

Rust if you want to be compiled but secure af. it's a deeper learning curve, but it's relatively efficient on run time. Would use this over C to make a server program (for security alone) - C++ too if i wasn't a good C++ coder (it's easy to learn shittier past practices than to learn the c++17 idiomatic way when it comes to online help, so you may sometimes find yourself reading solutions online that aren't as safe)

Go if you want the hipster lang of the future. I haven't used it much to give it a fair shake. seems easier, less convoluted, also there's a significant amount more well known software that was made with Go over Rust (See Docker, IPFS, gogs, etc.,)

>secure af
Meme, secure af is done with actual formal verification. Rust basically gives you address sanitizer and automatic RAII.

RAII is primarily a feature of systems languages, user, and it is primarily useful for managing low level resources.

add static analyzer in cargo

I am a distributed systems researcher. I have been programming in Go full time for 3 years. I have no experience with Rust but I can weigh in on garbage collection.

Garbage collection is slow. When I write a go program initially I use judicial makes, and appends which invoke allocs. The code is usually concise, correct, and a bit slow due to garbage collection.

Novice Go programmers can stop here, and have working code. I consider this a benefit over C/C++, my other languages of choice.

With even a little bit of Go experience, and knowledge of how memory works, a go program can be modified to rarely and optimally invoke garbage collection. I consider it a downside that I have to fight garbage collection every once in a while to get optimal code, but when it I do it is comparable to C or C++ performance, you just need a bit of skill to reach it.

No they don't.

intelligent people use the right tool for the right job.

Go is good for writing utilities for other systems, in my experience. I work on a huuuge HTTP/RESTful API implemented in C++. Perhaps I want a tool to easily interact with said API, but isn't a browser.

Instead of fighting with libcurl and rapidxml or whatever parser I need in C++, I can whack something out in half an hour in Go.

LMFAO

Here's some recent impression of Go: barrucadu.co.uk/posts/etc/2016-08-25-three-months-of-go.html
The Good:
> Incredibly easy to pick up
> Garbage collector keeps getting better and better
> Style wars are a thing of the past
The Neutral:
> Code generation seems to be the accepted solution to a lot of problems
> Strict, not lazy, evaluation
> The standard library is not so great
The Bad:
> A culture of “backwards compatibility at all costs”
> The type system is really weak(No generics, No sum types, No separation of pure code from effectful code)
> The tooling is bad
> Zero values are almost never what you want
> Lots of boilerplate

Animal similiar to sheep

Rust, if you want to write fast, safe programs.