If not, does that mean that any variable that ends with _status gets an automated _on variable linked to it?
Elixir for Humans Who Know Python
171–180 of 198 posts
Re: Elixir for Humans Who Know Python
#172Re: Elixir for Humans Who Know Python
#173Earlier quoted context omitted.
I've got experience in both Phoenix and Django and I disagree. In my view, Phoenix is the less clean one: Django does not generate anything through scaffolding like Phoenix. Your CRUD (and auth and forms and everything more or less) is generated by overring the built-in Django classes or the classes offered by the packages. Nothing gets thrown away in real production; you use your class hierarchy to change it to your…
Elixir haskell and erlangs concurrency and parallelism story far outweigh any imperative pythonic benefits or idioms IMHO
Re: Elixir for Humans Who Know Python
#174Earlier quoted context omitted.
I'm not really familiar with Phoenix, but skimming through the section linked below, it seems to cover what you're looking for? Basically, you use a tool to generate your model + migration code and then run the migrations. https://hexdocs.pm/phoenix/ecto.html#using-the-schema-and-mi... As for the comparison to Django, I don't really expect any web framework to have docs at that level. They are simply huge and have be…
Yes, I skimmed through that and was surprised to see it be compared to Django. It's different. Django is for building CRUD apps quickly. That's it. It's not for the long haul of super complicated apps, which many projects don't ever reach before they fail/get abandoned.
Re: Elixir for Humans Who Know Python
#175Earlier quoted context omitted.
Elixir haskell and erlangs concurrency and parallelism story far outweigh any imperative pythonic benefits or idioms IMHO
Concurrency is a pet use case for 99% of projects. Library ecosystem is the primary and dominant factor when choosing general-purpose technologies and Python has it beat.
Re: Elixir for Humans Who Know Python
#176Earlier quoted context omitted.
Elixir haskell and erlangs concurrency and parallelism story far outweigh any imperative pythonic benefits or idioms IMHO
Concurrency is a pet use case for 99% of projects. Library ecosystem is the primary and dominant factor when choosing general-purpose technologies and Python has it beat.
Unfortunately The slowness of python, gil and really bad design choices of Asyncio in python 3 relative to how elegant parallelism and concurrent programming is in Racket, haskell, elixir and erlang make python a non starter for many basic use cases
Re: Elixir for Humans Who Know Python
#177Earlier quoted context omitted.
It seems like the basis for your comment is weird stack tribalism that you’ve very evidently bought into, rather than anything actually…worth discussing. It then comes as no surprise that throughout your entire comment you didn’t seem willing you yield any ground to Python or Django at all. It then comes as no surprise that your assertions about Django are counter to my experience, as someone that by the sound of thi…
It is perhaps utopia but it would be nice if we could discuss those topics without falling into camps. For example, I could argue for hours about the benefits of immutability, but I still believe that imperative loops are clearer than functional ones. There is even a repository with solutions for nested traversals in different languages and the Python one is my preferred by some margin: https://github.com/josevalim/n…
I know you started a proposal once around the time when we made that repo.
Re: Elixir for Humans Who Know Python
#178Earlier quoted context omitted.
Yes, I skimmed through that and was surprised to see it be compared to Django. It's different. Django is for building CRUD apps quickly. That's it. It's not for the long haul of super complicated apps, which many projects don't ever reach before they fail/get abandoned.
99% of line-of-business apps are CRUD. There's nothing special about "super complicated apps" that isn't brought in by the Python ecosystem. Where exactly do you think Django fails in that regard?
Re: Elixir for Humans Who Know Python
#179Earlier quoted context omitted.
I'm not really familiar with Phoenix, but skimming through the section linked below, it seems to cover what you're looking for? Basically, you use a tool to generate your model + migration code and then run the migrations. https://hexdocs.pm/phoenix/ecto.html#using-the-schema-and-mi... As for the comparison to Django, I don't really expect any web framework to have docs at that level. They are simply huge and have be…
Yes, I skimmed through that and was surprised to see it be compared to Django. It's different. Django is for building CRUD apps quickly. That's it. It's not for the long haul of super complicated apps, which many projects don't ever reach before they fail/get abandoned.
Re: Elixir for Humans Who Know Python
#180Earlier quoted context omitted.
Concurrency is a pet use case for 99% of projects. Library ecosystem is the primary and dominant factor when choosing general-purpose technologies and Python has it beat.
In a multi core world concurrency and parallelism are no longer pet use cases. Unfortunately The slowness of python, gil and really bad design choices of Asyncio in python 3 relative to how elegant parallelism and concurrent programming is in Racket, haskell, elixir and erlang make python a non starter for many basic use cases