I think google is heading the way of SUN, they now make many nice products that add no obvious revenue streams!
What google really needs is to make products that make money and the re-organization need to be based around that, employee compensations and incentive should be based around how much money they make for google.
for example, unless its clear how much money the go lang will save for google, they should kill the project and just use C++ or Haskell or whatever!
I tend to believe that most people who are coders, developer and into FOSS, tend to buy very little software and only pay for the absolute necessary
This is not a bad thing, software is our thing, so we just won't pay for anything
But I've seen people pay for less trivial stuff, like items on a facebook game.
So probably we won't, but that never will mean, that millions of web browsers won't! I can almost bet that if you sell an extension that claims to make chrome more secure, enough people will buy it to make you happy!
Um, you're joking, right? Perlbrew itself is fine (I use and like it - I actually wrote a small Bash completion script for it[2]), but it implements only a fraction of the functionality of rvm[1]. (Rvm also precedes Perlbrew by some time, I think).
One question, I noticed that the pdf from from the onyxneon site is 185 pages long, when a previous draft which i downloaded from chromatic's site was 273 pages long.
"Going from Javascript to Coffeescript today feels a lot like going from Java to Ruby felt to me in early 2003."
One should really wonder, why did he skip on Python, Perl and Ruby for all those years? Knowing that RoR appeared in 2004, and thinking that Coffeescript seems closer to Python
hi nice site, please consider having a table view that have the following columns: Book Title, Author, Publication Date (make the table sortable by any row)
And if I click the table row, it can expand to the long descriptions and cover shot you added to each book. What first at attracts me to a book is the title, author and how recent it is!
What google really needs is to make products that make money and the re-organization need to be based around that, employee compensations and incentive should be based around how much money they make for google.
for example, unless its clear how much money the go lang will save for google, they should kill the project and just use C++ or Haskell or whatever!