#digitalsalon

July 23, 2018
[22:59:06] skwingar_: leaves
[22:59:58] skwingar: joins
[23:24:54] skwingar_: joins
[23:25:41] skwingar: leaves
[00:00:01] skwingar_: leaves
[01:09:03] skwingar: joins
[01:44:23] skwingar_: joins
[01:46:52] skwingar: leaves
[01:53:07] skwingar_: leaves
[02:12:27] skwingar: joins
[08:17:22] skwingar: leaves
[15:00:52] alex[m]7: dang, i wish i caught the flutter present, how was it?
[15:01:22] alex[m]7: alex commented on thisgeek’s file https://digitalsalon.slack.com/files/U1LH6M160/FBSPCKWQL/img_20180718_134312.jpg: dang, i wish i caught the flutter present, how was it?
[15:03:33] thisgeek[m]: Pretty good. If you’re willing to write in Dart you can get some nice benefits for development and support for target environments.
[15:03:33] thisgeek[m]: Also learned that Fuchsia’s a thing.
[15:03:40] thisgeek[m]: https://arstechnica.com/gadgets/2017/05/googles-fuchsia-smartphone-os-dumps-linux-has-a-wild-new-ui/
[15:15:29] alex[m]7: cool
[15:15:37] alex[m]7: read the graphql article
[15:16:06] alex[m]7: thisgeek he made one comment I am not sure if he got right
[15:17:13] alex[m]7: where each points to a different app
[15:17:43] alex[m]7: i have been diving in to aws appsync
[15:18:00] alex[m]7: which uses graphql and apollo
[15:18:32] alex[m]7: and you can have everything come from different "resolvers"
[15:18:42] alex[m]7: even in the same call
[15:18:57] alex[m]7: not sure which tech owns the term "resolver"
[15:19:17] alex[m]7: but it is an interesting approach
[15:19:24] thisgeek[m]: I don’t remember that part, but I bet you’re right that it’s not a given you can’t do that.
[15:19:55] thisgeek[m]: Especially since you could have a layer in front of a service that handles the routing.
[15:20:28] alex[m]7: in some ways it's the same and in some ways it's different
[15:20:34] alex[m]7: different trade offs
[15:22:19] alex[m]7: appsync apps can use dynamodb, elasticsearch, or lambdas to resolves any part of a graphql query
[15:22:46] alex[m]7: any way, gotta get back to it, ttyl!...