Fantastic presentation! I’m brand new to Elixir but I understood everything since it was so clear! I’m used to functional overloading based on argument types in C++, but I was surprised that Elixir has function overloading based on pattern matching!
I’m just getting the hang of the Elixir syntax and was thinking to myself ”now, how do I do all that cool OTP stuff?”. And after watching this talk I’m ready to break new Elixir ground. Thanks for a great talk!
Not bad, Jesse. But this is more just an intro to just one OTP behaviour (design pattern). I think you may have lost a couple of people by just gliding from your initial example to using GenServer. The primary reason is because GenServers are OTP-compliant and the developer gets a ton of things out of the box, like logging, whereas rolling your own does not. I think doing a live demo also would've been better. Elixir/Erlang allows the developer to almost always code the happy-path first which helps solidify the mantra of, "let it crash". If the room wasn't full of developers test-driving Elixir, then at least a note about pattern-matching and demonstrating it quickly would've been nice, too. But all-in-all a pretty good talk :)
Awesome talk! I have one question around if you are storing your data in the process and that process is restarted, do you lose the data that had been stored? Thanks!
Bit over the top. but I would like OTP on Haskell (I know distributed exists but it's not maintained much). And I'd like a Haskell with lips macros and syntax. All of that together would be the perfect language
Fantastic presentation! I’m brand new to Elixir but I understood everything since it was so clear!
I’m used to functional overloading based on argument types in C++, but I was surprised that Elixir has function overloading based on pattern matching!
6:27 - "if this didn't fix it - I'm gonna kill myself"
10/10
I’m just getting the hang of the Elixir syntax and was thinking to myself ”now, how do I do all that cool OTP stuff?”. And after watching this talk I’m ready to break new Elixir ground. Thanks for a great talk!
Breath man, breath. I know you're nervous, but remember to breath.
lol remember to breath
Breathe man, breathe. I know you're nervous, but remember that "breath" is a noun and "breathe" is a verb.
Great talk
My first time when I learned OTP it was weird.
I think it took me to get used to the syntax.
This explanation help me a lot, thank's!
awesome stuff! Thank you :)
Great talk man. Thanks :)
That GenServer reminds me of Redux library for JavaScript ;)
Not bad, Jesse. But this is more just an intro to just one OTP behaviour (design pattern). I think you may have lost a couple of people by just gliding from your initial example to using GenServer. The primary reason is because GenServers are OTP-compliant and the developer gets a ton of things out of the box, like logging, whereas rolling your own does not. I think doing a live demo also would've been better. Elixir/Erlang allows the developer to almost always code the happy-path first which helps solidify the mantra of, "let it crash". If the room wasn't full of developers test-driving Elixir, then at least a note about pattern-matching and demonstrating it quickly would've been nice, too. But all-in-all a pretty good talk :)
I wish I'd get such constructive feedback whenever I talk
Great
Awesome talk! I have one question around if you are storing your data in the process and that process is restarted, do you lose the data that had been stored?
Thanks!
'course you do. That' the point or retarting. the speaker did say "clean slate or clean state"
Yes
Everything that isn't Haskell is pure garbage.
Why ?
Needs to be on a t-shirt
@@EricLouisYoung hahah I'd be the first one to buy that
Bit over the top. but I would like OTP on Haskell (I know distributed exists but it's not maintained much). And I'd like a Haskell with lips macros and syntax. All of that together would be the perfect language