@peres The flutter dev experience might be great, but most series B-D startups I know in nyc use react native to share tooling, maybe codebase between web and native gain the velocity they need to stay competitive. RN is not perfect, but react is informing iOS development for a reason.
@chadm80 @lewandorkski@BobString It's gonna catch the type and reference errors if you use it right, so if you expect something to be defined always, and are tying to access it as a field of an object, typescript will see how the object could be possibly undefined and tell you.
@lewandorkski @chadm80 @BobString The benefit is testing on your frontend at compile time. TS can be really frustrating and can seem imposing in the way that the types use a lot of OOP principals -- and it definitely adds lines. I was a sceptic too, but now I see it, you cant not use it. It catches everything.
There's a world many developers sadly never see: "I can honestly say that there has been nothing in my career that could ever compare to spending the time in the world of Erlang and absorbing the experience of its veteran community by osmosis."Β https://t.co/dsYBYCKk5U
@mjackson I asked the core team about layout props and they said they weren't intended to work that way. I use them in glam bc they are useful to see in the context of the adjacent components. Layout is not style; we aren't writing css.
4 months on #vscode with #ReactNative and #elixir -- was impressed, but haven't found anything that compares to #jetbrains Refactor. Probably be heading back bc relative imports are π±
@sseraphini@andrewingram@flowtype I'm working with subscriptions in Absinthe in in elixir yes, and it is amazing, not as easy to set up graphene but in the long run better imo because if the dataloader batch support and functional language ease, lib author and community both π
@andrewingram The subscriptions support in elixir is excellent and timex is also good. I'm currently using with RNRelay with scheduling, timezones, and it's a game changer. Ping me in the elixir slack. cameron_m
@easyangel Great talk, but isn't he saying to do it the other way around? Unlike what sangria is doing where it derives the schema from the classes, you start with graphql schema and it derives the classes.