They are the ones who made Python popular though, Python got popular because people learned that it was used by Google. Now Google is shining their light to Go.
I tried Go, but I didn't like it that much. It feels like the only new thing it brings to the table it's the go routines. Also it feels like it's very simple (perhaps too simple) and very opinionated (e.g. indenting), or how code is stored. It seems like it was designed just for Google's needs.
It was designed to replace C++ and finally replace Python.
To be simple, opinionated, with top batteries included, fast and easy to deploy. All of this together are quite new on the table ! It seems it was designed just for me :-) !
If you want to rewrite a large monolithic code base from one language to another there's problem that you would have to finish the entire work before you can use the code in new language.
So what can you do? You write code to do the automatic conversion for you. The problem is that the generated code is not maintainable, but at least now you can make calls to it. It also allows you to rewrite module by module.
Google's Unladen Swallow project did not succeed, they also don't seem seem to move away from Python 2.7, for god's sake even this project is Python 2.7 only, and ticket about Python 3 support was closed with change in documentation that specifically says Grumpy targets Python 2.7 only. It can't be any more clearer that Google is moving away from Python to Go.
This is crazy awesome. Currently only works for Python 2.7 though.
A lot of good discussions on hacker news: https://news.ycombinator.com/item?id=13319904
[deleted] 69 points · Jan 2017
[deleted]
Vorticity 20 points · Jan 2017
Meaning that the Python community is about to get a bit smaller...
sedaak 17 points · Jan 2017
Ehhh just a bit. Python has stellar growth.
[deleted] 4 points · Jan 2017
They are the ones who made Python popular though, Python got popular because people learned that it was used by Google. Now Google is shining their light to Go.
I tried Go, but I didn't like it that much. It feels like the only new thing it brings to the table it's the go routines. Also it feels like it's very simple (perhaps too simple) and very opinionated (e.g. indenting), or how code is stored. It seems like it was designed just for Google's needs.
kaeshiwaza 4 points · Jan 2017
It was designed to replace C++ and finally replace Python.
To be simple, opinionated, with top batteries included, fast and easy to deploy. All of this together are quite new on the table ! It seems it was designed just for me :-) !
jrandomcoder 4 points · Jan 2017
Don't worry, they don't actually use this in production.
spacebandido 41 points · Jan 2017
That's what they all said about Node
ArmoredPancake 4 points · Jan 2017
...yet.
koffiezet 1 points · Jan 2017
Yet. They're looking into that direction for a reason.
[deleted] 2 points · Jan 2017
How big does it have to be?
recycled_ideas 8 points · Jan 2017
No, because this won't do that for them. The code base is still going to be python 2.7.
What it'll do is allow them to get past the limitations of Python 2.7 without having to rewrite hundreds of thousands of lines of code.
[deleted] 8 points · Jan 2017
If you want to rewrite a large monolithic code base from one language to another there's problem that you would have to finish the entire work before you can use the code in new language.
So what can you do? You write code to do the automatic conversion for you. The problem is that the generated code is not maintainable, but at least now you can make calls to it. It also allows you to rewrite module by module.
Google's Unladen Swallow project did not succeed, they also don't seem seem to move away from Python 2.7, for god's sake even this project is Python 2.7 only, and ticket about Python 3 support was closed with change in documentation that specifically says Grumpy targets Python 2.7 only. It can't be any more clearer that Google is moving away from Python to Go.
recycled_ideas 1 points · Jan 2017
That might be true, but it's also entirely plausible they'll stick with the python front end for the foreseeable future.
They closed the python 3 ticket because that's of no use to them. Their code base is 2.7 and they could add features to that if they need them anyway.