Joe Grund

Software Engineer @intel

[Rust Language @rustlang]

ITS HERE!!!!

Rust 1.31 and Rust 2018 is finally out! https://t.co/wbvYXA5Rar

Thank you so much to everyone who has contributed over these past three years. ❤️❤️❤️

[Joe Grund @JoeGrund]

Creating a node stream computation expression + some helper fns #fable #fsharp

[Joe Grund @JoeGrund]

Created a template for using @jest with @FableCompiler: https://t.co/vYcEvK0Dyt

[Joe Grund @JoeGrund]

@rauschma F#

[Brandon Keepers @bkeepers]

Check out my obsession for the past few months: https://t.co/1ISSq6Fcg5

[Joe Grund @JoeGrund]

Added Some @ExpectoIO like testing into https://t.co/AF3rBTbDB5. Uses mocks that stand for typed fns as well.

@FableCompiler

[Joe Grund @JoeGrund]

Using @FableCompiler and @jest on a Node.js service

[Joe Grund @JoeGrund]

@FableCompiler @TomasJansson Full #fsharp project will work for Fable + Node interop.

WIP (reference) example here: https://t.co/gzDK1CgFmU

[DigitalOcean @digitalocean]

We're committed to ensuring choice, competition & free speech by supporting #NetNeutrality on 7/12. Join us and act: https://t.co/6gMPE5OK4t

[Chris Holt @lefthandedgoat]

Learning angular 4 and it just seems like magic, magic strings, and java/c# ecosystem 7 years ago (DI, services, etc). Not my cup of tea.

[Joe Grund @JoeGrund]

@williamberryiii @kevinswiber @gblock @kot_2010 @isaac_abraham @dotnetfringe @FableCompiler can exist in this space as an option. F# -> JS

[Scott Hunter @coolcsh]

If you are using .NET you should think about F#: https://t.co/Yds4tLNNqA

[λ Calrissian aka Matt Podwysocki @mattpodwysocki]

After the conversations at TC39, makes me realize I want to think more about function pipelining, binding and partial application

[λ Calrissian aka Matt Podwysocki @mattpodwysocki]

Now I have flatMap and flatten ES Proposals from @bterlson working on Iterable and AsyncIterable for IxJS https://t.co/3E5lmRBvKM

[Kevin Lacker @lacker]

Stanford CS is switching to JavaScript. https://t.co/OuwAJdno7I

[Joe Grund @JoeGrund]

@littledan @Flow Yes, both TS and flow are great, and can imagine difficulty of retroactively adding advanced static type system.

[Joe Grund @JoeGrund]

@littledan Probably not auto-curry, but I could see something similar to Function.prototype.bind (with some sugar syntax as well).

[Joe Grund @JoeGrund]

@littledan More usage of points-free style; Built-in would also cause type-system support as a side-effect.

[Joe Grund @JoeGrund]

@littledan @Flow Type inference + disjoint unions + Generics + type aliases would be nice in a built-in JS type system.

[Joe Grund @JoeGrund]

@littledan I use @flow for existing projects.

In my experience, built-in type systems are more complete with less bugs / corner cases.