News for hackers. Stuff that matters.
Re:Need for Speed: How Groupon Migrated to Node.js by tangue on Sunday December 08, 2013 @09:49AM (#6869802)
"To change one color throughout the entire Groupon.com webpage, that was estimated to take three months to do". ... It seems that they rewrite from scratch a terrible mess, the switch to Node is anecdotical
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by mcmillion on Sunday December 08, 2013 @10:24AM (#6869904)
Agreed. Incoming Rails vs. Node flame war aside, if it takes you 3 months to make trivial changes, you're doing something very wrong, or your development process is completely broken.
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by schneid on Sunday December 08, 2013 @12:52PM (#6870442)
On the plus side, making trivial changes now only takes a week!

"It took three months just to change the color appearing across the website, he said. “After we moved to Node.js, it took us literally a week.”" - http://www.datacenterknowledge.com/archives/2013/12/04/paypa...

[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by mcmillion on Monday December 09, 2013 @01:33PM (#6875834)
I don't even have words to say to that. Just wow.
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by tmikaeld on Sunday December 08, 2013 @10:22AM (#6869895)
The first Node.js dismissal, as expected.
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by camus2 on Sunday December 08, 2013 @12:38PM (#6870379)
Like it or not , NodeJs is here to stay.

The problem is devs using it for every use cases,even when it doesnt make sense, just like rails.

Of course,in a few years you'll read articles about how bad node is, just because developpers did not choose the right tool for the job.

[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by tangue on Monday December 09, 2013 @09:58AM (#6874543)
The only thing I'm dismissing here is Groupon's codebase. (BTW I'm impressed by Meteor and Derby)
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by mcmillion on Sunday December 08, 2013 @10:40AM (#6869957)
That's not a dismissal of Node, it's a dismissal of Rails as the reason for their problems.
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by ForHackernews on Sunday December 08, 2013 @12:18PM (#6870288)
Groupon hasn't gone bankrupt yet?
[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by allsystemsgo on Sunday December 08, 2013 @12:32PM (#6870348)
Groupon is awfully run. I ordered some pants for my wife two weeks ago. They literally just shipped. I have no idea when they'll arrive.

Their app is shit and it always has been. It's painfully slow.

Their products are usually not good. I rarely can trust that a thumbnail represents exactly what I'll be buying.

[ Parent | on HN ]
Re:Need for Speed: How Groupon Migrated to Node.js by nakkiel on Sunday December 08, 2013 @12:17PM (#6870279)
This is not a serious article at all. There's essentially not content. It deserves downvotes.
[ Parent | on HN ]