I’ve read everything I can read about rails engine. I think I have a
fair amount of idea of what it does, but I still can’t draw my
conclusion whether it’s safe to use the rails engine.
Like everyone else, I’m planning to create the next big thing
(myspace2, or youtube2). just for pete’s sake, say this next big thing
will do everything under the sky, social networking, photo sharing,
blogging, wiki, etc. I can program it in 1 of 3 ways:
- giant rails app does everything.
- use rails engine, so social net, photo, blogging, each will be an
engine. so 1 app, multi engines.
- create separate rails app for each, so if i want social net, photo
share, blog, then that’s 3 rails app. and use one central logging
system like how google account works.
as I’ve read, rails engine is fairly new and changing, so is rails. So
if I choose the rails engine road, will my app work down the road? eg,
like when rails 1.2 comes out? I’m in no position to debug either rails
or engine’s internal.
which way would you do?
thanks.
WuyaSea O. wrote:
- use rails engine, so social net, photo, blogging, each will be an
which way would you do?
thanks.
lol. LMfAO this is hilarous.
tells us how much u kno
On 11/11/06, jo [email protected] wrote:
WuyaSea O. wrote:
as I’ve read, rails engine is fairly new and changing, so is rails. So
if I choose the rails engine road, will my app work down the road? eg,
like when rails 1.2 comes out? I’m in no position to debug either rails
or engine’s internal.
lol. LMfAO this is hilarous.
tells us how much u kno
wow, jo. real constructive. instead of mocking, why don’t you help by
giving him a tip? and if you don’t want to give a tip point him
towards a link, or even keywords he can use in google.
–
Austin G.
Thinking & Making: IA, UX, and IxD
http://thinkingandmaking.com
[email protected]
jo wrote:
lol. LMfAO this is hilarous.
tells us how much u kno
I have just one question for you, Jo. Do you, by chance, spend all
your time in your parents’ basement playing online games, except when
you’re grounded?
Why do I ask? No reason.
- giant rails app does everything.
- use rails engine, so social net, photo, blogging, each will be an
engine. so 1 app, multi engines.
- create separate rails app for each, so if i want social net, photo
share, blog, then that’s 3 rails app. and use one central logging
system like how google account works.
Meanwhile - to address the actual question, while engines might not
always be such a great way to distribute general purpose code, they
seem to be to be a perfectly good way to create vertical slices in a
special purpose app, as in 2. above.
Anyone have any (constructive, helpful) thoughts?
=vg
I like em
But im interested in what all the concern is about their use
I haven’t used engines myself, but to decide between 1 and 3 would,
imho, depend on how interconnected you want your various pieces to be.
Google’s applications are fairly decoupled and handled by different
teams of developers. Each team simply needs to know how to utilize the
central log-in API.
Myspace, on the other hand, is very interconnected: blogs are tied to
profiles which can be tied together in groups, events, etc. With so
many touch-points, it makes more sense to handle them under one
application roof.
And then there’s everything in between.
Good luck!
DHH isn’t (or wasn’t?) a big fan of engines:
http://weblog.rubyonrails.com/2005/11/11/why-engines-and-components-are-not-evil-but-distracting/
Also the core team doesn’t seem to worry much about breaking them since
they
use non-public Rails API methods.
To the OP I think the 3rd option is your best bet. The functionality
you
describe is easily categorized into separate web applications.
On 11/11/06, Clayton C. [email protected] wrote:
[mailto:[email protected]] On Behalf Of Victor G.
system like how google account works.
–
Posted via http://www.ruby-forum.com/.
–
Thanks,
-Steve
http://www.stevelongdo.com
with all your comments, i’m more leaning towards the 3rd option now.
thanks all.