I can “compose” what I want and don’t have to worry about changing a class style and having it mess up something elsewhere in my application. The classes are very focused in what they do.Then I became much more productive when designing new things myself. It doesn’t take long to get the hang of it.That’s where the other, less tangible benefits of TailwindCSS come in. How’s that different than buying something like Bootstrap designed components and pages? Trading my money for time is a good exchange in my book! However, that only describes the benefit of paying for designed components. The benefit I got from TailwindUI (the paid for designed components), is that I could rapidly build something that looked great. I used to spend hours tweaking my UI CSS and succeeding in making it only marginally less crappy. The benefits that I see from TailwindCSS and TailwindUI is what it enables individuals and small teams to do. It was actually this conversation that convinced me to try it out! In episode #21 of the Thinking Elixir Podcast, we interview Patrick Thompson about the combination of TailwindCSS, Alpine.js and LiveView. ![]() Because of that, it pairs really well with Phoenix LiveView. He liked the Vue.js style so he created Alpine.js specifically to fill that role.Īlpine.js was created with this LiveView/LiveWire approach in mind. While creating LiveWire, he realized that some lightweight Javascript was still needed. Alpine.js was created by Caleb Porzio, the creator of Laravel LiveWire. Clicking to open or close a menu should not require communication with the server! There are still elements of the UI that need javascript. The removal of entire layers that require design, testing, maintenance and coordination between multiple people and teams brings a huge boost to team productivity! Still using javascript This means a smaller team can deliver compelling solutions faster than rival products built by much larger teams. Removing those layers means maybe I don’t need a separate and dedicated front-end team to manage the complexities of our continually changing Javascript build pipeline. I choose to go the LiveView route not because Javascript is “bad” or because “I don’t want to use javascript”, but because I can completely eliminate all those layers! Front to back testing also becomes a much easier!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |