Live data from Hacker News

Elixir 1.11

elixir-lang.org

61–70 of 104 posts

Re: Elixir 1.11

#61
Pretty stoked for this. I started learning Elixir a few months ago [0] and it's been a great balance of fun + practical. Way easier to get up and running compared some other FP languages I've dabbled with in the past :P

Also shameless plug: we're currently working on an open source messaging product called Papercups [1] if anyone is looking for an Elixir project to hack on!

[0] https://www.papercups.io/blog/elixir-noob

[1] https://github.com/papercups-io/papercups

Re: Elixir 1.11

#62

Earlier quoted context omitted.

Think about young startups that aren't sure when the next round of cash will come and their personnel stay there on average 2, 2.5 years. Spending 6-8 months on getting a new developer productive with a new language is super expensive for such a company. In fact, employing juniors in general is pretty risky for such a company.

A senior developer though should be able to get productive with a new language in a few weeks. It's not such an investment ....

Sorta true, often times not really. You can ship code that most likely works, but I'd still prefer a senior who knows the stack over you if I was the founder. You're saying in depth knowledge of a framework / language counts for nothing?

Re: Elixir 1.11

#63

Earlier quoted context omitted.

https://insights.stackoverflow.com/trends?tags=elixir Now you may say Stackoverflow isn't a good measurement. In Tiobe Elixir hasn't made it to the top 50 https://www.tiobe.com/tiobe-index/ There is little reason for me to believe Elixir is before it's peak, the data is showing otherwise. Elixir's contemporaries (Rust / Go / Kotlin) are at a totally different place usage wise. So I tend to think this is it for Elixir…

That’s very little data to make such broad claims. Up until 2017 or so, you could see the Elixir community active on StackOverflow with answers from José, Chris and most maintainers. Then the community collectively moved to Elixir Forum. Wouldn’t you prefer to ask questions where the maintainers can also answer? Per the Elixir Forum stats, the number of active users keep growing. I won’t comment on TIOBE because you…

OK found something to help us quantify this debate https://towardsdatascience.com/these-are-the-real-stack-over...

Now this is interesting because this counts question page views, not questions asked.

You can choose Elixir in that embedded tool, it's too bad its only for 2017-2018 but it still validates my point. My guess is the numbers for 2019-2020 are worse for Elixir.

Re: Elixir 1.11

#64

Pretty stoked for this. I started learning Elixir a few months ago [0] and it's been a great balance of fun + practical. Way easier to get up and running compared some other FP languages I've dabbled with in the past :P Also shameless plug: we're currently working on an open source messaging product called Papercups [1] if anyone is looking for an Elixir project to hack on! [0] https://www.papercups.io/blog/elixir-no…

I know you from your previous ShowHN, good luck, your product looks great!

Re: Elixir 1.11

#65

All I could only ask for today is just a better ide support. I don't like vscode; even though the plugin for intellij has improved, there is still a lot to be desired

The IDE type tooling is getting better all the time thanks to Elixir-LS. There was a 0.6 release a couple of days ago with a ton of improvements [0]. Better auto-completion triggers and Ecto completion come to mind as huge quality of life improvements. 0: https://github.com/elixir-lsp/elixir-ls/blob/master/CHANGELO...

Is this supported in IntelliJ ?

Re: Elixir 1.11

#66

Earlier quoted context omitted.

I work in Elixir most of the time but can read and write Erlang reasonably well, here's my two cents. Elixir's syntax was inspired by ruby and so if you've used ruby or look at ruby code and think, "yea, I get what's going on here" then you will likely find working with Elixir's syntax preferable to Erlang. Erlang's syntax was based off of Prolog and so it will be less familiar, unless you have done a bunch of Prolog…

Speaking for myseld, rebinding variables in Elixir is my least favorite part of the language, and I specifically avoid using the feature.

Yea, I'm mostly approaching this from the point of view of learning any new language is climbing a learning curve. If you are coming from most of the mainstream languages (java, javascript, python, etc) you are going to want to rebind things because that's how imperative languages roll.

