nice folks good, very good but => Stewart Mckinney can you explain below two sentences in more deep Please
Stick to Node.js for now, but I suggest learning Ruby at some point. It's > not going anywhere - it's certainly not the "Next Java". (cringe) I think > you will end up seeing them used more and more together than separately in > the future. Monoliths will die! On Sun, Aug 26, 2012 at 11:42 PM, Stewart Mckinney <[email protected]>wrote: > I wouldn't say you end up with "less useful" knowledge in Rails. There are > a lot of good patterns in the internals, which you will end up reading at > some point. The knowledge about Rails' conventions is somewhat situational > but even then you can apply similar concepts to Node applications , such as > having sensible directory structures that are "fractal" in nature. > > The MVC criticism is just - it is outdated and ham-fisted for the majority > of client side apps - but ultimately you will probably have one part of > your system that DOES conform to MVC weather you like it or not ( usually > your administrative section ), and this will happen no matter > which programming environment you use. Whether or not you deal with it at > that level of abstraction is entirely your choice. > > RoR also doesn't force a lot of the app to be on the server; that's > completely up to you. I'm just now finishing a project that uses Rails, > Backbone.js (a lot of code is there) and Node. Mostly Rails for the > administrative stuff, because its so much easier to make rapid changes with. > > Stick to Node.js for now, but I suggest learning Ruby at some point. It's > not going anywhere - it's certainly not the "Next Java". (cringe) I think > you will end up seeing them used more and more together than separately in > the future. Monoliths will die! > > > On Sun, Aug 26, 2012 at 1:56 PM, Mark Hahn <[email protected]> wrote: > >> You must be prepared for some hard work. The concepts needed to >> effectively use javascript for node can be complex, especially asynchronous >> callbacks and closures. >> >> I personally feel ROR is also hard and you end up with a lot less useful >> knowledge. ROR is limited to its MVC concept (which is outdated) and node >> allows you to use any model, now or in the future. ROR forces a lot of the >> app on the server where node can allow any mix of server and client code. >> My current app has more code in the client than in the server. >> >> >> On Sun, Aug 26, 2012 at 8:17 AM, ANIKET KADAM >> <[email protected]>wrote: >> >>> please people comment on this post so i can get more idea. >>> >>> >>> On Sun, Aug 26, 2012 at 8:45 PM, ANIKET KADAM <[email protected] >>> > wrote: >>> >>>> thanks all the people >>>> >>>> On Sun, Aug 26, 2012 at 8:42 PM, MikeB_2012 <[email protected]> wrote: >>>> >>>>> I'm coming from a decade plus of strictly programming in Matlab. I >>>>> spent a bit of time looking for a 'real', less expensive programming >>>>> language. Javascript isn't perfect but it is fast, readable, and gives >>>>> you >>>>> access to the modern world of programming (client-sever vice standalone >>>>> machine, browsers vice specialised gui's, emphasis on working with >>>>> text-based data vice pure number crunching). So I've gone with >>>>> javascript/nodejs/couchdb(via cradle). It isn't hard, there will be a lot >>>>> of slap-the-forehead (see a recent post of mine), but there is such a >>>>> wealth of possibilities all wrapped up in a single language that it's hard >>>>> to see why you wouldn't go with javascript/nodejs. >>>>> >>>>> >>>>> -- >>>>> Job Board: http://jobs.nodejs.org/ >>>>> Posting guidelines: >>>>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >>>>> You received this message because you are subscribed to the Google >>>>> Groups "nodejs" group. >>>>> To post to this group, send email to [email protected] >>>>> To unsubscribe from this group, send email to >>>>> [email protected] >>>>> For more options, visit this group at >>>>> http://groups.google.com/group/nodejs?hl=en?hl=en >>>>> >>>> >>>> >>> -- >>> Job Board: http://jobs.nodejs.org/ >>> Posting guidelines: >>> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >>> You received this message because you are subscribed to the Google >>> Groups "nodejs" group. >>> To post to this group, send email to [email protected] >>> To unsubscribe from this group, send email to >>> [email protected] >>> For more options, visit this group at >>> http://groups.google.com/group/nodejs?hl=en?hl=en >>> >> >> -- >> Job Board: http://jobs.nodejs.org/ >> Posting guidelines: >> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines >> You received this message because you are subscribed to the Google >> Groups "nodejs" group. >> To post to this group, send email to [email protected] >> To unsubscribe from this group, send email to >> [email protected] >> For more options, visit this group at >> http://groups.google.com/group/nodejs?hl=en?hl=en >> > > -- > Job Board: http://jobs.nodejs.org/ > Posting guidelines: > https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines > You received this message because you are subscribed to the Google > Groups "nodejs" group. > To post to this group, send email to [email protected] > To unsubscribe from this group, send email to > [email protected] > For more options, visit this group at > http://groups.google.com/group/nodejs?hl=en?hl=en > -- Job Board: http://jobs.nodejs.org/ Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines You received this message because you are subscribed to the Google Groups "nodejs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/nodejs?hl=en?hl=en
