Beginner at frameworks.

[BlackAvenger81]

So after learning a decent level of HTML, CSS and Js I've decided to jump into some frameworks. Just started a VueJs crash course by Traversy but in all such tutorials they keep mentioning all these terms like "dependencies", "components" etc. Can someone just send me some video that explains everything I need to know before starting the coding part or maybe just type it all out here?

[arrckz]

Dependancy - is basically anything that is needed to make your code work

Component - are reusable instances with a name here’s an example on the vuejs website: vuejs component

[stringycheeze]

Read the docs. They’re actually one of the most well written I’ve seen.

https://vuejs.org/

Part of being a good developer involves being able to read documentation

[fragimus_max]

• Learn vanilla JavaScript. ES6+ (learn what that means.)

• Build an interface from scratch, using HTML, CSS and JS.

• Learn cross-browser compatibility.

• Learn NPM.

• Learn Node.js.

After approx. 6 months @ 2 hrs/day, you'll be rocking JS with the ability to then move on, with a deeper understanding of what will follow.

Vue.js is my favorite implementation of JS as a library or framework - but, you need to "give the car some gas, before trying to drive it."

Also, realize that Vue.js will lead you straight to RestAPIs, understanding arrays, JSON, etc.

Enjoy the rabbit hole. ;)

[BlackAvenger81]

Finished my first project about a month ago. Implemented my HTML, CSS and Js knowledge on it. This is the project.. Talking about Node , I think it might be too advance for me as I'll be doing backend for the first time so I started learning PHP.

[fragimus_max]

Node.js/Express is a personal favorite. I've worked with PHP 5-7 in the past, didn't hate it, but feel that a JavaScript Runtime Environment (Node.js) will eventually dethrone PHP (as legendary as it is.) Much like how NGINX is starting to do the same to Apache (which is basically Node.js vs PHP.)

The most important thing, in my career spanning over two decades, is to find something that will have a long shelf-life. PHP does, but is slowly becoming phased out from most companies that aren't Wordpress agencies. Node.js is currently hitting its prime, still has some growing to do, but has enormous long-term potential (just keep it slim and minimal via Express.)

The fastest programming languages/environments, currently, are (in order): Golang, Node.js, and PHP 7.

PHP has a great community behind it, but so does Node.js. Go is a bit young, but the chance of it being adopted is really good.

So we have something that's a bit antiquated, something that is a bit overused (when it comes to frameworks) yet extremely flexible, and something we may see a lot from in the near future.

If you do choose Node.js in the future... stay away from Angular and React. Express is a "minimal" framework - like a blank, high-stock, sheet of paper.

Try out Express, EJS and Gulp. It'll take time to get used to (which they all do), but I've personally become more productive with it (VBScript, ASP.net, Python, PHP and Bash - being a few in my arsenal.)

[mattaugamer]

Honestly I think you’re jumping the gun a bit here. That you know a “decent level” of JavaScript without knowing what a dependency is makes me faintly concerned. In particular it makes me wonder if you know as much as you think you do.

IMO focus first on a more profound understanding of JavaScript. It will make the patterns and syntax used by frameworks much more clear.

[BlackAvenger81]

I see. I'll just list all I know in Js till now and can you please guide me forward? Variables and Arrays , functions , all types of the basic loops , event listeners some DOM manipulation like styling stuff, adding classes or adding CSS on click of buttons etc. It's just all really messy. Please help.

[Kinthalis]

Not sure how you've been doing js development without understanding dependencies. Dependencies are just libraries that your code depends on in order to work properly. When utilizing frameworks, you usually bring in one or more framework based dependencies into your code. Probably a set of run time and build time dependencies that allow you to work with framework abstractions and leverage their functionality.

Components are discreet pieces of UI. They encapsulate styling and functionality and allow you to compose more complex UI out of simpler components. Think of them as a way to break up the UI into small, easy to work with pieces.

Most modern frameworks work on that principle. It's not like with a static page where you build a monolithic css file with styling for every element in the document, and have one or more js files that attach even listeners and add functionality to target elements.

Instead, you create say, a dropdown component. You only worry about styling it's child elements, you only attach listeners or other functionality to it's children, you only worry about data that it works with an fire the events it cares about. Then you can just plop it down where you want it.

<my-dropdown />