5 ms·

I like that Trailblazer is promoting some concepts I'd like to see more rails devs use (service objects, form objects), I think this project will be a non-start

by d4mi3n 12y ago

I like that Trailblazer is promoting some concepts I'd like to see more rails devs use (service objects, form objects), I think this project will be a non-starter for most teams. But after giving the readme a once over and looking at the source code a bit, here are the concerns I would raise: 1. What advantage does this have over using the components it's wrapping? Why not just use the reform or representable gems directly? 2. Things like this introduce a steeper learning curve for newer rails devs, especially when they cause application architecture to deviate so much from what's commonly found in the documentation already available. 3. There seems to be no real documentation on what testing facilities are available for this framework. That being said, this is not bad at all for a pre 1.0 release. I don't always agree with some of the decisions apotonick (the author) in the code he publishes, but I do respect him for the fact that his work promotes a lot of discussion in the ruby/rails ecosystem.

markburns 12y ago
I've not used trailblazer myself but I've utilised some of the concepts or similar ones on existing projects and green field projects. I think the answer to 1. would be hard to express without getting deep into a specific complex application and most people don't want to open source their business applications, especially not as an example of bad code. It would be awesome if someone refactored a typical problematic large Rails app in the open using these concepts. But it's a lot of work/risk just for the greater good. 2. I'd suggest that the newer devs are going to find it easier navigating a clean codebase (with architectural complexity) than a well established Rails app with a lot of the code smells and complexity that come with going The Rails Way.
mattmcknight 12y ago
What advantage is there to form objects?
skratlo 12y ago
Yeah boy, that's the spirit! Everything is an object! As in... ummm, kingdom of nouns, yeah that one.

by d4mi3n 12y ago

markburns 12y ago

I've not used trailblazer myself but I've utilised some of the concepts or similar ones on existing projects and green field projects. I think the answer to 1. would be hard to express without getting deep into a specific complex application and most people don't want to open source their business applications, especially not as an example of bad code. It would be awesome if someone refactored a typical problematic large Rails app in the open using these concepts. But it's a lot of work/risk just for the greater good. 2. I'd suggest that the newer devs are going to find it easier navigating a clean codebase (with architectural complexity) than a well established Rails app with a lot of the code smells and complexity that come with going The Rails Way.

mattmcknight 12y ago

What advantage is there to form objects?

skratlo 12y ago

Yeah boy, that's the spirit! Everything is an object! As in... ummm, kingdom of nouns, yeah that one.