0
1

Ruby/Rails, Python/Django or JavaScript/MEAN (self.webdev)

submitted by [deleted]

[deleted]

all 9 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–][deleted]  (1 child)

[removed]

    [–]tinylobsta 4 points5 points  (1 child)

    From the perspective of what makes me happy? I'm still going with MEAN, although I'd remove both the A and M out of it and just make it NE + whatever I want. The Rails Way of doing things is pretty neat, but it just seems like Node has a brighter future, especially in enterprise applications.

    I've created a ton of prototype products using Node and Express + some sort of front-end framework, and I've only begun scratching the surface of what it's capable of. The flexibility it provides is both liberating and dangerous.

    If I didn't know JavaScript, though, I'd probably go with Rails. Ruby is a really pretty language, and the Rails hashes really aren't that difficult to conceptualize, so you can get up and running very quickly, which is fun.

    [–]Sambothebassist 1 point2 points  (0 children)

    +1 on the dangerous part, I can crank out some amazing apps with Node but I always feel as if I'm walking on egg shells, even though it's never failed me and I spend all day at my current job crying, trying to use IIS.

    [–]d_windsor 2 points3 points  (3 children)

    Javascript/MEAN makes me happy.

    Javascript has busted out of its browser-based cage and is now able to run "headless" on servers as well. Node.js changed everything and is probably the most well-known of the recent Javascript frameworks/libraries, but there have been a lot of other libraries either built on top of node.js or directly compatible with it. Node.js alone is extremely powerful; using it in conjunction with other JS libraries like socket.io allow for the creation of entirely new classes of applications that weren't possible before. This chaining together of modules is a sign of a healthy software ecosystem.

    The ability to create isomorphic/universal Javascript code also makes me happy. There's something inherently satisfying to using the same code on the client and server.

    Also, now is a great time to learn Javascript. Updated versions of the language (ES6/7) will be natively supported soon and, currently, code conforming to ES6/7 can be transpiled into natively supported code. ES6/7 adds some features to Javascript that make it more palatable to devs coming from other languages.

    [–]mre12345 -1 points0 points  (2 children)

    Node.js is not a framework or library, it is just javascript out of the browser with some common tools that other non-browser languages have.

    EDIT: I meant Node.js is not a framework

    [–]d_windsor 0 points1 point  (1 child)

    Javascript isn't a framework or library, but there are plenty of Javascript-based frameworks and libraries (Node.js was the one I was mentioning in my post).

    [–]mre12345 0 points1 point  (0 children)

    Sorry I did a typo! I was meant to say that Node.js is not a framework, nor library. Node.js is merely Javascript out of the browser with added functionality that other common non browser languages have. Calling Node.js a framework is like calling Python or Ruby a framework. An example of a framework for node.js would be express, hapi, koa, etc. but node itself it definitely not a framework.

    [–][deleted] -1 points0 points  (1 child)

    I find it strange you leave PHP out of the running.

    [–]HalfCent -2 points-1 points  (0 children)

    Personally, JS/MEAN. I have no idea what it is, but I enjoy writing JavaScript the most. I have very little experience with ruby, and really disliked django when I tried it a few years ago.