Here's an overview, case study and comparison to Phoenix of the V part of Rails MVC as experienced across the years. Rails organizes the view part of the MVC into views and helpers. You are supposed to put templates for each resource/controller into the app/views subdirectories and to put the accompanying helper code into app/helpers which are by default generated per-resource as well. In practice
Both Rails and Phoenix can manage and deploy assets for you. But the approaches and solutions differ greatly. Development toolsAs a NPM based tool, Brunch recognizes that modern JS is not just jQuery and browser stuff but also a wide choice of development tools. It allows dev-only JavaScript dependencies, just like in mix.deps or Gemfile, so tools like ESLint are no longer second-class citizens. T
As I was thinking about this article a few weeks ago, I was excited when I saw that Chris McCord, creator of the Phoenix Framework in Elixir, was on the Elixir Fountain podcast. One of the things they mentioned on the show was that they were tired of the comparison being made between Rails and Phoenix. The bias of coming from a Rails background may cloud your view of the framework and cause you to
A few years ago, I wrote an article about moving from Django to Rails. As I said there, I don’t find it too hard moving from one programming language to another, as long as you have good knowledge on concepts they all share. Each language, of course, brings something on its own. Last year, I decided to try something new. As a Ruby developer, Elixir proved to be a logical choice, and I have to admi
Stay Relevant and Grow Your Career in TechPremium ResultsPublish articles on SitePointDaily curated jobsLearning PathsDiscounts to dev toolsStart Free Trial7 Day Free Trial. Cancel Anytime. Key Takeaways Phoenix, a web framework built for Elixir, is similar to Rails but offers better support for technologies such as WebSockets and can scale better due to being built on the Erlang Virtual Machine.
Background While developing an interactive B2B marketplace platform, it became apparent that writing a scalable order-writing backend would need the capacity to do highly concurrent database reads and writes based on the volume of our customer’s requests. We needed it to update inventory counts in as real-time as possible to avoid users placing orders that couldn’t go through. Other parts of the a
This is not a, "Which is better?", post. It is more a way to help other developers, like myself, who have a background in Rails development and are interested in Elixir and Phoenix. While working my way through converting elFormo, Grok's form processing service, from Ruby/Rails to Elixir/Phoenix, I have found it helpful when others would use a concept in Ruby or Rails as a point of reference for u
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く