I know its difficult to define or measure those things but it will get a helpful overview for my thesis. Thanks in advance for your Time! :)
Ask HN: Which JavaScript frameworks do you use?
1–10 of 71 posts
Re: Ask HN: Which JavaScript frameworks do you use?
#2jQuery: 1) 4 hours 2) 3 3) depending on code base, maintainability can be extremely easy but it can also be extremely spaghettti 4) cross-browser compatibility of client-side scripts that manipulate DOM
linked-in dust: 1) ~1 hour 2) 3 3) 3 4) cross-browser compatibility, small size, one of the fastest
jQuery-ui: 1) ~1 hour 2) 3 3) 3 4) cross-browser compatibility, granular control over what features I deploy
Re: Ask HN: Which JavaScript frameworks do you use?
#3Re: Ask HN: Which JavaScript frameworks do you use?
#41. It depends, you can make something quickly but when it comes debuging or make strange things you need a deep understanding of what is going on. I would say between 30 to 40 hours.
2. At first it's like 2.5, but when strange things start happening, it can slow to about 2.
3. I would say 2.4
4. It was really popular, has a lot of resources available and made development really easy.
Now for my personal projects I'm learning ReactJS
1. The framework is really easy, and it can take about 10 hours to learn it deeply. The difficult part is thinking the way they propose you with Flux. That can be as long as angular with 30 o 40 hours.
2. Productivity can be a little worse than angular with 2.0, but results are much better.
3. This is the best part. Although I haven't build a big project, at first sight it might seem this is the best part of react. I give it 3.0
4. Speed, control of what is going on in the views, popularity, the idea of having the possibility to easily port my apps to native with React Native, the tools such as browserify make even better.
I hope it helps you, sorry for my english.
Re: Ask HN: Which JavaScript frameworks do you use?
#5Re: Ask HN: Which JavaScript frameworks do you use?
#6Re: Ask HN: Which JavaScript frameworks do you use?
#7If I were you (and honestly I wish I was, I loved being a student) I'd focus much less on analyzing an arbitrary list of JS frameworks and instead turn my attention to questions like:
Why are there so many frameworks in the first place?
What problems are JS frameworks trying to solve?
Why does it seems like new frameworks are constantly being produced?
Why can't any single framework achieve critical mass?
You might learn some very interesting things about the web as a platform and JavaScript as a language.Re: Ask HN: Which JavaScript frameworks do you use?
#8Want a live binding, 2 way, super performant virtual DOM, that feels less like a framework and more like something that came with JavaScript?
var binding = new Ractive({
el: '.some-class',
template: 'Hi there {{ name }}
',
data: { name: 'Alex' }
})
It's created and maintained by The Guardian interactive team.## Time needed for Learning the Framework (in Hours)
The basics take 30 seconds because almost everyone is familiar with handlebars/mustache templates, but 4 hours total.
Eg, ractive has promises for when stuff changes, and you'll have to decide how to load templates (eg, ES6 template strings, or browserify fs). Once you've done that there's not a lot to learn, which is great.
## Overall Development Speed (0-3 Points, greater better)
Development speed: 3. It's insanely fast to work with because it's simple.
## Maintainability of the Code (0-3 Points, greater better)
Maintainability: 3. it's small, so super readable.
## Why did you choose that Framework?
All of the above, plus the support side. It's been around for two years and everyone I know who's used it loves it.
Re: Ask HN: Which JavaScript frameworks do you use?
#91. It took me month and documentation is sufficient well enough to learn it faster. (I'm slow at learning, of course learning speed is vary, depends on habit of people)
2. I would give point 3
3. also 3
4. reasons why I choose this framework are it's productivity, u will get good development habits, good patterns while using it and it's good ecosystem
sorry my bad english.