Learning back end Elixir programming without back end experience

Dr. Stephen Strange: They really should put the warnings before the spell.

Ryan Dahl, Creator of Node.js:

And honestly, that’s the reason why I left Node. It was the realization that: oh, actually, this is not the best server-side system ever.

Node.js as a Backend: Best Use Cases, Tools & Limitations

Advice for choosing between elixir and nodejs

If you just want to get your feet wet start with Getting Started and continue with Mix and OTP to see if you’ll have any problems.

  • There is nothing special about languages that are being used on the “back end”. It just happens that originally JavaScript was designed with the runtime constraints of the browser in mind - so at the time there was no need for language features that are considered essential for large scale application development - and the Node.js community has had to backfill the holes ever since (e.g. adopt a module system before the official language specification did).
  • Being comfortable using the command line would be helpful. By extension in my personal opinion I think it would be helpful to work on a *nix type of platform. Some people seem to be successful with Windows especially when using the Windows Bash Shell - but I can’t help shaking the impression that Windows increases the amount of friction you have to deal with.
  • Seems people like to use vscode-elixir-ls but your favourite text editor will do.
1 Like