Hi guys, for about one and half a year I am involved in RoR Development. I like the framework very much! But more and more I have my doubts, that this framework will succeed, I think Ruby on Rails succeed only, if some powers from community will be concentrated on a target-oriented development of the Framework. Since the approach of a pragmatic way of programming isn''t new anymore, more and more frameworks come along with a similar aspect of application design. Check this out, http://5-0.dev.typo3.org/guide/index.html I find, that other frameworks are envolving more profound than rails does at the moment. The Dev Version of Typo3 is comming up with very estabilshed Components AND will catch up many people also with the built in CMS Functionality. I think there should really be a group as well, where some things should really be under one roof: Authorization Standard Localization Standard CMS Standard Extension- / Plugin- / Packageinterface I think i a longer term, RoR will have a chance if it will have some senseful application built on. Like a powerful CMS of DMS. What do you think? greetinx raf --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
On 30-sep-2007, at 1:08, Rafael wrote:> I like the framework very much!Good!> But more and more I have my doubts, that this framework will succeed,Well then you need to start liking something else.> I think Ruby on Rails succeed only, if some powers from community will > be concentrated on a target-oriented > development of the Framework.Some powers from the community are concentrated on building apps that work, not a frameworks-in-the-sky for making a CMS-that-does-everything-and-poorly-a-that> Check this out, http://5-0.dev.typo3.org/guide/index.htmlI''ve checked it out. It''s different. It''s a huge CMS with absurd system requirements. And I won''t be compiling PHP6 because I''ve had enough of PHP compilation tragedies in my former life.> I think i a longer term, RoR will have a chance if it will have some > senseful application built on.Rails has senseful appliactions built _on_, but has no applications built _in_. It''s intentional.> Like a powerful CMS of DMS.Youa are totally free to help with the development of Radiant. Or auto-admin. Or ActiveScaffold.> > What do you think?I think you should go Django if the "CMS-y preimplemented-ly componentized" is your kind of thing. -- Julian ''Julik'' Tarkhanov please send all personal mail to me at julik.nl --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---
I think you get the point of Ruby on Rails totally wrong. Ruby on Rails is no CMS like Typo3, thats something fundamental different. You cannot compare it, its a framework, a base to build web applications and services. And its becoming a plain core even more (many things have been removed and stuffed into plugins lately). And thats the best thing for me in Rails, it does not go into one direction, you''re free to do everything, make a CMS or just some application. And its even getting cooler every day, rails beeing the core enables the development of extensions like Hobo (www.hobocentral.net) which I personally would call the best framework to develop very fast and very Dry applications, based on rails. I have comparisions like that, if you want to compare it to typo, look at how easy it is to build your own cms (eg. in Hobo), or use one of the many existing publishing applications based on rails (see http://www.railsbased.org for a small list). And if you don''t the way these apps work, you can use them as a base, and extend them in no time. So please, let rails be a core framework, nothing more. It does not need CMS functionality and fu, modularity is the real benefit.>> Authorization Standard >> Localization Standard >> CMS Standard >> Extension- / Plugin- / Packageinterfaceall those points are already existing? But I''ll repeat that again, its totally wrong to put this into the core. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to rubyonrails-talk-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-talk-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en -~----------~----~----~----~------~----~------~--~---