jenso

Joined 13 years ago

Karma

Submissions

Member since

Feb 11

Recent submissions

First of all, I wouldn't call Backbone a framework. It's more like a library. It's only about 1500 lines of code with lot's of comments.

If you use Backbone, you'll have to reimplement/include other libraries to use the right design-patterns. And this takes time. AngularJS and Ember.js makes these decisions for you which saves alot of time.

Comment · 13 years ago

- If you're building a new web app today, which frameworks, platforms, technologies, etc. would you use? why?

Backend:

NodeJS - It's nice to have javascript on both the frontend and backend. And NodeJS is FAST.

MongoDB + PostgresSQL - MongoDB for stuff that needs to be fast / fast to build. PostgresSQL for stuff that doesnt fit the document model.

Frontend:

AngularJS - It's either AngularJS or Ember.js, I prefer AngularJS. http://stackoverflow.com/questions/14395887/what-are-benefit...

Yeoman - Generate boilerplate code

Grunt - Compile LESS, Run tests, CSS minification

Bower - Javascript dependencies management

- Would you choose a familiar framework that allows you to develop faster (because you're comfortable with it) even though it's not necessarily 100% 'right' for the job?

I'd rather choose a new framework, at least if it's a project that I will put serious effort into.

- Would you push your own limit and think outside the box to find a better solution even though introducing new technology to the team could be costly (and possibly unpopular)?

Yes, I would definitely do it.

That's actually what I'm currently doing at a startup. We're refactoring the current frontend-javascript codebase which is 30 000 lines of code and it's completely unmaintainable, so we're rewriting it in AngularJS