everyauth

uchi's everyauth [1]. There are 163 issues open, and all recent ones have no trace of comments from Brian (sign 1). One of these issues is mine. The example code in the repository is broken, and one of the OAuth modules has a showstopper bug (sign 2)[2]. Brian's Github activity shows he is working on the admittedly more important derby.js project (sign 3)[3]. I am not focusing on Brian because I want to shame him, but everyauth is a good example of an abandoned project, and all of its users should pack up and move on. [1] https://github.com/bnoguchi/everyauth [2] https://github.com/bnoguchi/everyauth/pull/367 [3] https://github.com/bnoguchi?tab=activity

in't easy, but someone has to do it. There are some great concepts like http://nowjs.com/ but I guess the status quo of JavaScript is not there yet. We need ES5+ in the browser to do the really good stuff. Strong, responsive and enthusiastic community Big part of the community is great! Some really brilliant minds out there! But there is also a part of not so skilled dudes who hated rails and now just hopping on the node bandwagon for the wrong reasons (and leaving behind a trail of unmaintained github repos w/o tests). Large productivity gains in HTML & CSS using Jade & Stylus Well, switching from HTML/CSS to HAML/SASS was a large productivity gain. Switching to Jade and Stylus was just felt "ok". The real performance boost at SASS dev came from Compass, which didn't existed for Stylus for a long time. Now there is Nib http://visionmedia.github.com/nib/ but it's still a pretty young project compared to Compass. Btw: For those who do a lot of Rails + Node.js development check out https://github.com/9elements/haml-coffee it's HAML married with CoffeeScript. Performance and scalability I buy the performance, kudos to the V8 team and @ryah. But scalability does not come from using a certain tech (unless it embraces scalability per default). Scalability comes from crafting a system that has no single point of failure (http://en.wikipedia.org/wiki/Single_Point_of_Failure). So please don't compare apples to pines. Wealth of hosting options: No.de, Joyent’s SmartMachine, Heroku, Nodejitsu True, I would just add homebrew hosting and deployment with capistrano and forever: https://github.com/nodejitsu/forever Make your developers famous Don't be foolish. Doing Open Source (right) is one of the hardest disciplines out there. Just releasing some written code into a new ecosystem does not automatically uplift you to the rockstar developer olymp. You have to maintain your code, deal with issues, deliver support etc... Doing Open Source work is very important. You take - you give - but more important you'll learn. But you don't need node for that there is plenty of room in this Internetz thingy, look at https://github.com/codejoust/session.js Developer happiness I know the feeling: Staying on the bleeding edge looking into the space where no man has gone before feels great. But be carefull, if things don't go well they can easily switch to developer tears. It almost took the node ecosystem a year to mimic typical "getting things done modules" like EveryAuth https://github.com/bnoguchi/everyauth which derives from https://github.com/intridea/omniauth/ in the rails world. OH: If you seeking for something like rails in the node.js world... then just use rails. Bottom Line When you read this you may get the feeling that I don't like node - I'm loving node http://node.9elements.com/ and it definitely has it's use cases: - if you do something in realtime - if you are developing an API - if you need high performance but for other use cases I wouldn't bet my life on it... yet. If you're interested in node, then go for it, play with it, never stop exploring - start small and grow with the ecosystem. One day it may replaces technology X with framework Y, but until then I would lower my expectations a little. So... enough ranting, let's engage the discussion - I hope you enjoyed this article: http://twitter.com/sippndipp