Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 4 years ago.
Improve this question
I just decide to learn backbone.js. I am a between junior and intermediate level front-end developer. my current job is dealing with html, css and jQuery. My boss asked me to learn this backbone.js and want to know how long it gonna take me to learn. so can anyone who experienced before tell me how long it gonna take?
thank you
If you don't know javascript, it will take awhile. I know this because I didn't really understand javascript when I got started with it. By know javascript, I mean being able to understand and fully explain:
Variable Scope
Object.prototype
.call, .apply, and .bind
Closures/Lexical Scope
Anonymous functions
Function Hoisting
If you don't know all that, get and read Crockford's Javascript: the Good Parts
If you do know all that, then you need to understand how to use Backbone properly otherwise it won't make any sense. When using Backbone, you really shouldn't have any non-backbone javascript outside of a sparse initialization of your base Views...also learning how to use the built in event binding is essential. This is a pretty good guide, as (obviously) are all the sources here
So I would say it could take a few days to a week or longer to fully comprehend whats going on, and much longer to get to the point of being very skilled with it.
I only just started with backbone as well and i must say it's pretty straight forward.
So assuming that you already have a thorough understanding of JavaScript it self, i think you can get started with it within 2-3 days ( with the right amount of dedication that is ).
If you are not yet very familiar with JavaScript, you have to make sure you get that down first.
Code school has an excellent high quality interactive tutorial that will give you a rocket start.
http://www.codeschool.com/
But there are plenty of free resources available as well, so don't let that stop you !
http://backbonetutorials.com/
The documentation on github is very complete, but it's probably not the best place to get started.
http://documentcloud.github.com/backbone/
If you are looking in to backbone you might also want to look into AMD with requireJS, that is a little more complex but definitely worth looking into at as well !
http://requirejs.org/
Related
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 1 year ago.
Improve this question
I've been assigned to a legacy project which runs on Ext JS 4.2. I know JavaScript but I'm totally unaware of Ext JS and I'm having trouble in understanding it. Can someone please guide me on how to learn Ext JS, what approach should be followed and the important topics to be covered? Or what sequence should be followed?
I have been using ExtJS (7.2.0) in a corporate project for six months, these are some tips I would have needed some time ago.
You should start from the official docs and examples given by Sencha:
guide --> the main topics are The Class Systems, MVC Application Architecture and Components, which are the basis of ExtJS;
examples --> I find the KitchenSink example very useful, since you can briefly overview all the components available in the system - you can also give a look to MVC examples, in order to see more complex architectures;
forum --> you can also check out the Sencha forum, which has many interesting topics (many more that you can find here on Stack Overflow).
Since you are using an older version of ExtJS, you will find many materials on the internet, because it was widely used several years ago, while now it is difficult to find updated sources.
You can check out Saki website or fiddle explorer sorting by created date ASC:
I used to be a trainer for Sencha, and I left the company in 2013 right around the time when ExtJS 4.2 was the main version.
The fastest way to get up to speed on the framework is to take a training class from Sencha. I haven't worked for Sencha for 8 years, and many of my colleagues (who I respected highly as trainers) aren't there any more, so this is not a plug for their services, but it's the fastest way. You will learn shortcuts that will take you much longer if you were to do it yourself. The framework is huge an complicated, and it's nice to get an overview of how it works from an experienced guide.
Before I was hired as a trainer, I took both the ExtJS and Sencha Touch classes that they had available, and the difference between the "before" and "after" in my understanding was huge. Yes, it's a week of your time, and yes, it's $2500, so your manager may not agree with my recommendation, but like I said, it's the fastest way to get up to speed.
If you do decide to take the class, spend some time with your legacy app and write down where you're getting stuck, and ask those questions in class. Part of the class value is that you can get some free light consulting for any issues you may be having.
The fact that you know Javascript is a big plus. I've had people in my classes who were new to Javascript, and that was another hurdle that they had to get over.
Good luck with your app!
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 2 years ago.
Improve this question
I know that for a simple static website, using plain HTML.. is the easiest and quickest way. But, what are some use cases between the two options? Is using a framework mostly the best solution?
You can basically see frameworks as pre-written structures for your App.
In other words, frameworks are meant to help you building applications quicker by addressing common development problems.
So, going back to your question, there are not really times where you would prefer vanilla javascript over frontend frameworks due to the incapacity of scaling well, which could result in inscrutable and unmaintainable spaghetti code.
Other bit you would want to consider about frameworks, is their high performance obtained thanks to their virtual DOM (abstract map of the real DOM), which helps handling events to update parts of the App without the need of re-rendering it.
On the other hand, I would suggest to go with a static website using pure HTML and Vanilla JS, only if learning / instructing someone, or if building something really really simple (but rest assure 99% of your commercial websites may suit better under a framework rather than without).
If you want to read more about it, I would suggest the following articles:
https://stackoverflow.blog/2020/02/03/is-it-time-for-a-front-end-framework/
https://gomakethings.com/why-do-people-choose-frameworks-over-vanilla-js/
https://www.freecodecamp.org/news/do-we-still-need-javascript-frameworks-42576735949b/
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 3 years ago.
Improve this question
I'm going to learn Clojurescript for building UIs and I want to use the React wrapper.Should I learn React before diving into Om?
Learn ClojureScript first, don't even think about React.
The learning curve for Om is not straightforward and you'll need to have a fairly grounded understanding of the fundamentals of the language before some of the abstractions that come with Om make sense (atoms, protocols etc). It's designed to be powerful, not simple and accessible.
Honestly, I'd try Re-agent first. The syntax for describing views is nice out-of-the-box and it'll also help solidify your understanding of atoms. If you like it, then you can complement it with Re-frame for a full blown FRP architecture.
I think it's easier to learn Om coming from Re-agent or Re-frame, than it is from React.
No, just dive into Om (or Reagent).
For 99% of UI concerns you won't need to know about the underlying React details, eventually for that 1% of cases you'll need to refer to the React docs.
I wouldn't worry too much about React. You can learn it through Reagent. Dive straight into Reagent by reading existing code. I started with the Flappy Bird demo and a few others.
To understand React you could look for uses of componentDidMount and the other component lifecycle methods. But honestly you only need to understand these methods for special use cases. Each item having to have a unique key is something that will trip you up, but only for legacy code as that requirement has been removed in the latest version of React.
You could also, even right from the beginning, be reading Om Next code and tutorials. You won't understand them fully right away, but keep having to go back to them. I believe that's the case for everyone!
How you approach it will also depend on whether you are a top-down or bottom-up learner. A bottom-up learner might be delighted to find out from one of the tutorials that queries have metadata linking them to components. On the other hand a top-down learner might be relieved to find a complete application to study. Here's my current best effort at a small Om Next application for understanding purposes.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 7 years ago.
Improve this question
I get it: the API is going to change, possibly in dramatic ways.
However, I make small apps for less than 10 customers each. I'm thinking that I can:
choose a specific version and stick with it
make lots of tests to check for compatibility with new releases
Also, given the projects are small, there's very little code to update when needed.
I realize that the Angular team is communicating the general readiness of their code in terms of availability for adoption from the general developer user-base.
I hear things like:
"Should You Use Angular 2.0 or 1.x?" =>
"The executive summary: There’s no Angular 2 to use, so Angular 1 is still the way to go."
And then I see videos showing how to use it. And I think to myself: with the above strategy of choosing a specific version & sticking with it + doing very careful updates to new releases, I don't see a very compelling reason not to. I mean, the only thing not to do would be not to go complaining to Angular whenever their changes inevitably break my code; it's expected. I'd be disappointed if it didn't break between now & then. That's part of the fun. Fix it and move on.
Concerns:
Security: the only real concern that gives me pause is that some security issue might be in play. But then, that's almost always the case. After all, it is the world of cyber insecurity.
Angular team can still make major changes in syntax and behaviour.
You can just try to use similiar approach with Angular 1.x, especially they introduced .component in Angular 1.5.
So just work with directives and components, after Angular 2.0 release migration should be fairly easy.
Closed. This question is opinion-based. It is not currently accepting answers.
Want to improve this question? Update the question so it can be answered with facts and citations by editing this post.
Closed 8 years ago.
Improve this question
I've been programming on and off for about 2 years now with python and C++, and a little bit of other languages like html, css, etc. I'm familiar with object oriented design and basic syntax of many languages. One that I've recently gotten into is javascript. About two months ago I heard about Angularjs and its capabilities. However, I've never done javascript at the time so I thought I'd give myself a few weeks to get familiar with javascript before I tackle Angularjs. A few weeks turned into 2 months and getting familiar is harder than I thought. However, I didn't want to stick to learning javascript forever, I wanted to move on the real goal and that is to learn Angularjs. So I started doing tutorials on Angularjs about a week ago. Now I'm stumped. It is very confusing to me. All the directives, MVC, controllers and such are so difficult for me to grasp. Experienced developers don't seem to have trouble picking up the framework, but I am so lost. I'm forcing myself to grind on it every single day until it makes sense but I'm rapidly loosing motivation because I don't understand most of it. Is this due to the fact that I still don't know enough javascript to grasp it? Will I have to learn more javascript to learn it? Frankly, I enjoyed javascript that's why I was able to keep doing it for 2 months. But my future for Angularjs is not looking very good and it has only been a week.
It would definitely help to understand vanilla JavaScript more as well as having a better idea of what is going on "behind the scenes" in a web app. If your knowledge is fuzzy and you don't understand vocabulary / concepts being used, you cannot assimilate new information about those concepts. Take your time, no need to rush. Read a book or some articles about MVC - get a good idea of what is happening all the way around. And don't limit yourself to Angular (great as it may be). Some light beginner reading
I would pick up some books on MVC. The more "big picture" understanding you have the easier it will be to implement in AngularJS. Check out Amazon for well reviewed books.