Should i learn Go or Rust? C-cucks leave

>>58435515
C

Learn C.

>>58435515
You should learn you some Haskell. You will never need to learn another language again.

Who gives a fuck OP you're still not going to have a job or a family of you're own

>C-cucks leave

Grow up and stop using the word cuck you sound immature and retarded.

>>58435515
Learn Lisp

>>58435660
cuck

>>58435515
Go is cute I like it, the toolchain/development environment feels a bit too imposed though

learn C

>>58435658
ew functional
>>58435667
t.b.h. i'd use this
>>58435660
Cuck.
>>58435648
>>58435640
>>58435873
Cucks.

>>58435905

>ew functional

>t.b.h. i'd use this

error

C

>>58435515
C++11.

>>58435515

Neither.

Both are new-age trash.

>>58435515
It depends on what you want to do. If you want to whip up some safe-ish web servers or services, Go has better standard libraries and will be faster to learn.

If you want to write an OS from scratch, then Rust will hopefully be the way of the future and cool to know. It's got a more complex syntax and is overall harder to learn than Go, though.

If you don't know C, then learn C first. If you already know C, then learning either language becomes 50% easier.

>>58435515
C++
+
+

C#

>>58435905
epic cuck meme xDDddDDD
upboats xDDDD

File: e55.png (178KB, 800x800px) Image search: [Google]

178KB, 800x800px

>>58435952
this.
Also picrelated

FORTRAN

>>58436198
>Rust will hopefully be the way of the future
Rust is at least 5 years away from being actually usable, but it will never get there. C++ will kill it by then and nobody will even remember its name.

>>58436421
>this is somehow worse than ugly slow try-catch-finally bullshit
>this is somehow worse than magic number error codes

do explain yourself

>>58436799

I could have believed him were he referring to Rust's try! macro, which I admit is a pretty awesome way to deal with error values.

However, he seems to agree that Rust is "new-age trash" so we can safely conclude that he's not talking about Rust, and therefore just a retard.

>>58435658
What if I actually want a job though?

>>58435515
Learn Java or [spoiler]C++[/Spoilers]

>>58436941
If you want a job, go to a vocational school and learn to be an electrician or a plumber

>>58436885
I write C# for a living and I think Java/C# style exceptions are a terrible fucking idea.

At least with Go/Rust I have the freedom of deciding which errors are trivial and which ones aren't. .NET will just crash the entire thing because you created a MailMessage object with a bad email address.

Plus, if I need to account for multiple, different errors in a single block of code, I can do it in a way that's neatly laid out vertically in execution order rather than appending multiple catch() blocks at the end of my method. I don't have to guess which call throws an AccessViolationException and which one throws a FormatException or whatever the fuck.

>>58437029
I completely agree that exceptions are the "goto" of C++/Java/C#, except made slightly worse by the fact that "best practices" actively encourage people to only handle a small subset of errors.

I personally love Go's error handling, and the peace of mind you can get by knowing that all of your errors are explicitly dealt with (or at least explicitly disregarded) before you even run the program. Still, I can understand why someone used to exceptions would find it a hassle at first. Rust, on the other hand, has all of the benefits of Go's error return values but without the extra code thanks to try!. I wish Go had something similar, because I dislike several other aspects of Rust's syntax.

>>58435515
Why not both?
Go is fairly easy to learn, especially if you have programming experience already.
And then you can also learn some Rust. It's not like your brain is only capable of learning one language

>>58437212
I don't know why anyone hasn't said this already. In the real world, your boss won't ask you what languages you know. He'll just say "this project is in C#/Java/etc, start reading if you haven't used it before"

Go.

>>58437212
Syntax and language idioms take a day to learn. Standard library APIs, however, take a month.

You should definitely learn C.

>>58437746
>Standard library APIs, however, take a month.
Fortunately, you don't need to learn those for rust since its standard libraries become obsolete every month, even if they're technically "supported"

rust if you are making an OS, go if you just want speed and comfy

>>58435515
What do you think Python, Rust, Java, or Go are written in?

>>58438134
go is written in go but nice try

>>58436289
Stop tripfagging, tripfag.

>>58438134
Rust is written in Rust

>>58438134
An implementation of Python is written in Python
Rust is written in Rust
Go is written in Go

