130 karma · joined May 6, 2017
Granted, the codebase uses pattern matching, type specs and Dialyzer extensively, which all definitely contribute towards making the navigation easier. Without those tools in use, I can definitely imagine navigation being more difficult.
There's more interesting information on synchronization and bridges on Veritasium's video, The Secret of Synchronization [2].
[1] https://en.wikipedia.org/wiki/Broughton_Suspension_Bridge [2] https://www.youtube.com/watch?v=t-_VPRCtiUg
Are there any specific collaborative features the team is planning for future releases?
One interesting piece of data comes from Elixirforum.com, arguably the central hub for the Elixir community. In their recent MOTY update [1], they announced that "..to give you an idea of how far we’ve come and how fast Elixir has been growing, in the forum’s first year we served just over 1M pages for the entire year, now, we’re serving a million a month".
The official Elixir language site has also been steadily accumulating more and more case studies [2], which one might consider as sign of health in terms of Elixir being used in the industry. Obviously it's only the success stories being told, though.
Recent news regarding Nx [3], Livebook and Axon suggest there are new doors being opened for Elixir as a language in the AI/ML space. This expands what the language can be used for, and as such, could be considered as another sign of health and vibrancy in the ecosystem.
Looking at something like GitHut [4], it seems like Elixir has maintained a steady position on its rankings in terms of pull requests. This suggests that usage of the language hasn't declined in the recent past.
Lastly, the 10-year Dashbit blog post [5] by José might highlight some other development. While "development" is not synonymous with "health", I feel like the contents can suggest lack of death :)
[1] - https://elixirforum.com/t/2020-motys-and-our-5th-birthday-up... [2] - https://elixir-lang.org/cases.html [3] - https://dashbit.co/blog/nx-numerical-elixir-is-now-publicly-... [4] - https://madnight.github.io/githut/#/pull_requests/2020/4 [5] - https://dashbit.co/blog/ten-years-ish-of-elixir
In case someone here wants to read rather than listen to all the details, I wrote down some notes over at: https://elixirforum.com/t/anyone-who-wants-to-speculate-abou...
While it's probably impossible to prove one way or another, I've personally grown to accept that I will never be fully satisfied with everything in my life. Accepting that fact has given me some kind of peace, because I no longer dwell on the what-ifs as much as I used to. It doesn't matter if I reach the goals I have in mind right now, as I'm bound to come up with new ones that are just out of my reach. I believe bettering oneself is good, but I also believe it's important to accept that there's never a goal to be reached there.
I do worry about the impact it has on these "popularity tracking" services though, since the discussion living elsewhere might (falsely?) indicate that the language isn't attracting developers.
Saša Jurić made an absolutely wonderful hands-on presentation [2] of what (oftentimes rather unique) value propositions Erlang/Elixir/BEAM bring to the table. It's a very tightly-packed presentation, but I strongly recommend having a look if you're curious.
1. https://lobste.rs/s/ntati1/even_go_concurrency_is_still_not_...
And if you felt like you hadn't reached your own definition of success, then what of it? Would that really, honestly change your life in any measurable way, or is the feeling of "not being enough" all in your head? If it is, then that also means your head holds the means to get rid of such a feeling.
I really want to recommend the book "Man's Search for Meaning" by Viktor Frankl. It was one of the greatest assets for me overcoming my own depression, and I hope it can help you battle your suicidal thoughts all the same.
This approach and separation of concerns also means that building e.g. REST or GraphQL APIs on top of your application is simple, as your web framework has no say in how the data is actually structured or queried.
Being able to ship a single binary (like with Go or Rust) sounds handy, but shipping a tarball hasn't been that much of a challenge either. Being able to run BEAM code in the browser also sounds handy, but due to size issues I probably wouldn't want to ship the entire BEAM to my users either, right?
Can someone with a more thorough understanding of Lumen share some thoughts on this?
I learned that if I’m not happy, then nothing else in life will really matter to me, and that my own happiness and health are the most important things that I can have. I always knew this on some abstract intellectual level, but it wasn’t until after I had actually gotten better that I truly, deeply understood it.
Take care of yourselves out there. You’re the most important thing you’ve got.
[1] For one example, https://dockyard.com/blog/2018/12/12/phoenix-liveview-intera...
[1] https://dockyard.com/blog/2018/02/28/elixir-deployment-tools...
[1] https://www.manning.com/books/elixir-in-action-second-editio...
Could you please elaborate on this a bit? What makes you believe that the 0.19 alpha release is just around the corner?
I'm curious because my personal experience has been very much the opposite. I've built nothing but small projects using Phoenix, and I've considered it to be a very straightforward companion whenever I've needed to add a web interface to my Elixir apps.
This isn't to say that I wouldn't use SO for other purposes, as I actively visit the site for JS/PHP content. Anecdotal evidence to support your insight by all means, of course.
For a more thorough experience, however, I would absolutely recommend you to have a look at the books the Elixir community has produced. As you're specifically asking for tutorials (and not other sources for learning), my best recommendation would be Programming Phoenix [2], a book written by the creators of Elixir and Phoenix.
The book is structured so that most of it is focused on building one specific web application, so you can follow along from start to finish and build something far more interesting than just a run-of-the-mill blog (and learn a lot about Elixir and Phoenix in the progress).
[1] https://hackernoon.com/introduction-fe138ac6079d [2] https://pragprog.com/book/phoenix/programming-phoenix