Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Why I love Rust

speakerdeck.com

Post reply on HN
Print view View original

51–60 of 159 posts

Re: Why I love Rust

#51

Post by neppo »

pcwalton wrote: post #23
hellofunk wrote: post #19

Earlier quoted context omitted.

I disagree. As others have pointed out, the demand for C++ jobs is still much higher than Rust jobs, so I think my answer still stands as a way to set yourself apart when thinking of a new language to spend a few months on. Ideally, one would learn Rust and C++ both and see how they differ, and why.

> I disagree. As others have pointed out, the demand for C++ jobs is still much higher than Rust jobs, so I think my answer still stands as a way to set yourself apart when thinking of a new language to spend a few months on. It's not going to be a particularly interesting thread if everyone who works in a language that trends higher than Go on Google chimes in to say "you should learn my language instead, because it…

OPs asked which language to learn from a career perspective, so C++ is good advice in that respect

Re: Why I love Rust

#52

Post by k__ »

pcwalton wrote: post #14
mcpherrinm wrote: post #3

Earlier quoted context omitted.

While I'm bullish on Rust being a big language in the next few years, there's not much production use yet -- it's still pretty immature from a production tooling point of view. Go, on the other hand, has a lot of adoption. So if you're looking for a language to use on the job today, it's gonna be Go.

> it's still pretty immature from a production tooling point of view. I think that the production tooling for Rust is pretty good. For example, it has a package manager that everyone uses, with features like lockfiles that are specifically designed for production. Not many languages have this. It's undeniable that Go is more popular than Rust, but I think "production tooling" is not the reason.

Rust and Go are going into different directions.

Rust is trying something new and Go tries to only use the stuff that worked in the past.

It's no surprise that people favor Go instead of Rust.

Also the last time I saw a video about a low level language discussion, only Rust had a dev there nobody really knows. C++, D and Go had prominent people speaking for them.

The tooling really isn't the problem, as far as I can tell, Cargo is really one of the best package manager out there.

Re: Why I love Rust

#53

Post by 0xFFC »

derefr wrote: post #34
fmstephe wrote: post #31

Earlier quoted context omitted.

This is good advice. I am totally confused by the Rust vs Go debate. They occupy such different spaces.

I think the reasoning behind the debate is that, together , they mostly obsolete C/C++. Go takes the high-end and Rust takes the low-end, and there's no niche left for C to occupy in the middle. I guess the real answer is, if you want to learn "the language that people will be using instead of C in ten years"... learn both of them.

I don't think so. Of course, there is space for Rust and Go. But that does not mean there will be no niche for C and C++. That is simply not correct. Ignoring C and C++ mean you are ignoring maybe billion $ industry around them . and That is simply wishful thinking.

Re: Why I love Rust

#54

Post by clouddrover »

weavie wrote: post #21
clouddrover wrote: post #9

Earlier quoted context omitted.

The TIOBE Index for January, 2016 has Java at number one. Rust is at 47 and Go is outside the top 50: http://www.tiobe.com/index.php/content/paperinfo/tpci/

Visual Basic.NET more popular than Javascript? Assembly language more popular than Ruby? That doesn't seem right to me.

I don't find it too surprising. Check out IEEE Spectrum's index from 2014:

http://spectrum.ieee.org/static/interactive-the-top-programm...

You can break it down by classes of development (web, mobile, enterprise, embedded) as well as weighting (Spectrum, trending, jobs, open, custom). Spectrum's index (even though it's from 2014 and includes things TIOBE doesn't like SQL) isn't so very different from TIOBE's index.

Re: Why I love Rust

#55

Post by humanrebar »

zvrba wrote: post #40
wobbleblob wrote: post #35

Earlier quoted context omitted.

The problem is that C++ is a language where the "top 150,000 most essential things to get you started with C++" is a volume that spans several book shelves. Even Bjarne Stroustrup allegedly rated his own C++ skills at maybe 7 out of 10. If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level.

> If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level. This is nonsense. Perhaps it's true to some degree if you try to "learn" C++ from tutorials of dubious quality rather than from a decent book.

You sound like someone who has never really explored C++ lookup rules.

Re: Why I love Rust

#56

Post by jeremyjh »

wobbleblob wrote: post #35
hellofunk wrote: post #15

Earlier quoted context omitted.

I actually think you'd go far to spend 3 - 4 months learning C++. Almost every language you can likely encounter in your career will use some feature that will get introduced to you in C++, especially modern C++, and, almost any language will be easier to learn and use after first going through a C++ learning curve. Besides, C++ is still the big player, more than all others. Even Apple's new language Swift is written…

The problem is that C++ is a language where the "top 150,000 most essential things to get you started with C++" is a volume that spans several book shelves. Even Bjarne Stroustrup allegedly rated his own C++ skills at maybe 7 out of 10. If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level.

> If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level.

This is ludicrous. Depending on your back-ground and the amount of time you spend working in the language each day, a journeyman level competency can be had in just a few months. Honestly this sounds like a comment from someone who has not done much C++. Please correct me if I'm wrong.

Re: Why I love Rust

#58

Post by humanrebar »

jeremyjh wrote: post #56
wobbleblob wrote: post #35

Earlier quoted context omitted.

The problem is that C++ is a language where the "top 150,000 most essential things to get you started with C++" is a volume that spans several book shelves. Even Bjarne Stroustrup allegedly rated his own C++ skills at maybe 7 out of 10. If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level.

> If you start with C++, you're committed to a multi year project, that's what it takes to advance from novice to junior level. This is ludicrous. Depending on your back-ground and the amount of time you spend working in the language each day, a journeyman level competency can be had in just a few months. Honestly this sounds like a comment from someone who has not done much C++. Please correct me if I'm wrong.

I agree with GP and I've been doing C++ for a long time. There are a lot of dark corners that aren't a problem until they suddenly are. Most C++ devs don't really understand iterator invalidation, for example.

Re: Why I love Rust

#59

Post by icen »

jokoon wrote: post #57

I know C++, and have never encountered the 'let' keyword, until I tried some haskell. What does let mean ?

It just means to bind a variable:

    let x : u32 = 0;
In Haskell, it's used for temporary definitions, or pure definitions in do blocks:

    let f = \x -> x + 1 in f 2

Re: Why I love Rust

#60

Post by oever »

curun1r wrote: post #50
middleclick wrote: post #2

I want to spend at least 3-4 months learning a new language but just can't figure out if I should spent time learning Rust or Go. I am thinking more of it from a career perspective than interest.

Disclaimer: I say this having spent much of last year learning Go and the last couple months learning Rust. I'm a big fan of both languages. I see Go as my go to language for more situations right now, but I think that once Rust has matured a bit more, I'll choose it for more and it will probably become more useful to me than Go. I doubt I'll ever get to the point where I'd choose it for everything over Go, but I can…

I've programmed only tiny bits in Go and Rust, so I will not comment on those languages. My main programming languages have been C++, Java, JavaScript and XSLT. Going from that background to Haskell is mindblowing. The language is very clean and there is very little mental capacity needed for worrying about errors because many errors that are possible in other languages are ruled out entirely or hard to make in the first place.

Currently, I'm writing a website with Yesod. In Yesod, the URLs on the site are grouped in types and database queries are constructed from these checked types. Any change in database scheme will simply give a compile error.

Rust also sounds attractive, but I think the web stack is not as nice as Yesod yet.

Post reply on HN