Live data from Hacker News

Elixir 1.12

elixir-lang.org

91–100 of 109 posts

Re: Elixir 1.12

#91
post #65

Earlier quoted context omitted.

> if a call at the beginning of the pipeline returns a tuple of `{:ok, result}` In my understanding, pipeline are mostly reserved for “unfailable” operations operating on raw data; whereas the where/else/do macro is more oriented towards errors handling; would it work better in your case?

I think you mean `with`, not `where`? Yes, it helps a bit in some cases, but it's not a replacement for a pipeline - mainly because you'd need to name your intermediate results and "thread" them through the calls yourself. I think I gave a bad example, the better one would be a function returning datetime in the format of :erlang.localtime: `{{Year,Month,Day},{Hour,Min,Sec}}`. I would like to be able to use this valu…

Hm, this works and is about as terse as `pattern_tap`:

    :erlang.localtime()
    |> case do; {_, {h,m,_}} -> {h, m}; end
    |> do_something
Not that I'd want to do that in production code, but I felt a bit nerd-sniped here, to see the shortest way I could find without dependencies.

Re: Elixir 1.12

#92
post #4

See also, https://news.ycombinator.com/item?id=27192873 (Ask HN: Are you satisfied with Elixir or do you regret choosing Elixir?) with great insights about the language. Another popular thread that comes to mind is the one about Discord scaling Elixir ( https://news.ycombinator.com/item?id=14748028 and https://news.ycombinator.com/item?id=19238221 )

Sadly that HN thread is biased toward the person/team that is "leaving" Elixir because it wasn't a good fit for them. For the people who understand Elixir/OTP's strengths it's excellent. We use Elixir for several apps and haven't had any issues recruiting/training people (remote). If we were to chose again we would 100% pick Elixir; nothing else comes close for our use-case.

> Sadly that HN thread is biased toward the person/team that is "leaving" Elixir because it wasn't a good fit for them

Having a balanced pros and cons are great for everyone. Not every thread should be praising Elixir else people won't be able to make an informed decision before selecting a language to build their business on.

I'm personally more interested in cons of a tool as opposed to the pros. This way I can assess whether the failure points are within the acceptable parameters or not.

Re: Elixir 1.12

#93

Earlier quoted context omitted.

I went though that persons submissions/comments on HN. its literally the only time they mention Elixir, everything else is ruby/rails or python. Makes me wonder if it's a troll post.

What made you do that? Genuinely curious. You immediately suspect trolling when you see people complaining about Elixir?

Oh yes, @joelbluminator, the troll-in-chief when it comes to Elixir posts. You really have an axe to grind against this language, do you?

> For one I really do think Elixir is a horrible career choice and I wanna save young average developers who still have time to correct that mistake (https://news.ycombinator.com/item?id=27204755)

Sadly, your trolling is too subtle to get shadow banned, so we are doomed to keep reading your inane comments in every Elixir thread, hiding under the cowardly guise of "doing it for the young developers."

https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...

> Im not at all negative about Elixir. It could be a fantastic tool, I never used it. (https://news.ycombinator.com/item?id=26905869)

Re: Elixir 1.12

#94

Earlier quoted context omitted.

What made you do that? Genuinely curious. You immediately suspect trolling when you see people complaining about Elixir?

Oh yes, @joelbluminator, the troll-in-chief when it comes to Elixir posts. You really have an axe to grind against this language, do you? > For one I really do think Elixir is a horrible career choice and I wanna save young average developers who still have time to correct that mistake ( https://news.ycombinator.com/item?id=27204755 ) Sadly, your trolling is too subtle to get shadow banned, so we are doomed to keep r…

[deleted]

Re: Elixir 1.12

#95

Earlier quoted context omitted.

What made you do that? Genuinely curious. You immediately suspect trolling when you see people complaining about Elixir?

Oh yes, @joelbluminator, the troll-in-chief when it comes to Elixir posts. You really have an axe to grind against this language, do you? > For one I really do think Elixir is a horrible career choice and I wanna save young average developers who still have time to correct that mistake ( https://news.ycombinator.com/item?id=27204755 ) Sadly, your trolling is too subtle to get shadow banned, so we are doomed to keep r…

[deleted]

Re: Elixir 1.12

#96

Earlier quoted context omitted.

What made you do that? Genuinely curious. You immediately suspect trolling when you see people complaining about Elixir?

Oh yes, @joelbluminator, the troll-in-chief when it comes to Elixir posts. You really have an axe to grind against this language, do you? > For one I really do think Elixir is a horrible career choice and I wanna save young average developers who still have time to correct that mistake ( https://news.ycombinator.com/item?id=27204755 ) Sadly, your trolling is too subtle to get shadow banned, so we are doomed to keep r…

[deleted]

Re: Elixir 1.12

#97

As an aside, I teach Elixir as part of my distributed systems MSc course. Anyone here in the London area (or even UK) looking for junior engineers? It would be nice to have some companies to point my students at when they start looking for jobs (or year in industry).

Oh really cool! Which University then?

Re: Elixir 1.12

#98

Earlier quoted context omitted.

I think you mean `with`, not `where`? Yes, it helps a bit in some cases, but it's not a replacement for a pipeline - mainly because you'd need to name your intermediate results and "thread" them through the calls yourself. I think I gave a bad example, the better one would be a function returning datetime in the format of :erlang.localtime: `{{Year,Month,Day},{Hour,Min,Sec}}`. I would like to be able to use this valu…

Hm, this works and is about as terse as `pattern_tap`: :erlang.localtime() |> case do; {_, {h,m,_}} -> {h, m}; end |> do_something Not that I'd want to do that in production code, but I felt a bit nerd-sniped here, to see the shortest way I could find without dependencies.

That's actually what pattern_tap's tap macro expands into :) See: https://github.com/mgwidmann/elixir-pattern_tap/blob/master/...

Re: Elixir 1.12

#99
post #9

The one thing I’ll say about Elixir I’m always impressed how disciplined they are with the issue tracker on GitHub. Currently 17 issues for such a broad piece of work seems nothing less than astonishing.

That's partly because Jose is a machine. I have one anecdote that might provide some insight:

I filed a bug that turned out to be an incorrect dialyzer spec on a library function. Jose fixed it and merged the fix to master within 40 minutes of me filing the bug. It was a small issue, and I had done a reasonable job at bug filing (small test case, pointers to source of problem) but to have that level of discipline and responsiveness on bug fixing is spectacular.

Re: Elixir 1.12

#100

As an aside, I teach Elixir as part of my distributed systems MSc course. Anyone here in the London area (or even UK) looking for junior engineers? It would be nice to have some companies to point my students at when they start looking for jobs (or year in industry).

Oh really cool! Which University then?

[deleted]
Post reply on HN