This is because join negatively impact the scalability of a DB: - When huge amount of traffic hits your DB, out of the most commonly run-out resources - CPU, Memory, and IO - CPU is usually the one that runs out first. And Join uses quite a bit of CPU. - When you have a lot of data and have to partition it, you will feel so lucky if you don't have to deal with distributed joins.

I have used many languages professionally and in my personal projects. Java is the language that makes me most productive. Why? It has the best tooling support. There are a few things that is extremely important for my productivity: - Precise autocomplete - Jump from a name to its definition - Call hierarchy - Code template - Auto formatting - Great unit test support - Stable and high quality debugger - Hot swap - Drop to frame during debugging - Remote debugging - Profiling and heap analysis

Recently, I am working on both a very large C++ code base and similarly large Java code base. In C++, I find myself routinely use logging and printf for debugging, because switching to debug build and use a debugger is such a pain. In Java, debugging is much easier. The feeling is like night and day.

It does not have it now, because they want to focus on the basics. Once that is done, adding a camera is not a big deal.

But I feel like that would make the media -- followed by average people -- go crazy. Consider the current NSA news combined with "Google puts hundreds of cameras in the sky".

> But I feel like that would make the media -- followed by average people -- go crazy

Yes, that will be a two uncomfortable days of online nerd rage.

A handful of police departments in the US already have constantly floating omni-directional camera drone balloons. The technology is only getting cheaper.

Huh ... don't look now, but Google is already putting hundreds of cameras in the sky, daily. Various aircraft, even some satellites, are devoted to Google imagery. Having a new fleet of balloon-based "craft" providing imagery could easily fit into Google's M.O.

And what happens when "Google puts thousands of cameras on our faces" ?

Well like if you didn't have a camera in your pocket for years. Or like cameras hidden in pens weren't available cheaply for years. Seriously, the time for people to be scared of others recording things is has already passed (mostly unnoticed).

It's different, since people will actually have to buy and use those cameras, the pushback will probably focus less on Google and more on the wearers.

You can use another "attacker" balloon to do it.

There are probably many ways to shoot down the balloon, but it's probably out of the technological reach of a farmer. I don't think there's anything off the shelf that could shoot something down from 80,000ft.

Just cover the continent will require a lot of balloons. The world has 148,429,000 sq km. If you cover 1600 sq km per balloon, that is 92768 balloons. Just cover Africa will require around 20k balloons. It will only work out, if Google can increase the coverage area per balloon.

20K ballons doesn't seem like that many unless each one costs a ton of money. From an industrial production point of view it barely seems like a drop in the bucket given how many cars/phones/planes we produce.

Each balloon would cover a circle, so it'd be more like 1,250 sq km. I think it would be optimistic to expect each balloon to cover exactly that area. They'd need to overlap just to eliminate gaps, and I'm sure there's a random element to their motion, so that would require them to overlap more.

Scalability is an architecture issue, not a programming language issue. You can certainly build linearly scalable system in Ruby. It just costs more to scale a Ruby app vs. an equivalent Java app. In the end, the tradeoff is between engineering cost and operating cost. When you spend 100k to hire an engineer and your traffic can be handled by a few boxes. Engineering productivity is your primary focus. As your traffic grows, you need more and more servers, server efficiency becomes more and more important. At some point, the savings in server cost justifies the increased cost in engineering effort and you make a switch from Ruby to Java.

There are lots of things in the toy, art, and spare part category that can use the 3D printing technology. Just like many other technologies, 3D printing will be adopted by designers, hobbists first. If there is enough demand, it will show up in shared workshop such as Kinko. It may or may not make into every home. Who knows. It really depends on if there is any killer app that drives the demand.

There are security issues with this approach. However, I wouldn't mind if a site offers both traditional login and email based login. Then, I, as a user can choose which is the most appropriate.

There are a lot of ebay market research tools out there. You will need to stand out either by pricing or by feature. Good luck.

The service can stay free by monetizing the traffic I am sending to eBay using their affiliate program. Currently I create landing pages for all searched terms and try my limited seo skills to get these into the google index.

Is there any feature at the top of your head that you would like to see in this tool?

Thank you for your comment!

So, growth hacker is a marketer. Fine. But not all marketers are growth hackers. My understanding is that, growth hacking is a specialty in marketing which focus on consumer web marketing. It is also a very technical and hands on position. As a growth hacker, you not only need to have a marketing plan, but also need to implement or help implement the marketing plan. There is nothing wrong for giving a name to a sub-category of marketing profession.