>>58438140
>>58438157
>>58438159
First version of the compiler was written in C for every one of those. If you have to compile your own compiler, the first one is also written in C.

And if you start out with just Linux, as in the kernel, you can't even start with C - then you need to write the first compiler in x86 assembler.

Learn C or assembler. It's what basically any other language builds upon.

>>58438170
Most likely a bait but

What language was the first ever C compiler written in? Possibly assembly for whatever the fuck architecture. You should learn that.

>>58438212
Yes. All compilers were written in assembly before C was created. It was the first high level language suitable for writing compilers.

>>58438212
Correct, PDP-7 Assembler to be specific. Dennis Ritchie wrote it so that he and Ken Thompson could rewrite UNIX from PDP-7 Assembler to C because while hand-written assembler is faster, it's also much more complex to write. However once you get too many abstractions (ie. languages written on top of languages written on top of assembler) you lose more and more efficiency.

>>58438242
>(ie. languages written on top of languages written on top of assembler

I seriously hope you don't believe this

>>58435515
Go

https://dl.acm.org/citation.cfm?id=358210 is an interesting example of why you might not want to trust your binary C compiler (true for glibc, bsd libc and every other binary C compiler, and every compiler built on a compiler that was made with that binary compiler - it's literally turtles all the way down).

>>58438319
In essense, the only way to counter the problem is to have your own C compiler that you trust with which to verify the source code with (so-called diverse double compiling), which is an almost unmanagable task with a modern OS (kernel + base system, even if Linux arguably has none).

>>58438212
>>58438170
The HolyC compiler was written from scratch in AMD64 assembler. Now it's self-hosted.

>>58438262
Assuming you're expecting your programs to run as fast as possible, you always want to compile down through whatever intermediate languages your languages first compiler was written in, all the way down to assembler.

I realise, however, that most people who program stuff nowadays aren't interested in that.

>>58438404
Maybe so, but you can't trust it unless you DDC it with your own AMD64 compiler. Do you have one?

OP here, I'm just gonna learn Go. The creators of C say go is better.

>>58436799
Gopher is retarded. Golang eror handling is irrelevant.
>>58436885
Fuck you.

>>58438461
>creators
Who?

>I want to look cool and elitist but I don't actually give a shit about technology, should I l earn Go or Rust? Which one is more edgy /g/?

Learn OOP first, be useful, then learn those languages.

>>58438319
Err, meant gcc, clang, tcc, Visual Studio C compiler, et cetera and not the libraries.

>>58438492
>learn OOP
Learn C, then an OOP, then whatever else.

Give yourself a proper foundation, so that you might one day actually be useful.

>>58438444
>Assuming you're expecting your programs to run as fast as possible, you always want to compile down through whatever intermediate languages your languages first compiler was written in, all the way down to assembler.
>
>I realise, however, that most people who program stuff nowadays aren't interested in that.


Dude. You're assuming any language written in C transpiles into C and then to native, which is obviously incorrect. By that logic you can't write a better C compiler in C because it's going to be compiled by another C compiler.

>>58438547
All of Cs derivative languages (C++,C#, Objective-C, Limbo, Go, and probably some others) as well all the languages whose first compiler was written in C (Java, Python, Perl, and probably others) can be compiled into C and from there be compiled into assembly.

go

rust has no jobs lol

Rust isn't even stable yet, let alone mature.

>>58438657
Languages whose first compiler wasn't written in C can also be compiled into C and from there be compiled into assembly.

What was your point? The examples you gave don't compile to C, even if their compilers were originally or currently are written in C.

>>58438170

First compiler of rust was written in Ocaml, fucktard

>>58438744
No way.

>>58438744
That just means it's even further removed. OCaml was still written in C though.

>>58438657
You need to learn what compilers really do.

They don't compile to C and then to native. They compile directly to native. Of course I'm ignoring the IR level like LLVM.

Some compilers REALLY do transpile to C or other languages but that's not the norm.

>>58438765
So, they never do X, except when they do X?

You're sending me mixed messages anon.

>>58438444
>Assuming you're expecting your programs to run as fast as possible, you always want to compile down through whatever intermediate languages your languages first compiler was written in, all the way down to assembler.
This is saying that if I write a poorly optimised X-language-to-native compiler in C, then later ditch that compiler and write a better one in assembly, I should suddenly start compiling X-language to C instead of native because the random fact that the "first" compiler was written in C, despite not interacting with the current compiler at all, will magically make my programs run faster.

The language that your compiler is written in is completely irrelevant. The performance of your program is entirely dependant on what the compiler outputs.

>>58435515
PHP

>>58435515
If you aren't good at C and C++ then you should learn those first.

Between Rust and Go, I would say Rust if you want to be sensible but Go if you want a job.

Go doesn't really need to exist, all the problems that it tries to solve are already solvable by existing languages like Java and Node.js with much better ecosystems, but everyone is getting on the Go bandwagon anyways because Google is behind it (just like AngularJS).

Rust on the other hand solves a real problem, but I don't trust Mozilla to do a good job with it. Already there are some missteps like with the crate system. In a utopia, Google develops Rust and it becomes the next C/C++, while Go gets developed by Mozilla but no one gives a shit.

>>58438765
Is there a compiler that can't do source-to-source compilation? If so, why the fuck does it exist.

>>58438839
And one of the tricks to optimizing code if you actually need to do that is to do source-to-source compiling down to C and then to assembly.

The captcha for this post was "Dead End", I'm taking that as a sign.
Good bye, thread.

>>58438859
>Already there are some missteps like with the crate system

Such as?

>>58435515
learn c

every language besides c was designed without practical application in mind. using any interpreted language like java for production code shouldn't be allowed, it just wastes time on the end user.

go is basically a java ripoff, trying to market to c/c++ audience.

don't even mention rust, it's a meme created by mozilla, the headquarters for sjw >>>/trash/ software

>>58438941
amen

>>58438476
you've been BTFO

>>58438941
dumbest meme /g/babby post I've seen in my entire life

File: 82d[1].jpg (101KB, 584x649px) Image search: [Google]

101KB, 584x649px

>>58435515
Go doesn't let you place curly brackets wherever you want and tries to tell you how to capitalize names. There is absolutely no reason for these "features" other than pure autism.

Rust is far from production-ready and I doubt it ever will be.

Learn C++.

Download Python and work on your algorithmics. Don't use all the "wow cool stuff" of python, keep it simple.

When it is done, learn C. To beginning, try to convert your basic algorithms in C. Then learn about the specificities of C. Work a lot with pointers, it's essential to understand how your computer works, how memory, stack, etc... works. Try system programming, networking, etc...

Then, try some fun OOP languages, like Python (complete, not only the simple part), C#, Ruby... and, alongside, try to learn the basics of assembly programming, with 64k asm for example.

Finally, the final boss, functional programming : Haskell, OCaml, ...

Note that I never mentioned Go or Rust.

>>58439051
>no LISP dialect
if you were a comic book character you'd be Bad Advice Man

>>58439051
And I forgot C++. Try to learn C++ after some "fun" OOP, like C#.

>>58435950
c++17 when?

>>58439050
>Go doesn't let you place curly brackets wherever you want
you will find that any modern development environment enforces style

Go just takes it one step further by making the compiler anal about it

having one predictable readable style across all code bases is more valuable than letting you put it in shitty places like on a newline or something

The most important part for /g/ street cred is that you hate IDEs and OOP and never produce anything useful. Now you can fit in

>>58436799
>>this is somehow worse than ugly slow try-catch-finally bullshit
>currentyear++;
ishygddt

>>58439071
has the spec not suffered enough already?

>>58439059
(((lisp)))

File: ChuckMoore.jpg (36KB, 279x234px) Image search: [Google]

36KB, 279x234px

>>58435658
Haskell is too rigid. Forth is the true language to end all languages, and Chuck Moore is its prophet.

>>58438227
>It was the first high level language suitable for writing compilers.
Bullshit. There were compilers written in Lisp long before C even existed.

>>58439184
And they were completely unusable for real work, just like everything else ever written in Lisp.

>>58438891
>Such as?
the crate system

File: foreachrecorddo.png (19KB, 863x369px) Image search: [Google]

19KB, 863x369px

>>58435515
Learn Pascal ya dunce.

>>58435515
Learn C.

(Tfw too smart not to manage memory myself)

>>58435515

I'd say learn C.