This is exciting! I've been meaning to host some things on FreeBSD. Coming from a Linux background, the question of how to ship and run my applications on there becomes quite a bit more familiar through this milestone.
I recently started a new job working on a Elixir codebase. While it took me a while to understand the architecture and conventions (just like with any language, I guess), dealing with types was not a concern when it came to navigating the codebase.
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.
Is it possible to share more details about your particular setup? I believe you, but this doesn't sound right. I've used the plugin on all three major operating systems in a wide variety of projects and configurations, and have never had this happen to me. Curious to learn more about what could be the culprit for you.
I have had the same issue as the parent poster. I'm on Windows 10. Everything was fine when I was on Elixir 1.9.2, but the moment I upgraded to 1.11.2, the ElixirLS extension just started to break frequently, or getting stuck while building. I ended up disabling it until I have time to troubleshoot further.
Apparently an incident took place in 1831 where a bridge collapsed under soldiers marching, but the Wikipedia article [1] notes that "The conclusion of the investigation was that the vibration caused by the marching precipitated the bolt's failure, but it would have failed eventually anyway".
There's more interesting information on synchronization and bridges on Veritasium's video, The Secret of Synchronization [2].
That video link about synchronisation is very interesting. Thankyou.
Synchronization of bridges, hearts, lightning bugs, metronomes, sailing clocks. Cool
The short-term goal is to add "user tracking", so we know exactly who is a given notebook session and, if they are editing anything, where their cursor is.
My hunch echoes that of other commenters here. That is, it seems like many core libraries have been quite steady and "complete" for a while now, and many people are just using them today to get work done. That isn't to say the language ecosystem would have stagnated, however.
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 :)
Elixir was dropped from the 2020 Stackoverflow survey due to lack of usage (it was there in 2019).
In Tiobe index Elixir isn't in the top 45.
Jobs aren't that plentiful.
Seems like as a community Elixir needs to use alternative measures ("Elixir Forum") because the conventional measures don't look good.
And saying Elixir may become a popular option for ML is beyond wishful thinking.
Pretty disappointing to see it using XLA. Anything Tensorflow is notoriously difficult to build on a local machine and generally considered a dependency nightmare. I would've thought libtorch bindings would be much easier.
Our compiler backends are pluggable. We went with XLA because that seemed the most accessible to us 3 months ago but you should be able to bring in libtorch or any other tensor compiler.
That's actually one of the things I am really looking forward to: see what other compilers people will integrate with. I am aware some of the neural network libs have pluggable compilers but it will be interesting to see it done at the tensor level. :)
This topic of success and what contributes to it always makes me think back to this great video by Veritasium (aka. Derek Muller) titled "Is success luck or hard work?" [1].
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've dabbled in Elixir for quite a lot over the past few years, and I have to agree with the general trail of thought you're showing. If I have a question about Elixir, I don't even think about going to StackOverflow for it. I either go ask on ElixirForum, or Google for my problem (which, in most cases, lands me to an ElixirForum thread rather than a StackOverflow one). I think the surge in the use of ElixirForum is inversely correlated with the use of StackOverflow: the more the forum has grown, the less reason there has been to use SO.
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.
One major thing would probably be OTP, which would be very difficult to implement as-is on top of Go. A recent comment thread [1] over at Lobste.rs explored this in more depth.
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.
