Come on, open your minds a little. Once every 5 years it doesn't hurt to learn some new, better ways of doing things. And if someone wants to write java code untill he dies, then there's a great method of doing that called "stick to java" ;)
That same kind of thinking already marginalized nodejs. The code written in it is horrible because almost everyone is trying to emulate c++ and java instead of taking one week to learn the language a bit and JS is so flexible you can actually do that to some extent. Not sure why some people think that every language on the planet needs to be a bad clone of c++ or java.... probably putting "java" in its name doesn't help. Thanks GOD it's golang, not go++, we'd be doomed. Seriously. For me - against generics because of amount of complexity and issues it'd introduce into the language. Would be cool to see a fork implementing it because maybe it can be done "nicely", however i doubt it... It brings to mind Rust's multithreading paradigms. That's actually great stuff... but totally unfit for integrating with golang (for this im preety sure). Hopefully, if generics will be implemented it won't be integrated too tightly so i won't have to get back to writing code which is more jav'ish that it needs to be. Because, that's a crazy idea... if i liked how java works more i'd just use java ;) And introducing operator overloading into this beautiful design will be like putting readability back into medieval ages... -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/d0ab80ae-ad07-43e3-9a87-32a61940c639%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
