Paul Schoenfelder

Hey @ThisWeekInRust Community, We are hiring @rustlang engineers at Ockam. More here: ockam.io/team

I haven’t tweeted in months, but these chips have required me to ask: America, why the fuck don’t we have these on our shelves? Montréal gets it, what’s our excuse?

@yonkeltron By the way I linked you the wrong thing haha, the paper is here: people.ucsc.edu/~palvaro/molly…

@yonkeltron Definitely interested!

@yonkeltron When I last dove into the topic, I looked at the references in the LDFI paper by Peter Alvaro, et al., pdfs.semanticscholar.org/e2be/6d31c44e1…

@shadowhand Dude, Ivi and I love this show, so damn good - I'm in withdrawal until the last season now :(

Dark (on Netflix) is quite possibly the best time travel show ever made. It goes deep into the recursion and I freaking love it.

#!/usr/bin/env bash killall ZoomOpener osascript -e 'tell application "System Events" to delete login item "ZoomOpener"' rm -rf ~/.zoomus/* chmod 000 ~/.zoomus

@MatthewOden You should be able to combine this with qemu to run the actual container on your desktop. That would be my go-to solution. I googled it quick and came up with this post which seems to use that as a base: ownyourbits.com/2018/06/27/run…

Still building - but so far, it looks like all I'll have to do is update @gotbones's alpine dockerfiles to point to arm32v6/alpine instead. ...and everything _might_ just fall into place? *fingers crossed*

Hrm. Looks like there's not a ton of support out there for versions of ARM-alpine docker images on elixir. Which makes sense - anything running on arm is probably using nerves. Guess I'll throw my own together?

@TechnoEmpress Hi! You can use libgraph to represent trees already of course - enforcing the "tree-ness" of a graph is can be done by just checking if `is_tree?` is true after manipulating the graph, which is a cheap check. A tree lib could build on libgraph as a foundation as well

@dnlserrano Hey Daniel! Been AFK from Twitter for awhile. I've been working on something tangential to Aria, and will have something soonish. I will definitely share news here as soon as it is available though :)

hey @gotbones any news on a potential super alpha release of Aria? looking forward to it. cheers.

@philipbrown Hey Philip! I am primarily counting on the community for those things, but I do plan to rebuild Swarm using it, so that would cover at least the global process registry :)

@gotbones Hey, I recently watched your talk on Cadre, great work! Will Cadre have implementations of global process registry, distributed cache, global locks etc, or do you intend for the community to use Cadre to build those things?

@FrancescoC @joeerl This is terrible news :(, Joe was a pleasure to talk to, he always had something interesting to share. He was, and always will be, an inspiration to me and many others

It is with great sadness that I share news of Joe Armstrong's passing away earlier today. Whilst he may no longer be with us, his work has laid the foundation which will be used by generations to come. RIP @joeerl, thank you for inspiring us all.

@yburyug @elixirlang @doomspork @binarytemple @devoncestes @DockYard In my opinion, the big reason why core shouldn't just take up an existing project, beyond maintenance issues, is that core should be a place for building blocks, so that the ecosystem can try new things and find better solutions without requiring the core team to be arbiter

@gotbones @elixirlang @doomspork @binarytemple @devoncestes @DockYard That's good to hear. I just struggled with 'why not adopt the existing code' w.r.t the formatter, property testing lib options, this. But I've also never coordinated a project so large, so theres a million things that are involved I dont know about that I'm sure impact that call.

@yburyug @elixirlang @doomspork @binarytemple @devoncestes @DockYard To be clear, what is going in core is not reinventing the wheel, it is based on experiments, techniques, and lessons learned in Distillery, with an eye toward the future. IMO it is a natural evolution of the tooling that has been going on since I first released ExRM years ago

@elixirlang @doomspork @binarytemple @devoncestes @gotbones @DockYard I'm a very happy user and will continue to be, I just wish there was tighter integration with core and the dev community using the tools to adopt some of these things rather than build a whole new version.

@elixirlang @doomspork @binarytemple @devoncestes @DockYard The core team and I have been talking about the shape of things to come for a long time now :) - Distillery will still have a place in providing richer features that don't belong in core, but we're finally getting to a point where the building blocks are part of Elixir itself!

@doomspork @binarytemple @devoncestes @gotbones @DockYard Distillery 2.0 was essential in testing some ideas that will ultimately be part of core, such as config providers, and we have recently validated some of our decisions with @gotbones too (mostly implementation details where the approaches differ).

Distribution is one of Elixir's greatest strengths, but taking advantage of it properly is a non-trivial problem. Cadre can help! Get up to speed on architecting your distributed system with @gotbones at @LonestarElixir! #paul-schoenfelder" target="_blank" rel="nofollow noopener">LonestarElixir.com/2019/speakers/…

My Phoenix LiveView writeup is out! It details our latest progress and shows off a bunch of demo applications. We show autocomplete in 35 LOC, a complete snake game in 330 LOC, and how our optimizations match hand-written JSON in payload size. dockyard.com/blog/2018/12/1…

Kawase Hasui

Speakers for @LonestarElixir 2019 are posted! Check them out at LonestarElixir.com! @yoooodaaaa @bcardarella @dandresselhaus @KronicDeth @ericoestrich @davidpick @sprsmpl @gotbones @redrapids @gregvaughn @zacky1972