Paolo Marino
@pmarino.dev
Senior Software Engineer, consultant and tech enthusiast.
Mostly interested in #ElixirLang
My website: https://pmarino.dev
Want to get in touch? DMs or hey@pmarino.dev
Speaks: 🇮🇹, 🇬🇧, learning 🇹🇼🇨🇳
Mostly interested in #ElixirLang
My website: https://pmarino.dev
Want to get in touch? DMs or hey@pmarino.dev
Speaks: 🇮🇹, 🇬🇧, learning 🇹🇼🇨🇳
Ecco adesso devo sentirla 😂
June 6, 2025 at 7:56 AM
Ecco adesso devo sentirla 😂
Puntata molto interessante, anche questa. Complimenti!
May 1, 2025 at 5:42 PM
Puntata molto interessante, anche questa. Complimenti!
Perhaps the fact that one would expect a LiveComponent to be its own process, while it is not, is also a source of confusion
April 29, 2025 at 9:20 PM
Perhaps the fact that one would expect a LiveComponent to be its own process, while it is not, is also a source of confusion
Very interested as well! 👀
March 25, 2025 at 4:06 PM
Very interested as well! 👀
Molto contento di trovarla anche qui!
November 15, 2024 at 7:27 AM
Molto contento di trovarla anche qui!
In that case I think is basically a different problem because processes handle messages sequentially anyways. If the outcome of the message is that the current process receives another one that would still be processed afterwards. I am not sure how knowing it upfront would change the final behaviour
November 8, 2024 at 8:51 AM
In that case I think is basically a different problem because processes handle messages sequentially anyways. If the outcome of the message is that the current process receives another one that would still be processed afterwards. I am not sure how knowing it upfront would change the final behaviour
I personally do not think it makes a difference because thinking of all calls being somewhat blocking makes reasoning about the overall code more easy for me.
Then again it depends what you mean by “async” calls
Then again it depends what you mean by “async” calls
November 8, 2024 at 8:03 AM
I personally do not think it makes a difference because thinking of all calls being somewhat blocking makes reasoning about the overall code more easy for me.
Then again it depends what you mean by “async” calls
Then again it depends what you mean by “async” calls
Well in a way writing COBOL in 2024 is kind of innovative 😂
November 7, 2024 at 7:55 AM
Well in a way writing COBOL in 2024 is kind of innovative 😂