Never have heard of it:
It seems to compile to pure Erlang code, isn’t that a disadvantage when compared how Elixir and Gleam do it?
Oh, and that syntax with in in the end and full of if else 
Exadra37
dimitarvp
I admit I haven’t dug in the deals. I got attracted by the promise of strong and static typing at the compile stage, and the OCaml syntax.
I seriously have no time for such nice little distractions though…
OCaml is recursive; in means that you are nesting this statement into the next one – otherwise the next statement won’t have access to variables declared in the previous one(s). It’s quirky, I admit.
if / else can be replaced by pattern-matching, at least in the pure OCaml (not sure about Caramel).
2
Exadra37
This bit really puts me off of even wanting to try the language, despite the strong typing promise, that I want so much in Elixir.
1
wanton7
My understanding is that you will also able to use Facebook’s ReasonML syntax (https://reasonml.github.io) with Caramel because it’s just a different syntax for OCaml.
1
DevotionGeo
Me and Elixir in 2021:
I had an App’s idea which could be successful in a month (that’s what I thought then). Languages I already knew seemed insufficient for that app. 
After reading different blog posts, watching talks etc, I came to the conclusion that Go or Elixir will be a perfect fit for that app. I started learning both of these languages.
Elixir made me a better programmer. I can’t explain how exactly, but it surely did.
Things I liked about Elixir when I got into it, were the pipe operator, pattern matching, function clauses, function overloading, and its familiar syntax. Then I realized that its real beauty lies in its concurrency model and the OTP.
I think Elixir is enough in all the aspects for the job it’s doing, but of course I’d like to see performance improvements, and luckily and thankfully there is a lot going on in that area already.
Don’t start leaning Phoenix before you’ve learnt enough Elixir, like you did when you were learning Ruby and Rails.
4
tradfursten
I am a java developer at work but I have dipped my toes in the elixir waters and find it fashinating.
I don’t have that much experience yet with the language since I work full time with my day job and have tree small kids.
But I have a small side project that I would like to build with elixir, phoenix and live view.
4
Nicd
What first drew you to it (how long ago!?) and what keeps you here?
I started looking at Elixir when it was <0.10, back in 2013. The first commits I can find are titled “Fix deprecations in Elixir 0.10”. 
I was actually looking at Erlang first because I wanted to learn a functional programming language and I was interested in distributed systems. An IRC acquaintance suggested Elixir and I was instantly interested. I have to admit syntax was a big part of that.
How have you found it has changed over the years?
No more lc, records were deprecated, maps got power and structs appeared, got rid of multiple competing datetime datatypes, the standard library datetime functionality is very featureful now, Hex.pm appeared, ElixirLS appeared, and all around the tooling improved so much. Also we finally have blessed releases and runtime configuration! 
The community has grown from an IRC channel to Slack, Discord, Matrix, and this awesome forum.
How have you changed, perhaps while using it? (Maybe you came from an OOP language and your mental model on how to build things has changed?)
Elixir was my first functional programming language and it shows in my early code. The most immediate impact I noticed was that I grokked map/reduce and their power. I started using them in OO languages too, and I think it has really improved me. I started splitting code into smaller, easily testable units, with less dependencies on object state. I nowadays have a healthier balance and can appreaciate aspects of both styles. Though I wish every language had immutability.
What do you think were the biggest strengths of Elixir/Erlang when you got into it and what do you think are its biggest strengths now?
It was BEAM for humans. No offense to Erlang, but back then it wasn’t inviting and the tooling wasn’t there. Nowadays Erlang has improved a lot and in general it feels like the BEAM community has exploded in both variety and quality of tooling.
I think BEAM is the biggest strength. What the VM offers is hard to find in other languages and there’s not many things that I find it lacking in, at least those that would touch me. In other words for me there’s no tradeoff to be made. Except the smaller size of the community when you compare to the giants.
Is there anything you’d like to see more of or improved or included?
Removal of charlist single quote syntax and pretty printing. Replacement of kwlists with maps in most function arguments. Typing! Very excited about Gleam/Caramel, though I haven’t tried them yet (there’s only so much free time).
Which bits do you love the most and which bits are you most likely to tell others about?
BEAM BEAM BEAM. The high quality stdlib, especially the string and datetime handling. Effortless concurrency that is used for things like Phoenix Channels. It’s like an OS for my project where I can start programs that talk to each other.
Also Nerves, Nerves is seriously awesome.
What’s your single most important tip to newbies?
Join the community chats, we’re quite friendly and really try to help you in your projects.
Which book or learning resource has been your favourite to date? (How many have you read? Which ones have been your favourite!?)
Metaprogramming Elixir made me finally understand macros. I have Elixir in Action but to my great shame I haven’t read it yet, though I hear great things of it. In general I’m not a reading person, I just hop in and mash code with the help of the API docs.
Hanging around on the different help channels and this forum makes you learn a lot of different things over time. I’m really grateful to all the good people helping others.
5
dimitarvp
A small, likely unrelated tidbit: while I was still coding both in Ruby and Elixir back in 2016, I’ve made a habit of using Ruby’s object.freeze method to reduce my potential bugs area. IIRC any attempt to modify a frozen object results in an exception, making it times easier to track down code that attempts to introduce invalid state.
Same for me. The runtime itself is the biggest asset. Everything else is a nice bonus and just sealed the deal for me after the first few months with Elixir. To me the other huge strengths are the mix tool and the property testing library stream_data. And macros!
Well, let’s become friends because we are apparently brothers already. 
2
Nicd
Yeah, after using Elixir for a while, I started using Object.freeze in JavaScript projects. For example when we retrieved anything from an API, we’d freeze the data before passing it to any frontend logic. This helped find accidental mutation bugs in the code. But it was a bunch of manual work.
1