josevalim

6 ms·

1.
by josevalim 2mo ago
Boom! Fixed, thanks!
2.
by josevalim 2mo ago
It should be fixed soon (deploying now). Thank you!!!
3.
by josevalim 2mo ago
It is funny (and perhaps a bit depressing) that LLMs were trained on our content and now, if we generate a similar structure as before, with the usual love and care, we will be criticized by it. Even when it does not "look bad or is a
4.
by josevalim 2mo ago
That's a good point. It is meant to be an introductory example but I will see if I can come up with something else! Thanks! EDIT: shipped!
5.
by josevalim 2mo ago
Thanks for the kind words and the nice question! 1. The cross module optimizations I mentioned above 2. Have a WASM target for the runtime itself 3. Make it easier to ship single file executables with the whole VM But they are really “nice-
6.
by josevalim 2mo ago
Can you clarify which ones? We will be glad to improve them (or feel free to send a PR).
7.
by josevalim 2mo ago
There are multiple people working on the JIT within the last 5-6 years. The WhatsApp folks also contribute meaningfully. I suspect once the Erlang/OTP team squeezes all performance in the JIT, they will look into optimizing across modu
8.
by josevalim 2mo ago
The Software Mansion folks designed it and we actually iterated on the designs on Figma, having discussions as humans, and exploring alternatives. They were lovely to work with. I also worked on all of the copy myself, collecting feedback f
9.
by josevalim 3mo ago
I don't think these articles fully cover (pun intended) the claims being made. First of all, we need to separate "types" from "static type checking". Elixir always had types and types by themselves won't elimi
10.
by josevalim 3mo ago
Lovely!!!
11.
by josevalim 3mo ago
That’s very exciting! Is there anywhere I could follow you for updates? If you don’t want to share it publicly, and is ok with sharing it privately, my email is my username on gmail. Thank you!!
12.
by josevalim 3mo ago
Agreed on the guardrails bit. My point is that we still don't have much evidence that static types are an effective way to constrain the search space for coding agents, or how much value they add on top of other mechanisms. Redundancy
13.
by josevalim 4mo ago
Please file a bug report if you can indeed isolate/reproduce it (and please ping me on GitHub once you do)!
14.
by josevalim 4mo ago
No, this comes from interacting with the community, companies, and large projects throughout the years, followed by research, publishing of papers, and careful analysis on the costs and benefits of introducing said feature! Only then we add
15.
by josevalim 4mo ago
> Honest question, in the era of vibe and AI assisted coding is there any advantages of using untyped programming languages, apart from the fact that non-typed languages has more traning data for the LLM? Author here. Type systems restri
16.
by josevalim 4mo ago
That happens with a single module but not across modules because being able to hot code load modules is an essential ability in Erlang/Elixir.
17.
by josevalim 4mo ago
You are mixing runtime and compile-time dependencies. Runtime dependencies (circular or not) have no impact on compilation performance and stability. Phoenix does include one circular dependency (the layout is rendered by your endpoint an
18.
by josevalim 4mo ago
That can be a concern indeed but it is worth noting that strong arrows compose/propagate. So if you have a function without guards that calls a function that guards on said types, the caller is also strong! We will likely have mechanis
19.
by josevalim 4mo ago
Last I checked there were inacuracies. I am not sure if they have been addressed!
20.
by josevalim 4mo ago
> some stuff being sold as "all these libs/packages that haven't had any updates for over a year is fine because Elixir" I just don't buy it I maintain more than 20 packages and, except for the major ones, like P
21.
by josevalim 4mo ago
The syntax you are commenting on has always existed in Elixir, before v1.0, as part of patterns and guards. You are commenting as if we added this now but we have made no changes to the language surface. The difference is that we now levera
22.
by josevalim 7mo ago
The team that built Erlang (Joe, Robert, Mike, and Bjorn) didn't know the actor model was actually a thing. They wanted to build reliable distributed systems and came up with the isolated processes model you find in Erlang today. Event
23.
by josevalim 8mo ago
Hard to say, as it really depends on what goes wrong. In practice we would likely need to make different trade-offs (for example, do less inference).
24.
Type inference of all constructs and the next 15 months(elixir-lang.org)
14 points by josevalim 8mo ago|2 comments
25.
by josevalim 10mo ago
Correct, I pushed a fix, should be live soon! Thank you!
26.
by josevalim 10mo ago
You are right, poor phrasing on my side. Instead of focusing on C appearing twice, I should rather focus on how complex the expansion is, meaning that everytime we have to expand the BDD (which we need to do during subtyping or emptiness fo
27.
Improving web accessibility with trace-augmented generation(tidewave.ai)
5 points by josevalim 10mo ago|0 comments
28.
by josevalim 11mo ago
LiveView was still before v1.0, hence the churn, but Phoenix itself did not introduce breaking changes since v1.0, released more than a decade ago. Our skeleton for new applications change, as best practices around web apps are still evolvi
29.
by josevalim 1y ago
It was honestly a mistake from my side, as I am not a native speaker! But I was told to stick with it, since it has a gentler and unique meaning.
30.
by josevalim 1y ago
It is in our roadmap!

More ›