How do RORe and Spree compare when it comes to updating an existing project? I’d imagine that would weigh in heavily when it comes to making a decision.
Daffy —
What do you mean by updating an existing project? if you need to keep history both are difficult. It’s just a difficult process. I do have experience with this…
drhenner —
I’ve already started to write my own webshop in rails
It is much more fun + now with Rails3 it is easier to write a webshop than to learn and bugfix/patch an existing one
However good luck for both teams
Cs —
WOW The lastest comment on my blog was a great example of a big code fight. OK maybe it’s just good talk but fight sounds better.
CS: if you just want a payment processor and a simple cart I agree it fun to do it yourself. If you want an admin/cart / shipments / fulfillment / inventory tracking / wish lists / save items for later / solr searching / paperclip/ an admin for adding products / tax calculations / shipping charges that change depending on location / performance / ok I will stop here… Doing it yourself might not be as fun. :) Of course I did it so I thought it was fun. =)
drhenner —
Sorry, to clarify, ‘by updating’ I mean if updates are required to the underlying ecom system to fix a bug, say, or patch a security hole. My understanding is that performing an update to a Rails engine would be easier, because your app uses it more like an interface, whereas with RoRe your code and the RoRe code are more tightly bound together. I could be totally misunderstanding things though, because I have next to experience with RoR ecommerce platforms, I’m just curious, so please correct me if wrong.
Daffy —
If there is a security patch I could refer to a specific commit SHA. It wouldn’t be as easy as an engine but not too difficult.
Comments
How do RORe and Spree compare when it comes to updating an existing project? I’d imagine that would weigh in heavily when it comes to making a decision.
What do you mean by updating an existing project? if you need to keep history both are difficult. It’s just a difficult process. I do have experience with this…
I’ve already started to write my own webshop in rails
It is much more fun + now with Rails3 it is easier to write a webshop than to learn and bugfix/patch an existing one
However good luck for both teams
WOW The lastest comment on my blog was a great example of a big code fight. OK maybe it’s just good talk but fight sounds better.
CS: if you just want a payment processor and a simple cart I agree it fun to do it yourself. If you want an admin/cart / shipments / fulfillment / inventory tracking / wish lists / save items for later / solr searching / paperclip/ an admin for adding products / tax calculations / shipping charges that change depending on location / performance / ok I will stop here… Doing it yourself might not be as fun. :) Of course I did it so I thought it was fun. =)
Sorry, to clarify, ‘by updating’ I mean if updates are required to the underlying ecom system to fix a bug, say, or patch a security hole. My understanding is that performing an update to a Rails engine would be easier, because your app uses it more like an interface, whereas with RoRe your code and the RoRe code are more tightly bound together. I could be totally misunderstanding things though, because I have next to experience with RoR ecommerce platforms, I’m just curious, so please correct me if wrong.
If there is a security patch I could refer to a specific commit SHA. It wouldn’t be as easy as an engine but not too difficult.
Post a comment