How to choose the right javascript structure and how to get started?

Question

my first post on the stack, so I'm thrilled for every answer.

I have a really big problem in choosing the right javascript structure. Just some personal information, I know the basics of javaScript, I can write jQuery and, of course, I know HTML5 and CSS3. But I want to switch to server applications, like many others, I think. Since then I have been reading months on the Internet about all the different frameworks, but it is so hard to solve for one.

A few days ago, I started using angularJs, but for some reason I really did not understand this, because it goes deeper, because I really do not understand the documentation, and as far as I looked, there are not so many videos there. I can study better with the video.

Then I switched to meteor.js, but their documentation is even more complicated, and there are also not many videos there. Reading about the meteor, I headed to node.js because it was said that it is easier to understand if I understand node.js. But until I understand node.js, a lot of time is lost. I know that I need to learn this, but I just want to start with a client-side framework that connects easily to node.js.

My main intention at the moment is to start with a real basic todo application, just for myself, to learn it and maybe add more and more functions later. Someday I want to continue and try another application, another, etc. This is a long way. But I can’t choose a framework for it. I want something that is quite open for different use cases, let it be a small or large application. Just in case for the future. But basically, when I read about structure, they also say something about commonJS, underscore.js, etc., and it just bothers me because I always think I need to learn all this.

So what's the best way to get started? Should I go back to Angular and try again? Should I just try to write it myself and study the documents when I need something, or read the full document first? Same for the meteor. And I also have the spine always in my mind, if it can be better. This area is so stunning to get started, so what's your experience? How did you get started and what is the best way? I do not want to lose more time for meaningless reading without a solution.

Thank you so much for your help.

Answer 1

Choosing a JavaScript framework is not an easy task - there are a lot of them, and they vary significantly in quality, characteristics and maturity. I would recommend visiting the TodoMVC site, which demonstrates the same applications - a simple to-do list implemented with various different frames.

He offers the following recommendations on how to make the right choice:

After you have downloaded the latest version and applications, you will want to decide on a specific structure to try.

Learn the syntax you need to define models, views, and (where applicable) controllers and classes within the framework you are interested in and try your hand at editing code to find out how to do this. Feels like using it first hand.

Please make sure that if you are satisfied with this, you spend more time (including reading official documents, the source and its full list of functions). There is often much more than we imagine in our examples.

Answer 2

I was also embarrassed when I started AngularJS (not that I am an expert now), but after a while you will get it, and about the videos that I found, these links and those helped me a lot:

• egghead.io
• AngularJS Angle Channel

I hope for this help.

Answer 3

I put node.js through its balls right now, without using any of the frameworks. I am ignoring the framework right now because I want to work out what I can and cannot do with just node.js. So far, I got node.js to respond with a hello expression, a JSON expression, the contents of a text file, including a rendered HTML file, the next one on the list is an entry from the Mongodb database. I also broke the HTML page into a header file, a body file and a footer file, and I used the promises from the q.js library to display the entire HTML page of the file as a whole. Due to the need, I treat all HTML pages as dynamic, but I am learning to render static pages.

I also used node.js with SSL the day before yesterday, I developed how to export node.js to heroku, and I need to implement a redirect from http to https.

As soon as I comfortably, if not completely - completely, may be redundant - familiar with node.js without frameworks, I will add frameworks such as express.js and socket.io one at a time and see what I can do with each of them separately. I believe this onion-based disposable approach is the most reliable and least time-consuming way to master node.js with a reasonable level of confidence. And this approach is realistic in its feasibility, because we are talking about three or four frames.

I am surprised that you never learned bootstrap.js in the interface - at the moment I can make bootstrap.js in a dream - and you never looked into AJAX calls that allow asynchronous communication with the back end.