As I understand it, reposts are fine as long as a reasonable amount of time passes between submissions. I swear I've seen a few stories that get submitted almost every year, although I can't remember any off the top of my head.
That's "past" button lets you quickly search for previous discussions.
I think I remember a Bleacher Report engineer talking about this on an Elixir podcast. They use it to power their push notifications and pride themselves in being consistently the fastest among their competitors.
Postmates [0] for a variety of internal services. It's been rock solid and easy to ramp new team members on to. We do have a good number of in-house erlang folk, too.
The immutable nature helps with 1) reasoning locally (you can always understand exactly what happens in a function by reading the function itself) and 2) debugging. Additionally, dialyzer provides a very nice (optional) typing system for erlang / Elixir.
And with the new deprecation in 1.4 of bare words, a disambiguation goes away where when looking at a function you sometimes had to go "is this a variable or a function". Now functions with 0 args have parens, always.
I've found the locality of everything in the function that you mentioned helps IMMENSELY in refactoring. Just give a function a namespace and call it, and then figure out where it actually belongs later as you figure out your implementation.
We do at TalkJS (https://talkjs.com). It's a pluggable user-to-user messaging service, and the concurrency that Phoenix and notably Elixir offer have been really helpful in keeping our infrastructure simple.
Tinfoil Security! All of our release engineering is orchestrated through a small Phoenix app that calls out to docker images to perform various types of deployments (Heroku, EC2, ECS, building docker images, etc).
I'll probably do a write-up on it at some point, because it is now trivial for anyone on the team to deploy any of our services to any environment (or a new one!), and to integrate new services into the platform.
Yes! Phoenix creator here. We need to give the blog some love, but in 2015 we had a big year. We released the "Programming Phoenix" book for pragprog and our big "Phoenix Presence" feature, a CRDT backed eventually consistent process group:
What does presence use for its persistence layer? For its gossip protocol? Are you using plumtree, a fork, or something home rolled? Are you aware of Christopher's work with Lasp and the delta-CRDTs?
This sounds great and it's very idiomatic to OTP, it's like a web app VM.
28 comments
[ 3.5 ms ] story [ 65.3 ms ] threadThat's "past" button lets you quickly search for previous discussions.
[0] https://twitter.com/postmatesdev/status/803775289713049600
I've found the locality of everything in the function that you mentioned helps IMMENSELY in refactoring. Just give a function a namespace and call it, and then figure out where it actually belongs later as you figure out your implementation.
https://github.com/doomspork/elixir-companies/
I'll probably do a write-up on it at some point, because it is now trivial for anyone on the team to deploy any of our services to any environment (or a new one!), and to integrate new services into the platform.
https://dockyard.com/blog/2016/03/25/what-makes-phoenix-pres...
We also have been working on Phoenix 1.3 which I laid out in my ElixirConf keynote. Ask me anything!
This sounds great and it's very idiomatic to OTP, it's like a web app VM.