2,885 karma · joined March 14, 2012
Co-founder, Kami - kamiapp.com
It's interesting how many different approaches there are when stepping back and using some of the OS - for example where does MySQL/InnoDB fit in this?
It seems they are intending you to use their buffer pool rather than the OS's disk cache (as they advise to make the buffer pool take large percentage of RAM), as opposed to Postgres where they recommend having shared_buffers as ~20% of RAM and leaving the rest for the OS to use. Is InnoDB doing something different here or is it just because they have a better cache implementation?
What lead to that design decision and what are the tradeoffs from it? Intuitively it seems like it'd be better to bypass the OS, but on the other hand Postgres does work incredibly well.
You can also do some pretty nice data syncing/access between the two using Postgres' Foreign Data Wrappers to access MySQL data within Postgres - unfortunately it doesn't look like MySQL has a equivalent for accessing Postgres data from within MySQL.
It's also incredibly easy to fall off the blessed path where you can interact solely with voice - when setting a reminder, for example, if it doesn't hear 'Yes' when it's expecting to it'll just sit there and you need to touch the screen to continue - defeating the whole point of voice interaction.
Google's voice search has incredible voice recognition and text to speech and can tap into an amazing amount of information through the knowledge graph, but they don't seem to be capable of fixing the basic bugs and UX issues preventing all that technology from actually being usable.
GKE has good commandline tools but the web interface is even more limited than ECS's is - I assume at some point they'll integrate the Kubernetes webui into the GCP console.
GKE is still pretty immature though, more so than I realized when I started working with it. The deployments API (which is a huge improvement) has only just landed, and the integration with load balancing and SSL etc is still very green. ECS is also pretty immature though.
I've been considering using your service for a while and it would be useful for us, but I couldn't justify paying what it'd cost us to use it.
I wish they had shown it climbing those stairs though! :)
As for data stored on user's devices, Google also ships their phones with full disk encryption which Google cannot bypass - the implementation isn't as good as Apple's, but the concept is the same. Facebook doesn't sell any end-user devices so I'm not sure why they are even in your comparison.
One thing to check though - do you have _any_ accessibility services enabled (Lastpass is a common one). They absolutely murder performance and since turning Lastpass off my 6P is far from perfect but much better than it was.
With the way MS is going maybe they'll introduce official support!
There's such an extreme lack of decent laptops around that working around the limitations of OSX seems to be the only option for now.
Maybe the next version of the Pixel will be more suitable as a general purpose development machine or someone else will make a decent linux laptop (if Google can do it, why can't Dell?)
I'd rather deal with these issues and run a ubuntu VM for some things than deal with the cornucopia of crap that is the PC laptop market but hopefully some day that will change.
Their sports in-ears are great also - I've never found any in-ear headphone that beats the MIE2 in comfort and not falling out, and the sound isn't bad either.
Interestingly, Dragon 2 does have enough fuel to land on Mars, with clever aerobraking. NASA has done some feasibility studies on using a Dragon to land on Mars with a sample return vehicle inside it.