The Business Case for Livewire

In some folks' minds, React has won the battle for frontend frameworks. But what metrics are we using to decide?

In this talk, I give the case for why a business might consider choosing Livewire–and why programmers might consider learning it.

Transcript

1. The Business Case for Livewire !
3. Oof.
4. Here's the message:
5. React won.
6. React won... sort of.
7. What metrics prove React won?
8. React won in the same way full-stack JavaScript won.
9. Just because a lot of people use something, it doesn't mean it's any good.
10. So, what metrics should we care about?
11. "The business case"
12. "The business case" "What toolset best enables businesses to accomplish their goals?"
13. The goal of any software company is to ship software to users.
14. So, how do we best enable developers to ship software to users?
15. Minimize friction from idea to deploy.
16. What usually causes friction? • Non-code processes
18. What coding issues usually cause friction? • Duplicated effort/code • Features split across multiple codebases • Complicated deploys • Multiple people required per feature
19. So, if we want to maximize business' ability to ship software, by minimizing friction...
21. Livewire: • One person... • writes one set of code for a feature... • in one codebase... • with one set of tests... • with one standardized deploy process.
22. Livewire makes shipping code easier.
23. Hiring? Easier.
24. Coding? Easier.
25. Testing? Easier.
26. Deploying? Easier.
27. However...
28. It Depends
29. Is Livewire the right answer for every project ever?
30. Is Livewire the right answer for every project ever? No.
33. So who is Livewire for?
34. Organizations who benefit from an individual or a small team being able to ship code.
35. So sure, there are more other businesses using (React, fullstack JavaScript, etc.)
36. "If you want to live like no one else..."
37. What are your goals, as a software business?
38. Want to ship? Livewire's got you covered.