5 ms·
The biggest risk Google faces is not developing some awesome new thing. There is very little risk that they will develop some awesome new thing, but not be abl
by staunch 17y ago
The biggest risk Google faces is not developing some awesome new thing. There is very little risk that they will develop some awesome new thing, but not be able to make it scale.
If discouraging developers from using Python means that one great project doesn't happen it's probably a net lose for them.
- lucifer 17y agoPrecisely what category of "awesome new thing[s]" needs to be developed in Python and can not be implemented in Java or C?
- staunch 17y agoI'm not saying there's anything technically wrong/bad about Java/C++. Awesome new things come from people's brains. Some people's brains are sensitive to things like motivation/happiness. Python makes some people's brains more motivated/happy than Java/C++ does. An new thing may never get off the ground, or be taken far enough to become awesome if the developer doesn't have the motivation to work on it.
- rbanffy 17y agoA tongue-in-cheek reply could be "something that has to be done in a short time?" A programmer using Python (and Ruby, Perl, Lisp, Smalltalk) is usually more productive than one with comparable brain-size using Java or C.
- lucifer 17y agoProductive in this context means 'coming up with an idea that Google can turn into a product'. /tongue-in-cheek
- rbanffy 17y agoA nice approach is to develop in your VHLL of choice, profile and rewrite the more important parts in a less expressive (but faster/leaner) language like Java or C (or Verilog)
- lucifer 17y agoExactly. (Obviously the preference would not be to prototype ideas in a statically typed language.) My expectation of the mythical Google engineer is that s/he can crank out the code whether its Python, Java, or C++. So, I remain unconvinced that Google the company is going to lose wonderful ideas because of their strong preferences regarding their production codebase.
- stcredzero 17y agoFunction Points/LOC is about the same for Smalltalk/Lisp/Ruby/Python. There are Smalltalk and Lisp implementations that run impressively fast. Also, memory use is more efficient. Library support is much better on Ruby and Python, however, due to the size and vibrancy of the user communities. If I were Google, I would develop a server-oriented language on top of the V8 virtual machine, using the "good parts" of Javascript as a compiler target. Add optional typing and type inference, but only as a parse/compile time facility to provide information to the programmer. Add a functional programming sub-grammar with the same facility. Then, add a fast Python implementation using the same engine, with strong support for calls from one language to the other. This way, Google would get the benefit of both the vibrant Python community and a fast, scalable VM.
- nostrademons 17y agoUnladen Swallow.
- stcredzero 17y agoBy using V8, they would also have the combination of the Javascript and Python communities.
- joe_the_user 17y agoBut would it mean that? Would using server-side javascript make the project less likely to happen? How many projects absolutely depend on the language they're implemented in - especially given that javascript gives you all the scripting features that c++/java lack.
- SwellJoe 17y agoWould using server-side javascript make the project less likely to happen? Yes. The library infrastructure of server-side JavaScript is pitiable compared to Python (or C++ or Java). This will change, I have no doubt, and I believe JavaScript will become the most popular language for practically everything short of systems programming in the not too distant future (7-10 years, perhaps), but it's definitely not as easy to build a server-side app in JavaScript today as it is in Python, Ruby, Perl, etc.
- litewulf 17y agoI'm using Rhino on the JVM. Imagine writing Java code, without having to type classnames all the time and you have a rough approximation of what its like. (And yes, you can import arbitrary Java bits into Rhino. It is "freaking sweet")
- SwellJoe 17y agoBut Rhino has the same performance issues as Python and Perl and Ruby, doesn't it? According to one benchmark ( http://ejohn.org/apps/speed/ http://ejohn.org/apps/speed/ ), Rhino is generally several orders of magnitude slower than Spidermonkey and Tamarin. Which probably means that it is also orders of magnitude slower than Python, Perl and Ruby. Since JavaScript was suggested as an alternative to Python to act as a reasonable substitute for C++ and Java for performance reasons, suggesting a JavaScript implementation that seems to be dramatically slower than even Python seems nonsensical. While JavaScript is a lovely language, and I'm all for it being used more on the server-side, Rhino only solves the lack of libraries problem when compared to Python...it does not solve the performance/memory problem of using Python at Google scale. Unless, of course, things have changed dramatically since any of the benchmarks I found were run.
- nostrademons 17y agoThe risk/reward tradeoffs are very different for Google than for a typical startup, though. In a startup, you have no brand name to risk. If you develop a product that everybody wants but it can't scale, people might grumble a bit, but they still want your product, and you've still got nothing to lose. But if Google develops a product that everybody wants but can't scale, it runs the risk of damaging the reputation of other Google products. And there's a lot of prior success to damage. Do it often enough and people start thinking, "Those Google engineers don't know how to do anything right. Why should I trust them with my data for GMail or Docs or Websearch?"