News for hackers. Stuff that matters.
Re:Rust in 2018: easier to use by curiousGambler on Sunday January 14, 2018 @04:19AM (#16143446)
I get the impression Go runs the microservice space. It's built for it and is incredibly fast despite the GC. I don't see Rust claiming that position anytime soon.
Re:Rust in 2018: easier to use by eecc on Sunday January 14, 2018 @04:44AM (#16143517)
Where I live and work, golang is only used at one major client (because they’re US based, the decision must have happened elsewhere.)

Everything else is Spring Boot (java), Akka (Scala) or Nodejs. Apparently nobody wants to embrace a language designed for offshoring, so no Meetups, noisy user groups and so on... even Clojure is more popular

Re:Rust in 2018: easier to use by K0nserv on Sunday January 14, 2018 @05:47AM (#16143696)
Golang is a language designed for offshoring? It was invented at one of the largest engineering orgs to be used in house
Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @07:04AM (#16143918)
In the words of Rob Pike:

"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 1"

"It must be familiar, roughly C-like. Programmers working at Google are early in their careers and are most familiar with procedural languages, particularly from the C family. The need to get programmers productive quickly in a new language means that the language cannot be too radical. – Rob Pike 2"

So a language that makes it quite easy for enterprises to deal with developers as cogs.

Source:

http://channel9.msdn.com/Events/Lang-NEXT/Lang-NEXT-2014/Fro...

https://talks.golang.org/2012/splash.article

Re:Rust in 2018: easier to use by foldr on Sunday January 14, 2018 @07:43AM (#16144031)
I don't see what that has to do with offshoring. Developers of the kind Rob Pike is referring to exist everywhere in the world.
Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @07:59AM (#16144074)
I do enterprise consulting, in projects which happen to always have some kind of offshoring involved.

Projects where the languages are easy to pick up and anyone can do it, are always the first on the pipeline to give away.

Re:Rust in 2018: easier to use by foldr on Sunday January 14, 2018 @08:12AM (#16144118)
Are you really saying that Rob Pike is part of some kind of conspiracy to offshore all the coding that's currently being done at Google SF? Golang has been around for a while now, and there's no sign of that happening.
Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @08:23AM (#16144144)
No, I am just stating that the goals of having the language designed for such target audience, can have that as side effect.

Just like it happened with Java.

Re:Rust in 2018: easier to use by foldr on Sunday January 14, 2018 @02:52PM (#16145970)
Your responses to K0nserv and singhrac suggested that you were defending the claim that golang was "designed for" outsourcing.

If you're making the weaker claim that Go's design "can" have the effect of triggering outsourcing, then that's speculative and consequently rather difficult to refute. But you haven't provided a single piece of evidence that this has actually occurred, so far as I can see.

Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @03:23PM (#16146164)
I was making the claim that can be a side effect of its design and the way the community is against common features in modern languages, deemed too complex.

Lets see how it looks a few years from now, given that it is becoming a mainstream language thanks to Docker and K8s adoption.

Re:Rust in 2018: easier to use by foldr on Sunday January 14, 2018 @04:12PM (#16146492)
Many of those features (e.g. generics) are in Java and/or C#, which are nonetheless widely outsourced.
Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @04:37PM (#16146633)
True, however Go is like a Java or C# 1.0, they did not start as they look today.

So Go is in the right track to follow their path.

Re:Rust in 2018: easier to use by dullgiulio on Sunday January 14, 2018 @09:01AM (#16144261)
It's pretty bad that people outside the SV can code /s
Re:Rust in 2018: easier to use by wwweston on Sunday January 14, 2018 @12:32PM (#16145182)
Exactly. :)
Re:Rust in 2018: easier to use by singhrac on Sunday January 14, 2018 @07:49AM (#16144049)
Software is more than just language features. Rob undoubtedly meant that he wanted it to be quick to be understood by a vast majority of Googlers, so that they can focus on writing good software.
Re:Rust in 2018: easier to use by pjmlp on Sunday January 14, 2018 @08:00AM (#16144079)
Yet Google is known for having one of the hardest hiring processes, where they even give the candidates CS subjects to study before the interview.
Re:Rust in 2018: easier to use by shaklee3 on Sunday January 14, 2018 @03:56PM (#16146374)
He really said they're not capable?
Re:Rust in 2018: easier to use by nicoburns on Sunday January 14, 2018 @05:19PM (#16146831)
Rust's USP over Go isn't more speed, it's better abstraction, and better correctness. Go is definitely a good tool for microservices, and it isnt going anywhere. But writing Rust is a joy, and I wouldnt be at all surprised if it also carves itself a niche in this area.