This is probably colored from my own experience of going from Python (mainly) to Elixir (mainly). As a toy example, imagine having to remove all the negative numbers from a list in the middle of a function.

Most python programmers would reach for a list comprehension after learning about list comprehensions (which is great because they are more FP)

  my_list = [number for number in my_list if number >= 0]
So you pick up Elixir and you are trying to do the equivalent thing after reading through the docs

  my_list = for number = 0, do: number
And that works fine, it's my_list is exactly what you expect, no negative numbers.

Let's try the same thing in Erlang

  MyList = [X || X = 0].
  ** exception error: no match of right hand side value 
As a new user coming to the language, trying to do something so simple and getting a somewhat opaque error message is a significant degree of friction.

I have found that when I want the old value of a variable to no longer be available rebinding the name is a great way to ensure that. If in the future I decide that I need the old value later on in the function I can always just change the bind to some other name easily enough, but it prevents me from using state when I meant to use updated_state.

Not to say one way is better than the other, I just found this use of rebinding to work well for me by making it "impossible" to use the old / stale / out-of-date value.

Re: Elixir 1.11

#67

Earlier quoted context omitted.

The IDE type tooling is getting better all the time thanks to Elixir-LS. There was a 0.6 release a couple of days ago with a ton of improvements [0]. Better auto-completion triggers and Ecto completion come to mind as huge quality of life improvements. 0: https://github.com/elixir-lsp/elixir-ls/blob/master/CHANGELO...

Is this supported in IntelliJ ?

No idea. It is the foundation of VSCode and most of the other plugin systems powered by the language server standard.

Re: Elixir 1.11

#68

Earlier quoted context omitted.

That’s very little data to make such broad claims. Up until 2017 or so, you could see the Elixir community active on StackOverflow with answers from José, Chris and most maintainers. Then the community collectively moved to Elixir Forum. Wouldn’t you prefer to ask questions where the maintainers can also answer? Per the Elixir Forum stats, the number of active users keep growing. I won’t comment on TIOBE because you…

OK found something to help us quantify this debate https://towardsdatascience.com/these-are-the-real-stack-over... Now this is interesting because this counts question page views, not questions asked. You can choose Elixir in that embedded tool, it's too bad its only for 2017-2018 but it still validates my point. My guess is the numbers for 2019-2020 are worse for Elixir.

I don't see how this is any better. Most traffic on SO comes from search engines and if the questions and answers are elsewhere, such as in the Elixir Forum, then search engines will lead devs away from SO.

You say the language is in decline and none of this is solid evidence that's the case. It just says Elixir devs are not really active in Stack Overflow, which anyone in the community would be able to quickly point out.

Re: Elixir 1.11

#69
post #45

Earlier quoted context omitted.

Which ultimately makes those rare and esoteric stacks less likely to survive because experienced engineers who don't have experience with those particular stacks have no ways of getting those jobs without experience in those jobs. Companies like Jane Street make more sense. They use ocaml but they don't expect you to have any ocaml experience coming in, but they also have plenty of resources for training and hiring t…

Think about young startups that aren't sure when the next round of cash will come and their personnel stay there on average 2, 2.5 years. Spending 6-8 months on getting a new developer productive with a new language is super expensive for such a company. In fact, employing juniors in general is pretty risky for such a company.

Of course, the startup is doing what it takes to survive. I'm not saying this approach is wrong in any way. I'm just saying that this will result in these niche stacks staying niche and have a much smaller dev pool to hire from, now and in the future.

Re: Elixir 1.11

#70

Earlier quoted context omitted.

"Functional BUT utilitarian" ? You mean "Functional AND utilitarian" because for me these both are very welcome features.

The conjunction here is purely to taste, since utilitarian implies functional, as well as not particularly attractive; both are correct (as would just 'utilitarian', since it's not a loss of information, implying as it does the functional aspect).

I read that comment less literally and more like “they just about work for their function, but damn they ugly” :-)
Post reply on HN