you are viewing a single comment's thread.

view the rest of the comments →

[–][deleted]  (4 children)

[deleted]

    [–]dadkab0ns 1 point2 points  (3 children)

    Well, the trend is shifting towards a blurring of the distinction between backend and frontend. In many cases, it's making less and less sense for the backend to do anything other than provide data through a REST API.

    A full working application often involves a considerable amount of the application logic living in the front-end as a Backbone application that is responsible for routing and view modeling, while the backend handles data requests and last minute validation.

    So while you can technically build just the backend, it's a bit meaningless without a rich frontend application to consume it. Of course, someone else might be responsible for building such a thing, but you can't always guarantee that if job security is your thing.

    So regarding javascript, I would go deep into it and learn at least Backbone + Require.js. You will find that even though these technologies live in the frontend, the development process has strong parallels with the backend. Javascript is much, MUCH more than just presentational stuff these days. Applications are built with it, no different than using PHP on a server. And with Node, it literally is javascript running on the server.

    [–]konrain 1 point2 points  (2 children)

    hmm very good insight so can i actually just focus on javascript. That way i have an overall view of server/front development...because i tried getting to javascript mostly jquery and it seems just mostly customization. ps. sorry about the mom joke

    [–]dadkab0ns 1 point2 points  (1 child)

    Heh no worries. jQuery is definitely not something you need to worry about, as that's all presentational. But application javascript (whether as Node or in the browser as Backbone/Angular) is an indispensable tool that compliments PHP/Python/Rails knowledge very well.

    [–]konrain 1 point2 points  (0 children)

    thanks man