I’ve set up Atom and Spacemacs (trusty fallback, as always, if Atom doesn’t work out)
I’m writing some simple data structures (ex. linked list) to get an initial feel for Elixir syntax, testing, dyalizer etc.
Will do Elixir dips soon and build some simple API server with Phoenix, just for more experience.
Intend to eventually use Elm and Elixir together on something.
I’m working on a bpms, for the time being as a learning project. Some model-driven ideas (name it the “zero”-code movement) caught me a couple of years ago. In principle you (and / or your customer!) should become able to model as much of your application as returns at least investment. The models should be directly executable and persisted in f.e. json. So no code-generation (+ software deliveries) but load the model and interpret run-time. This gives you more flexibility than codegeneration. The modelers should be fit for different problems. So you have a form builder (wysiwyg) that maintains f.e. a json. You have a bpmn editor (boxes and arrows). If you stick to the standards this one persists in an xml, bpmn2.0 compliant. One or more editors for your rules (form validationrules - used serverside also - and decisionrules: the arrows between the boxes, xor boxes etc). And doubtles more to parametrize your app. The bpms needs all. You need the form builder + rules editor for usertasks. Etc. For the db we have the erd (boxes & relations).
Elixir / phoenix is ideal for this. Channels come in handy, the actor model etc.
I’m enjoying this playground!
Ooo, a couple questions:
Building a new iOS/Android social network backend using Phoenix.
It’s absolutely great I must say, but you know this))
