Why I’m thankful for JavaScript fatigue
JavaScript fatigue is an affliction that affects only those who's learning priorities are poorly chosen, such as framework-of-the-month.<p>This is why universities teach <i>computer science</i> rather than just programming. Learn about programming language <i>paradigms</i> - procedural, object-oriented, functional, etc; the language itself doesn't matter. Learn about relational databases. Distributed systems. Computer architecture. State machines. Formal grammars. Language translators/compilers. Data structures. Algorithms. Computational complexity/big O notation. That's the theory side of things.<p>Understand Unix, version control systems, and how to log into and administer remote systems. Learn about what TCP/IP is and how higher-level protocols like HTTP relate to it. Ensure you're able to write a program in at least one language that can talk to at least one type of database, and present at least some sort of user interface. That's the practice side of things.<p>These things will pretty much set you up for life. By themselves they're only a start, but you can pick up the rest as you go along, lazy evaluating any expertise you need with specific technologies as you go along.<p>As far as front-end web development is concerned, all you <i>really</i> need to know is JavaScript, HTML, CSS, and the DOM. Pick an abstraction layer on top of that <i>if you feel it helps you</i>, but don't feel that you need to know about every framework out there, because new ones are being generated faster than you can learn about them.<p>And yes, becoming good at this takes many years. But ensure that whenever you're investing time to learn, it's something that will last.