> This is depressingly similar
In graduate school, many a moon ago, my advisor would say that this is validation of the idea, so one should be happy to be on the right track.
Re:Lotus, a web framework for Ruby
by Eleopteryx on Monday June 23, 2014 @03:27PM
(#7933989)
Thanks for the de-demotivation.
I don't see it as such. I see it as "independently arriving at the same, correct solution." This is vision, not just skill. You don't see a lot of that. You probably just got distracted by another, harder problem once you realized you could see the end of the project.
Re:Lotus, a web framework for Ruby
by mattgreenrocks on Monday June 23, 2014 @04:37PM
(#7934482)
It isn't zero sum. There's still substantial design space to explore.
Lotus being received well just means people are ready for the idea. That may not have been the case in 2011, for instance.
Re:Lotus, a web framework for Ruby
by Eleopteryx on Monday June 23, 2014 @04:52PM
(#7934585)
I think I was misunderstood. By de-demotivation I meant re-motivation :)
Re:Lotus, a web framework for Ruby
by desireco42 on Monday June 23, 2014 @01:41PM
(#7933254)
Maybe you just found your kindred spirit and can join forces and produce something awesome for all of us
Re:Lotus, a web framework for Ruby
by Eleopteryx on Monday June 23, 2014 @01:43PM
(#7933268)
I'd be OK with that.
I seem to recall, a while back the creator of RVM suffered a similarly disheartening setback when rbenv came out. RVM is still going strong. The community has not decided on lightweight frameworks. The choices you make won't be the same as lotus. You will no doubt attract a group of like-minded people who will be grateful for your contributions.
Rails controllers are hard to test because actions aren't designed to be testable objects.
ActiveRecord models become monolithic because there's no separation of instantiation, validation, persistence, or retrieval.
I originally experimented with building a Rails app that forgoes ActiveRecord to a large extent; using plain Ruby classes + Virtus gem to separate the aforementioned concerns depending on context.
I was pretty satisfied with the number of design headaches I was able to avoid, which is when I started to create a framework around the aforementioned paradigms.
Not sure if I just lost my motivation or not, but I'm glad I'm not alone.