I''m all for simple stacks, i'm hesitant at anything dynamically typed though (seems they don't do implicit conversions but you're still going to get runtime errors rather than compile time if i'm...
I''m all for simple stacks, i'm hesitant at anything dynamically typed though (seems they don't do implicit conversions but you're still going to get runtime errors rather than compile time if i'm reading right?).
Either way though, the site is...odd (doubly so if you look at the sister postgress site).
The image shows Elixir + Phoenix replacing a whole stack of stuff, including redis, then a few lines later we have the same thing replacing websockts, but if you want to replace background jobs, the equivalent of redis is now Oban, GenServer, and Task.
Like...yeah most languages that have any adoption have libraries in ecosystem to replicate common needs. This doesn't do a great job of convincing me i'd wind up using less, as it's own flow sorta contradicts itself. Now maybe you CAN get away with just Elixir+Phoenix instead of the stack shown, but the chart below doesn't make me think so.
I''m all for simple stacks, i'm hesitant at anything dynamically typed though (seems they don't do implicit conversions but you're still going to get runtime errors rather than compile time if i'm reading right?).
Either way though, the site is...odd (doubly so if you look at the sister postgress site).
The image shows Elixir + Phoenix replacing a whole stack of stuff, including redis, then a few lines later we have the same thing replacing websockts, but if you want to replace background jobs, the equivalent of redis is now Oban, GenServer, and Task.
Like...yeah most languages that have any adoption have libraries in ecosystem to replicate common needs. This doesn't do a great job of convincing me i'd wind up using less, as it's own flow sorta contradicts itself. Now maybe you CAN get away with just Elixir+Phoenix instead of the stack shown, but the chart below doesn't make me think so.