Hey all, as a potential competitor of Looker, I'm not sure how I should feel about this news. :) Here are some of the facts: 1. When Google acquired Alooma, they slowed down the development and dropped the support for other destinations such as Redshift and Hive. Even though Alooma is a data pipeline tool which makes it similar to Looker's case, the deal was $150M (compared to $2.6B) so I'm not sure the comparison ma…
Don't worry about it. It's undoubtedly an aquihire. If there is one thing that Google demonstrates consistently is a complete disregard for relationships with external parties. This product will die once Google stops communicating with external companies. This is your opportunity to reassure your partners you're not going away and to reach out to Looker's companies to see if you can help stay in-front of this. Just don't be a dick about it: "Hey, just saying that Google is known for letting products die. If you're concerned about this, we'd love to know how to help you with those concerns."
I'm a huge fan of Looker, but I'm not sure how I feel about this news. The best parts of Looker: - It connects directly to your existing data warehouse. Most BI tools suck in your data into their datastore; Looker queries your database directly. If you wanted Looker to cache results for performance reasons, you could set up a dedicated schema in Redshift for example and only give write privileges to that one schema.…
And Waze too. I love that app's singular focus in improving the driving experience and nothing else as a Maps product.
> singular focus in improving the driving experience Except for the super distracting Ads that cover half the screen while you're using it every time your car comes to a stop, the sponsored landmark-Ads that put a huge marker over every Dunkin Donuts location while driving, etc.
If you're not in your car to drive to the next Dunkin Donuts, what are you even doing?
That... would be the marketing team for you. We do spend quite a bit of our time adding stuff that I don't think I've seen anywhere else but is extremely useful for some of our biggest clients.
> I don't think I've seen anywhere else Market that stuff! Blog posts, list of features, service comparison - anything. For example, I know that Tableau offers in-memory storage that can help improve performance by bring data in locally and not hitting the original source. Kato mentions something about "10x performance improvement", but there's zero explanation how this is accomplished.
We have 3 different levels of storages to avoid hitting remote. Redis cache for query, storing the results on our server and letting users edit the data as well and finally front end cache with service workers.
I think I'll start writing out the feature comparisons.
I’m surprised (and glad) they didn’t integrate it into Google Maps and shut down Waze.
Even I am surprised too but I guess since Google started working on self-driving cars and then after seeing the advent of ride-hailing apps, they may have thought to keep Waze so one day Google can convert it into a ride-hailing + navigation app. Maybe that's the plan who knows!
i still don't get that argument. target audience of Waze is people who have cars and drive it around. people don't open up waze to get a taxi, they open it up to start driving.
I'm a huge fan of Looker, but I'm not sure how I feel about this news. The best parts of Looker: - It connects directly to your existing data warehouse. Most BI tools suck in your data into their datastore; Looker queries your database directly. If you wanted Looker to cache results for performance reasons, you could set up a dedicated schema in Redshift for example and only give write privileges to that one schema.…
What's your opinion of Periscope?
Periscope features for non-SQL users not strong enough. Looker did a great job of enabling the non-SQL analyst types more familiar with a Tableau like UI.