ewrcoffee

> Looker's sale team is so aggressive and their support team is great. In fact, that's why Looker became so big in the last few years. Google is not famous in terms of support.

That's probably the major reason of the acquisition.

This is mostly lost in translation. The original quote has nothing to do with external shame.

I think the point of machine learning is that such detailed models do not need to be explicitly modeled, but as some implicit layers to learn.

I see. Now I see a strong point of favoring implicitly passing the context - attaching the context to a go routine local variable (no such thing yet), so the aspect of context passing can be decoupled. Of course for some logic we probably still want to do some explicit context stitching, but that won't pollute most of interfaces. Would that address your concern?

I would expect one can reason about the program of the proof in less than 100 hours, which is essentially the proof.

Not sure why don't you like go's context model. It works pretty well in our production system. I can see people would like to pass the context implicitly. But I don't have a strong opinion. Explicitness is not that bad.

There's a movie on business like this: The Bride of Rip Van Winkle by Shunji Iwai. But not sure if it is inspired by the exact same company.

We tried Apollo in its very early stage, the code complexity and the hard to debug object cache management drove us away. We are quite happy with some simple combination of raw fetch and mobx.

Will definitely take another look at the v2!

Chinese here, I agree that it is very easy to have puns in Chinese. But I don't think Chinese find puns very humorous in general (probably it is too easy?), is it more often used to make blessing or satirical phrases.

but it could https://youtu.be/gy5g33S0Gzo

If you are already a haskell shop and need some way to write JSON schema, this probably doesn't seem too much over engineer. On the other hand, if the purpose is just to limit the expressiveness of JSON schema, I think a runtime checking is more than enough (that's how we solved our problem). Since any data schema we write inevitably has a "validation" phase during our build process. And doing runtime checking during the build phrase allows more flexible and extensible validation; with less abstraction to be understood by the strawman.

Exactly, that paragraph is a very strong argument in favor of GraphQL.

I can see the major point of making a microkernel is to allow kernel or other service (like driver) upgrade to be de-coupled; it would also allow much easier integration of non-open source driver and service, which could be a pain with Linux as it doesn't provide a clean way to do without rebasing (which could explain why Android upgrade is much lag behind for existing phone). But don't get me wrong, I totally support Linux philosophy.

Very interesting! Where can I more details in building UI with Reason?

To my understanding, react allows writing more type safe code. So no.

Without session transaction, how does the application performs transactional read modify write?