4 ms·
Skip the frameworks, start with modern ES5/ES6, don't use babel/ts/etc initially. Modern JS is pretty clean and the native DOM methods are actually very pleasa
by vorpalhex 6y ago
Skip the frameworks, start with modern ES5/ES6, don't use babel/ts/etc initially.
Modern JS is pretty clean and the native DOM methods are actually very pleasant generally. You can get really far without even needing a package manager, but eventually something like npm becomes useful if bulky.
- hfourm 6y agoFurther, you will then understand why you need a framework like React should your project become complicated enough on the frontend.
- bob1029 6y agoThere's nothing stopping you from tracking client state in a a simple window.state object. This object can be of arbitrary composition, so I see no reason you cannot manage even the most complex UI state in this manner. For me, minimal web development means doing as much as I can at the server. This includes tracking client UI state if feasible. The more stuff you have in 1 domain like that the easier it becomes to control complexity. When your state machine is split between 2 realms is when you get into traps that things like React were created to resolve.
- twicetwice 6y agoI agree that if you have state in two places you're doing it wrong. That's why I keep all my state client-side (the only thing in session storage is your user ID if logged in). My server is basically just a thin wrapper around my database, providing an API for my client to call.
- pvorb 6y agoThe problem is there aren't many guides for learning "vanilla" JavaScript that aim at newcomers. MDN is a good reference, but I can't think of something more directed tutorial.
- lambertsimnel 6y agoIf you're interested in learning vanilla JavaScript through an online course, you might like to try Execute Program: https://www.executeprogram.com/ https://www.executeprogram.com/ I found it more thorough and challenging than others I've tried, but it doesn't assume any knowledge of JavaScript.
- TurkishPoptart 6y agoI have a question about an embarrassingly simple problem: "Element Access". Is there a way I could contact you about it?
- divbzero 6y agoIf by “Element Access” you mean getting pointers to DOM elements, try querySelector [1] or querySelectorAll [2]: var element = document.querySelector(...) var elements = document.querySelectorAll(...) [1]: https://devdocs.io/dom/document/queryselector https://devdocs.io/dom/document/queryselector [2]: https://devdocs.io/dom/document/queryselectorall https://devdocs.io/dom/document/queryselectorall
- lambertsimnel 6y agoFeel free to email me. My Gmail address is "parodieslost". Although I'm not affiliated with Execute Program, I have done the JavaScript Arrays course (including Element Access), and I'd be interested in your problem.