دانلود کتاب برنامه نویسی Phoenix LiveView – برنامه نویسی تعاملی اکسیر وب بدون نوشتن جاوا اسکریپت

If you haven’t been following closely, it might seem like LiveView came suddenly, like a new seedling that breaks through the soil surface overnight. That narrative lacks a few important details, like all of the slow germination and growth that happens out of sight. Chris McCord, the creator of Phoenix, worked on Ruby on Rails before coming over to the Elixir community. More and more often, his consultancy was asked to use Ruby on Rails to build dynamic single-page apps (SPAs). He tried to build a server-side framework on top of the Ruby on Rails infrastructure, much like LiveView, that would allow him to meet these demands for interactivity. But Chris recognized that the Ruby infrastructure was not robust enough to support his idea. He needed better reliability, higher throughput, and more even performance. He shopped around for a more appropriate language and infrastructure, and found Elixir. When Chris moved from Ruby to Elixir, he first learned the metaprogramming techniques[1] he’d need to implement his vision. Then, he began building the Phoenix web development framework to support the infrastructure he’d need to make this vision a reality. At that time, José Valim began helping Chris write idiomatic Elixir abstractions relying on OTP. OTP libraries have powered many of the world’s phone switches, offering stunning uptime statistics and near realtime performance, so it played a critical role in Phoenix. Chris introduced a programming model to Phoenix called channels. This service uses HTTP WebSockets[2] and OTP to simplify interactions in Phoenix. As the Phoenix team fleshed out the programming model, they saw stunning performance and reliability numbers. Because of OTP, Phoenix would support the concurrency, reliability, and performance that interactive applications demand. In functional programming, Chris found cleaner ways to tie his ideas together than object orientation offered. He learned to compose functions with Elixir pipelines and the plugs. His work with OTP taught him to think in the same composable steps we’ll show you as this book unfolds. His work with metaprogramming and macros prepared him to build smooth features beyond what basic Elixir provided. As a result, in Phoenix LiveView, users would find a pleasant, productive programming experience. As the web programming field around him grew, frameworks like React and languages like Elm provided a new way to think about user interface development in event-powered layers. Chris took note. Some frameworks like Morphdom popped up to allow seamless replacement of page elements in a customizable way. The Phoenix team was able to build JavaScript features into LiveView that automate the process of changing a user interface on a socket connection. In LiveView, programmers would find a beautiful programming model based on tested concepts, and one that provided JavaScript infrastructure so developers didn’t need to write their own JavaScript. And so, that seed germinated and poked up through the surface. Shortly after the seed became visible, we introduced the first version of this book. Six years and hundreds of features later, LiveView hit version 1.0. In a nutshell, that’s LiveView. We’ll have plenty of time to go into more detail, but now, let’s talk about you. This book is for advanced beginners and intermediate programmers who want to build web applications using Phoenix LiveView. In it, you’ll learn the basic abstractions that make LiveView work, and you’ll explore techniques that help you organize your code into layers that make sense. We will try not to bore you with a tedious feature-by-feature march. Instead, we’ll help you grasp LiveView by building a nontrivial application together.