News for hackers. Stuff that matters.
Re:Nes emulator written in go by kibwen on Monday March 23, 2015 @08:10PM (#9254142)
I think this attitude is far too cynical. Library authors that care about their users don't break backcompat lightly, and they do backport bugfixes. The mantra "programmers are lazy" does not imply that programmers are inherently amateurs.
Re:Nes emulator written in go by MetaCosm on Monday March 23, 2015 @09:59PM (#9254472)
I think that isn't so much attitude as experience. That said, I will watch post May 15th and hope I am wrong, but I suspect despite the buzz some of the policies will be (broad adoption) language suicide.
Re:Nes emulator written in go by kibwen on Monday March 23, 2015 @11:29PM (#9254738)

  > I think that isn't so much attitude as experience
Experience with library ecosystems which lack proper versioning support, perhaps.

  > some of the policies will be (broad adoption) language 
  > suicide
What policies? How does this discussion at all concern any deficiencies that are unique to Rust?
Re:Nes emulator written in go by serge2k on Monday March 23, 2015 @10:48PM (#9254617)
So instead we end up with libraries on 1.0 for years because you can't break by upgrading.
Re:Nes emulator written in go by kibwen on Monday March 23, 2015 @11:27PM (#9254729)
I cannot express how amused I am at the silliness of this whole conversation, which is predicated on the absurd premise that users won't want to upgrade their versions of the compiler. What part of the phrase "backwards compatible" is lost on this crowd?