Lotus, a web framework for Ruby
lucaguidi.com
Lotus, a web framework for Ruby
1–10 of 143 posts
Re: Lotus, a web framework for Ruby
#2Thank for great fw.
I'm by no mean a Ruby expert but finding Sinatra is so simple to create complex apps, and Rails is so complex atm to pick up. I'm making slowly progress in Rails and always not sure if I done thing correctly in Rails way.
Lotus seems small enough, and good enouh, balance between Sinatra and Rails for me.
Keep up the good work. Thanks.
Re: Lotus, a web framework for Ruby
#3Whenever I hear lightweight and complete, I always wonder if they handle one of the hardest things to do cleanly in web-apps: user authentication and access control of resources. Does Lotus support this out of the box?
Re: Lotus, a web framework for Ruby
#4I'm intrigued. Just signed up for the mailing list. Do you have any links to applications built in Lotus?
Re: Lotus, a web framework for Ruby
#5This is an interesting attempt. It has Sinatra like simplicity, providing the modular architecture that was promised with the Merb + Rails merger.
At the very least, this will spark some interesting conversations and ideas.
Re: Lotus, a web framework for Ruby
#6This is depressingly similar to what I was aiming for when I recently began work on: https://github.com/lean-framework/lean (I feel like this happens to me a lot.)
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.
Re: Lotus, a web framework for Ruby
#7This is depressingly similar to what I was aiming for when I recently began work on: https://github.com/lean-framework/lean (I feel like this happens to me a lot.) 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…
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
#8This is depressingly similar to what I was aiming for when I recently began work on: https://github.com/lean-framework/lean (I feel like this happens to me a lot.) 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…
Maybe you just found your kindred spirit and can join forces and produce something awesome for all of us
I'd be OK with that.
Re: Lotus, a web framework for Ruby
#9I'm intrigued. Just signed up for the mailing list. Do you have any links to applications built in Lotus?
Here is a simple gist from Lotus author: https://gist.github.com/jodosha/9830002
And also there is a WIP room reservation app: https://github.com/sidonath/room-reservation
Re: Lotus, a web framework for Ruby
#10Whenever I hear lightweight and complete, I always wonder if they handle one of the hardest things to do cleanly in web-apps: user authentication and access control of resources. Does Lotus support this out of the box?
A quick look at the API[1] showed a couple mentions of Sessions in the example structure. Not sure if it is handled out of the box, but I get the impression it is not difficult to implement. But that is just authentication, no idea about access control.