Yes "the continuity of residence" is required for naturalization.
> An applicant for naturalization ... must have resided continuously in the United States after his or her lawful permanent resident (LPR) admission for at least 5 years prior to filing the naturalization application and up to the time of naturalization.
To be fair, what made Elixir take off, other than syntax there is also the developer experience overall, including documentation, package manager, unit testing framework out of the box, web-framework initially inspired by Rails etc.
Though, slightly off topic, but worth mentioning, that both Erlang and Elixir communities support each other very well. For example, now not only elixir is built on top of Erlang, but also Erlang adopts some things from elixir, such as monadic expression `with` from elixir inspired `maybe` in Erlang, or starting OTP27 Erlang is using ExDoc introduced by Elixir to generate documentations.
Do you know what other ecosystem comes closest to the existing in Python? I've heard good things about Julia.
13 years ago when I was trying to explore the field R seemed to be the most popular, but looks like not anymore. (I didn't get into the field, and do just a regular SWE, so I'm not aware of the trends).
There is also a lot of development in Elixir ecosystem around the subject [1].
I guess it has something to do with those functions frequently used in guards.
_Notice tuple_size/1, map_size/1, byte_size/1 and some other functions/macros are defined in Kernel and documented in the section Guards[0]_
We can't invoke remote functions (which Tuple.size/1 would have been) in guards.
Though, there are some other functions that I can't think of a reason why they are "orphaned" such as put_elem/3 to put element into a tuple, while, for example, for maps there is Map.put/3
Some companies from the section "Who is using Elixir" are probably not using elixir anymore unfortunately.
1. Bleacher Report gutting out OTP[0]
2. I've heard that Toyota Connected also ditched elixir after some changes in the leadership of the department (just rumors I heard in the hallway tracks at ElixirConf)
For those who is interested, as mentioned in the article, Gleam is already near v1 (v1.0.0-rc2)! And in a recent talk[1] Louis shared the idea, that there won't be major changes to the language anymore, and the main focus now is switching to the tooling!
They also used to be "pretty jazzed about Elixir" and had it in their stack [1], at least while Steve Cohen was there (btw, Steve is also the author of lexical[2] - one of the newer Elixir LSPs out there)
AFAIR, it should be possible to convert dialyzer specs to that new type system annotations. It would probably be not as precise, but could be a good enough starting point to then gradually make them more precise
> but I went with Elixir instead and just wish I could use that everywhere.
Same here! I would say, I'm in the similar camp as your colleagues but about Elixir. I'm glad to choose the right tool for the job as long as it's Elixir :)
> One of the strengths of GenServers is that they allow us to spin one up per user very easily, so they don't become a bottleneck where the Agent does.
Agent is a special case of GenServer[1]. With the same luck we could spin up an agent per user.
I think the parent commenter is not saying to write your one time use query in elixir using wrapper modules with Ecto, but tried to show that queries generated by Ecto are pretty clean and understandable in compare to other popular DataMappers/ORMs