lt-app VS hex_core

Shout out for an app called Language Transfer that I just came across via Reddit (https://www.languagetransfer.org/). It teaches languages speaking first through a simple audio course. Developed by one guy, completely free and without ads, but from what I’ve seen so far has a very clear focus on quickly getting up to speed with a different angle than other courses.

This is the basic idea behind the Language Transfer series of courses - https://www.languagetransfer.org/

I highly recommend www.languagetransfer.org. He teaches key grammar in a very thoughtful way.

googled it and got https://www.languagetransfer.org/. I assume thats what you were referring to. Can you please share why you recommended that program in particular over others?

Language Transfer has free audio courses for the languages you listed. I did the spanish course and some of the italian. It's honestly the best and most comprehensive audio course I've ever come across. It got me from nada to being able to effectively communicate and understand spanish (albeit with a limited vocabulary). It's heaps better than luodingo!

The guy behind Language Transfer, u/LanguageTransfer, one of the best language learning resource for Spanish, is from Cyprus. I’m not sure whether from the Greek or Turkish side though.

We give similar examples in our anti-patterns docs: https://hexdocs.pm/elixir/main/code-anti-patterns.html#compl...

## State management

Generally agreed. Just one nit:

> Sure the state is all encapsulated into processes, but then those processes are hidden behind an abstraction layer that makes them invisible, so really you’re just touching global variables.

They are not invisible. You can use Observer, the Phoenix Live Dashboard, and many other tools to traverse, explore, and navigate the supervision tree, processes, and see where all state is!

## Imports

Agreed. We had several discussions on how to improve this but nothing satisfactory. Maybe it is time for another tango.

## Mixed messages

I'd say we actually do a good job on the official docs on the topics that are directly related to Elixir:

* On umbrella projects, the official guide discusses trade-offs: https://hexdocs.pm/elixir/dependencies-and-umbrella-projects...

* Live upgrades are covered in our release docs: https://hexdocs.pm/mix/Mix.Tasks.Release.html#module-hot-cod...

* On macros: https://hexdocs.pm/elixir/macro-anti-patterns.html#unnecessa...

I assume the trouble is in finding this information, so if anyone finds we should link to them from other places, pull requests are welcome. In general, PRs to improve docs are always gladly received, be in Elixir, Ecto, or elsewhere!

## Others

> Anecdotally, when Elixir started off there was some bad blood between them and the Erlang community, which is the origin of this schism

No bad blood, really. I asked the `rebar` team (not the current `rebar3`) if they would accept PRs to also compile Elixir, they said no (which is understandable) and then we move forward with `mix` (which was a contribution from a Clojure developer inspired by `lein`). The projects drifted apart but we often share whatever we can in other places (such as https://github.com/hexpm/hex_core).

> In fact the Elixir compiler almost never gives you an outright error, basically it only fails if a file can’t be parsed. This feels spooky as hell… but its warnings are basically always correct and seldom miss anything

Yes! Our goal is to avoid halting compilation as much as possible and instead rely on precise warnings. It is easier to debug a program that compiles (and then raises) than one that does not compile at all.