News for hackers. Stuff that matters.
Re:The State of Go by mkpankov on Wednesday May 27, 2015 @07:34AM (#9610615)
> similar timeframes

I hope you understand first stable release of Rust happened less than 2 weeks ago (15 May 2015), vs. Go's Go 1 in March 2012.

3 years is pretty big difference.

Re:The State of Go by danieldk on Wednesday May 27, 2015 @07:56AM (#9610694)
I hope you understand first stable release of Rust happened less

Of course, but Rust has been in tech news for a while already. E.g., the Rust 0.1 post garnered 82 comments[1], over 3 years ago. Rust seems to be first mentioned in a submission title 5 years ago.

Of course, their inception was not exactly at the same time. But if we look back in 20 years, it's the same timeframe. Just like e.g. Python and Ruby, despite being 4 years apart. Or C and Pascal.

[1] https://news.ycombinator.com/item?id=3501980

Re:The State of Go by enneff on Thursday May 28, 2015 @01:37PM (#9619733)
I find your perspective a little bizarre. For instance, if we look on a galactic time scale, Lisp and Go were created at pretty much the same instant!

It's not fair to Rust to compare it to Go, as if they are at the same stage of their adoption and development. Several years is makes a big difference in the tech world.

Re:The State of Go by dbaupp on Thursday May 28, 2015 @09:07PM (#9622149)
Err, wat.

It seems ridiculously reasonable to compare programming languages on the time-scale of modern computing (~70 years). Dismissing the comparison like that is pretty crazy.

However, don't get me wrong: I totally agree that the years between the stable releases of the projects makes a big difference, especially now, while it is such a large percentage of the total lifetime of them.

Re:The State of Go by jcranmer on Wednesday May 27, 2015 @10:46AM (#9611707)
Go was first publicly announced in November 2009, Rust in July 2010.
Re:The State of Go by kibwen on Wednesday May 27, 2015 @05:24PM (#9614470)
At the time of its announcement, Go was tremendously further along in its development than Rust was at its own public announcement. Knowing modern Go, you can go back and understand Go code from 2009. Knowing modern Rust, trying to read code from 2010 is essentially impossible.
Re:The State of Go by justthistime_ on Thursday May 28, 2015 @11:00AM (#9618583)
I wouldn't say "further along". Deciding to not tackle any medium-to-hard problems just allowed them to be finished far earlier with their language.