We actually need more JavaScript frameworks

It’s easy to become overwhelmed by the growing number of JavaScript frameworks available today. Believe me, I was. And so I built a tool to help developers choose which JavaScript framework to choose. But it was rubbish.

Join me as I share my weird and winding journey through the JavaScript framework landscape. Starting with an overcooked meme, to building a terrible website, and finishing with a call to action, we’ll delve into the lessons I learned along the way, including the importance of asking the right questions about your project before choosing a tech stack and framework.

Transcript

1. WE ACTUALLY NEED MORE JAVASCRIPT FRAMEWORKS SALMA ALAM-NAYLOR @WHITEP4NTH3R
5. ME, AND YOU CAN QUOTE ME ON THAT “WE ACTUALLY NEED MORE JAVASCRIPT FRAMEWORKS.”
6. SALMA ALAM-NAYLOR I WRITE CODE FOR YOUR ENTERTAINMENT
7. SALMA ALAM-NAYLOR I’M GOING TO TAKE YOU ON A JOURNEY
8. WHY I CHANGED MY MIND
9. LOTS OF PEOPLE, ALL OVER THE INTERNET “WHAT JAVASCRIPT FRAMEWORK SHOULD I USE?”
11. 2 QUESTIONS
12. 1 QUESTION
17. 2 QUESTION
20. 👍 SIMPLE
21. 👎 NOT SIMPLE
22. 23 JAVASCRIPT FRAMEWORKS
24. 👍 PLENTY
25. 👎 NOT PLENTY
27. 🚫 🚫
30. 🚫
32. NOT ENOUGH OPTIONS
35. 🌶 SPICY
36. RYAN CARNIATO, CREATOR OF SOLIDJS “WE NEED NEW FRAMEWORKS. WE NEED INNOVATION RIGHT NOW.”
37. THE CIRCLE OF LIFE
43. SERVER
44. SERVER CLIENT
45. CLIENT SERVER (AGAIN) SERVER
46. CHOICES
47. MEANINGFUL QUESTIONS
49. ❌
50. “WE ACTUALLY NEED MORE JAVASCRIPT FRAMEWORKS.” SALMA ALAM-NAYLOR