News for hackers. Stuff that matters.
Re:Why Go Is Not Good (2014) by joined on Wednesday December 09, 2015 @10:51AM (#10704295)
If anyone is looking for the article publishing date (no indication on the site), archive.org made the first snapshot on June 2014.
Re:Why Go Is Not Good (2014) by tvon on Wednesday December 09, 2015 @10:56AM (#10704346)
Thanks, I found "<!-- 2014-06 -->" in the source as well, but it drives me nuts when web pages have no publishing or last-modified date.
Re:Why Go Is Not Good (2014) by SuperKlaus on Wednesday December 09, 2015 @11:23AM (#10704578)
Re:Why Go Is Not Good (2014) by carols10cents on Wednesday December 09, 2015 @11:12AM (#10704490)
Yeah, I suspected it was old when the Rust version used was 0.11...
Re:Why Go Is Not Good (2014) by hatsunearu on Wednesday December 09, 2015 @12:54PM (#10705341)
The most often encountered thing that I find Rust frustrating is how much the language changed over time--lots of random answers and posts that are outdated floating around somewhere that I have to throw out because the language changed.
Re:Why Go Is Not Good (2014) by krisdol on Wednesday December 09, 2015 @03:39PM (#10706566)
It's just incredibly young at this point, and still in a phase where making breaking changes for the sake of the language vision is acceptable. Swift has been in the same boat. I'm sure that will change in the near future. Luckily both languages have great compilers that catch backwards-incompatible issues.
Re:Why Go Is Not Good (2014) by insulanian on Wednesday December 09, 2015 @11:41AM (#10704737)
I love your user id :D