W
W
wiygn2014-05-08 07:02:10
Frontend
wiygn, 2014-05-08 07:02:10

Front-end for a snake tamer?

Hello, there is one REST API written in Flask. There is also one back-end developer who wants to learn how to write front-ends in JS, I am currently finishing reading Flanagan. Some time ago I started reading about different frameworks and a number of questions arose:

  • I saw recommendations about Backbone.js, which, they say, is ideal for working with a REST backend. Is it so? Alternatives?
  • Does AngularJS really have a high threshold of entry and should not be taken on by a beginner?
  • When is it necessary, and whether it is necessary, to generate html on the server, and when on the client?
  • Are JS framework templating engines inferior in functionality to Jinja2? If there is someone kind, then briefly describe the differences between the frameworks (speed, readability of templates, custom filters and other features in a nutshell).
  • Is it worth it to take on this whole thing right away, or first write in pure JS + a little jQuery magic for academic purposes?

I'm completely confused in this numerous variety of frameworks. Thank you.

Answer the question

In order to leave comments, you need to log in

2 answer(s)
K
Konstantin Kitmanov, 2014-05-08
@wiygn

1. Ideal or not, but backbone is sharpened for REST. However, this is easy to change.
2. Can't say.
3. When speed and search engines are needed, then we render on the server.
4. twig.js , swig are just two of the jinja-like ones, there are more. Do not forget about other popular solutions - jade, doT, ejs, handlebars, etc. The speed and number of features varies. The most "featured" of those that work on the client is Jade.
5. Will not knowing the language interfere with you when you try to write things that are quite complex in architecture? See for yourself.

A
Alexey Yeletsky, 2014-05-08
@Tiendil

With REST, in my opinion, any adequate framework will work well.
I'm in favor of creating a maximum page on the server, unless a thick client is being written. There are the following reasons for this:
- page rendering is far from the most difficult operation, few people rest against it;
- easier testing - launched a view - got ready-made html, which can be run with a validator, and check for the presence of the necessary lines in it;
- easier debugging - no need to additionally run js-code (in the browser or somehow separately);
- It will be easier to do SEO.
> Is it worth it to take on the whole thing right away, or first write in pure JS + a little jQuery magic for academic purposes?
And what is the end goal. If you rivet sites of "medium" complexity, then jQuery is more than enough, and the experience gained will later allow you to make a more informed choice.

Didn't find what you were looking for?

Ask your question

Ask a Question

731 491 924 answers to any question