josevalim

11 ms·

91.
by josevalim 2y ago
I have always considered helping the community grow into a diverse ecosystem to be my main responsibility (the Python community being a great example here). This particular effort started because some people got together and realized that w
92.
by josevalim 2y ago
Correct. When I did the presentation, I did mention we attempted to type Elixir and failed. Therefore, the idea of saying the language was "complete" was precisely to signal the community that most of the work would happen in the
93.
by josevalim 2y ago
Thank you.
94.
by josevalim 2y ago
> These libraries just aren’t “there” yet, and I think it’s important to be honest about that. Exactly. These projects are still during early adoption stage. While it is production-ready and many are doing so, getting there requires impr
95.
by josevalim 2y ago
> People have to realise these are mostly for hobby. It is really hard to get these working with other libraries. I have been dealing with this type of feedback for almost 20 years at this point: "This library doesn't work for
96.
by josevalim 3y ago
You are not wrong but you may be hinting at the wrong cause. It is hard to generate a useful graph or summary that gives actionable feedback once you reach a certain amount of nodes. Even mix app.tree, which has no cycles, is barely useful
97.
by josevalim 3y ago
I am Mox author and, honestly, I rarely use it. The most important part is to think strongly about what you are mocking and your interfaces (explicit or implicit). Once I do that, I do my best to use plain anonymous functions, modules, or p
98.
by josevalim 3y ago
I enjoyed reading the previous articles, so I was excited to read this one too. I really appreciate this style of feedback. Comments below. ------- ERROR HANDLING In my opinion, the "with {:is_email, true}" style is missing the fo
99.
by josevalim 3y ago
Exactly! The hard part was to find a type system that we can map most (if not all) Elixir constructs to, and set-theoretic types have been a great fit so far and we were able to develop the theory in the areas where it lacked.
100.
by josevalim 3y ago
It is not a goal of the type system at the moment, as we will focus on software correctness and developer experience. However, keep in mind the Erlang VM already uses typing information (from patterns, guards, and built-in functions) to opt
101.
by josevalim 3y ago
The examples will be very gradual - no pun intended - as we need to go through each Elixir construct and either add inference (if a pattern or a guard) or type checking rules. Right now we infer and type check one single construct (bitstrin
102.
by josevalim 3y ago
Thank you for the nice words, it is appreciated and it makes a difference whenever I am having a bad day. :)
103.
by josevalim 3y ago
There is a similar discussion here: https://news.ycombinator.com/item?id=38544486 TL;DR: you get granular and programmatic scaling, including the ability to scale using specific resources (for example, machines with GPUs fo
104.
by josevalim 3y ago
Yes, the local backend runs on your machine, and you would debug it like any other Elixir code on your project/machine.
105.
by josevalim 3y ago
Wouldn’t you lose, for example, streaming capabilities once you use Celery? You would have to first upload the whole video, then enqueue the job, and then figure out a mechanism to send the thumbnails back to that client, while with FLAME y
106.
by josevalim 3y ago
I believe the reason why we have seen so many different numbers given as limits for distribution is because they are often measuring different things. As you know, the limits will vary depending if it is just distribution or if global/
107.
by josevalim 3y ago
> Relying on shapes instead of types to identify results / objects Is the issue lack of types or relying on shapes? Those can be orthogonal features, since you can have structural typing (i.e. types that are built on top of shapes).
108.
by josevalim 3y ago
It runs fine, but using metal is complicated. We provide bindings for both libtorch and XLA. Libtorch has better metal support but still incomplete, with types and functions missing. Apple released a driver for XLA and it is, unfortunately,
109.
by josevalim 3y ago
Hi everyone, author here. This is a roundup from multiple projects and collaborators within the Elixir+ML ecosystem. I will be glad to answer questions where I can. :)
110.
Elixir and Machine Learning: Q3 2023 roundup(dashbit.co)
39 points by josevalim 3y ago|5 comments
111.
by josevalim 3y ago
Sorry to hear this. Phoenix v1.7 changed how it structures files in disk and that broke quite some of the getting started material. However, the guides are always kept up to date, so you can give it a try: https://hexdocs.pm&#x2F
112.
by josevalim 3y ago
Hi HerrBertling! I am glad you are enjoying Elixir and learning new things, I appreciate the nice words and the opportunity to be a positive influence. :)
113.
by josevalim 3y ago
> Erlang and Haskell have been hovering at under 1% for several decades. I am well aware that I am nitpicking at this point, but putting a restriction on your metric that rules out 99% of programming languages makes the comparison quite
114.
by josevalim 3y ago
Hi jerf! I feel this is evaluating Erlang from an angle it is not really prescribed as a solution for. Erlang's goal was never to be your company's message bus. Or your k8s. Even hot restarts have always been advertised as an extr
115.
by josevalim 3y ago
> One thing I would add, is Erlang/Elixir's emphasis on multi machine concurrency is somewhat at odds with the serverless future we're moving towards IMO, that's a misconception. They work at different levels and I wr
116.
by josevalim 3y ago
> it is rare that a language doubles its market share (assuming it's not in the vicinity of zero) after its first decade JavaScript, Python, and Ruby are all counter-examples. Erlang and Haskell might as well. I don't think tim
117.
by josevalim 3y ago
If it comes to this, we will certainly need to have a discussion on the topic. So I am definitely open to discussing the idea!
118.
by josevalim 3y ago
It is impossible to ignore the set theoretic type aspects, because the whole foundation of strong arrows is based on being able to negate a type. If I don't explain the set theory bits, then the rest of the article falls apart. I could
119.
by josevalim 3y ago
This is a surprising assessment given most of the blog post is explaining how to build the type system in a way it can give feedback on all _existing real projects_ already written in Elixir. :) It is the opposite of optimizing for type the
120.
by josevalim 3y ago
I understand many would love to have this yesterday but I strongly believe we should not speed it up. :) This is potentially the largest change the language will ever go through and we are being very intentional and deliberate on every step

More ›