As one of the "how do I integrate this with Rails" folks, I really appreciate all of your efforts John. If there is a way that I can help with taking "examples" off of your plate as per Danny's suggestion, I'd like to help. I really like the idea of treating Ruote as a service rather than "integrating" it directly in the app.
Damon Torgerson 425.442.3925 On Sat, Nov 16, 2013 at 11:22 AM, Danny Fullerton <[email protected]>wrote: > On 13-11-16 06:28 AM, Mario Camou wrote: > > On 16 Nov 2013, at 09:26, John Mettraux <[email protected]> wrote: > > > >> On Sat, Nov 16, 2013 at 07:16:06AM +0100, Mario Camou wrote: > >>>> On Nov 15, 2013 11:27 PM, "John Mettraux" <[email protected]> > wrote: > >>>>> Ruote 3.0, if I manage to find the time to build it, will probably > not be a > >>>>> Ruby project, but it should be easily accessible, as a service, from > a Ruby application. > >>> That's interesting. Care to share your thoughts on why not Ruby, what > >>> language or sort of language you're thinking about and why? > >> Hello Mario, > >> > >> I went too wide with ruote 2.x, one "adapter" for any sort of storage > out > >> there. Ruote 3.0 will [perhaps] focus on FS storage. There'll be a set > of > >> "conventional datastructures" manipulated by the tools that'd make up > ruote > >> 3.0, whatever the language they're written in. > >> > >> I would stay away from Ruby to avoid any "hey I want to integrate that > into > >> my Rails project, where is the sample I can copy/paste?" hassle. > >> > >> I also thought that going for Ruby would allow people helping build the > >> system, but no, it didn't, so I'm free to build it in any language I > like. > >> What's important (you Madrid guys know it very well), is that other > systems > >> can talk to it. > > I completely agree with you. Elixir perhaps? Or Scala or Go :) > > > > I hope you get the time to do this! > Hello, > > I can't help but wonder how this would change anything. Ruote's users > gravitates around Ruby so I don't see how changing the language of > version 3 would fix this. Better to simply start a whole new project. > > Sure scaling down some features, reducing the codebase, etc can help but > I'm really not quite sure about the language thing... > > It's true we see a lot of inquiries about "how to integrate with Rails" > but that's probably because there's a need. What if `we` (Ruote's users > - not John) try to fix this: develop a project which helps integrating > Ruote with Rails (not Ruote in Rails) while keeping a clean demarcation > between both of them? It's precisely what I'm working on. Could that be > helpful? > > Too little to late? > > regards, > > -- > Danny Fullerton > Founder > Mantor Organization > > > -- -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en --- You received this message because you are subscribed to the Google Groups "ruote" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
