11 comments

[ 2.6 ms ] story [ 39.6 ms ] thread
"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
The first Node.js dismissal, as expected.
That's not a dismissal of Node, it's a dismissal of Rails as the reason for their problems.
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.

The only thing I'm dismissing here is Groupon's codebase. (BTW I'm impressed by Meteor and Derby)
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.
This is not a serious article at all. There's essentially not content. It deserves downvotes.
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.