Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Lotus, a web framework for Ruby

lucaguidi.com

Post reply on HN
Print view View original

111–120 of 143 posts

Re: Lotus, a web framework for Ruby

#111

Post by Rapzid »

thecoffman wrote: post #21
jaredcwhite wrote: post #12

I'm all for new frameworks that emphasize different ideas and philosophies. If nobody ever tried experimenting with a new approach, we wouldn't have Rails in the first place. So kudos to Luca and his fine work in developing Lotus. I like much of what I see. That being said, I feel like YARWF (Yet Another Ruby Web Framework) is not the most pressing matter in the web space today, and I take exception to the notion tha…

>A complete web framework has client-side components that facilitate two-way communication to/from the server, data binding, HTML5 history state-based page/view swapping, etc. In other words, the type of stuff being addressed by Angular, etc. No. I can't possibly disagree with this any more strongly. I'm probably on the wrong side of history here, but Javascript absolutely should _not_ be a requirement for using a we…

Some might say you were on the wrong side of history.. If they even knew where the line got to. I doubt anybody has seen it in the past 5 years, so who is to say?

Re: Lotus, a web framework for Ruby

#112

Post by shime »

lobster_johnson wrote: post #90

Looks nice. I particularly like the ORM, which seems well-designed compared to ActiveRecord. That said, I have a distinct feeling this is too little, too late. I and my teams have long migrated away from frameworks, to microservices, or what some people call SOA, and we are not looking back. I strongly encourage this design over the old monolithic Rails approach. These are mostly small, highly specialized Sinatra bac…

This sounds very interesting. Please make a blog post about this if time permits. We seriously lack good resources about micro services when it comes to Ruby.

Re: Lotus, a web framework for Ruby

#113

Post by fredwu »

lobster_johnson wrote: post #90

Looks nice. I particularly like the ORM, which seems well-designed compared to ActiveRecord. That said, I have a distinct feeling this is too little, too late. I and my teams have long migrated away from frameworks, to microservices, or what some people call SOA, and we are not looking back. I strongly encourage this design over the old monolithic Rails approach. These are mostly small, highly specialized Sinatra bac…

The ORM part, largely due to the repository pattern, is very similar to my earlier attempt - Datamappify - https://github.com/fredwu/datamappify

Given time, effort and popularity, I could see Lotus::Model to become the de facto alternative to ActiveRecord, overtaking the ROM (Ruby Object Mapper, previously known as DataMapper) project. :)

Re: Lotus, a web framework for Ruby

#114

Post by pmontra »

izietto wrote: post #104

At the moment, if I should switch from Rails to another Ruby framework, the killer feature would be a well integrated built-in streaming support (something like Lotus::Live in this case), which nowadays is a must for a web framework; otherwise the stability of Rails and the big community around it (people, gems) would win against this project, as against the many other current Ruby frameworks. Anyway I wish good luck…

Rails has http://api.rubyonrails.org/classes/ActionController/Streamin... which I never used. It seems that Lotus::Live isn't ready yet. I can't find any docs for it so I don't know how they compare. Could you point me to an URL. Thanks.

Re: Lotus, a web framework for Ruby

#115

Post by userbinator »

Igglyboo wrote: post #26
thecoffman wrote: post #21

Earlier quoted context omitted.

>A complete web framework has client-side components that facilitate two-way communication to/from the server, data binding, HTML5 history state-based page/view swapping, etc. In other words, the type of stuff being addressed by Angular, etc. No. I can't possibly disagree with this any more strongly. I'm probably on the wrong side of history here, but Javascript absolutely should _not_ be a requirement for using a we…

>If your website doesn't work with NoScript turned on, I won't utilize it. You're definitely in the minority then, most users don't even know what javascript is let alone NoScript. I find it ridiculous that people are arguing against javascript, we're using a computer and not allowing it to run code.

we're using a computer and not allowing it to run code.

...from sources which some people find uncomfortable to be blindly trusting. From a security perspective, it's a huge attack vector - the majority of browser exploits require JS to work. Even if it's sandboxed, there's also the annoyance aspect; scripts can consume CPU and do all sorts of irritating things like breaking the back button and seizure-inducing animations.

Re: Lotus, a web framework for Ruby

#116

Post by jodosha »

vidarh wrote: post #105
krasnoukhov wrote: post #37

Earlier quoted context omitted.

It looks like you're missing the point. As an example, I've built the adapter for DynamoDB[1] so you can throw sequel out in matter of minutes even for existing app, and most likely without any code change. [1] https://github.com/krasnoukhov/lotus-dynamodb

The presence of Lotus::Model was a red flag to me, until I realised that Lotus doesn't seem to depend on it being used? I don't want my web framework to dictate my model API. Lotus::Model may be great, and I like that it's actually trying to implement the DataMapper pattern, but there are projects where all the model code was written for the backend and we only later decided to expose it as a web API for example, and…

@vidarh Lotus doesn't depend on Lotus::Model. I kept it out from the dependencies because of the reasons that you've described. Future versions of Lotus will have some facilities for Model, but it won't be a requirement.

EDIT: BTW Lotus::Model is shipped with an SQL adapter that is a nicer wrapper on top of Sequel. If you love this library you will love Lotus::Model too.

Re: Lotus, a web framework for Ruby

#117

Post by prawks »

stevekemp wrote: post #102
jshen wrote: post #98

Earlier quoted context omitted.

Can you give done examples of the types of things these micro services do?

Not the poster, but I've written a few small sinatra-endpoints in my time. For example I wrote a self-hosted comment-system, which is like a very basic disqus service. The back-end is a simple sinatra service that just allows "GET /comments" and "POST comments". ( http://github.com/skx/e-comments/ ) Last week I wrote a webhook-consumer, again using Sinatra. It receives a POST from github, parses the received JSON, an…

Sounds very similar to the things I've done with web.py in Python-land. Very small, lightweight services that had no need for the power of Django. One such example was a GET/POST/DELETE service to vote on submitted items (ideas, in this case).

Re: Lotus, a web framework for Ruby

#119

Post by izietto »

pmontra wrote: post #114
izietto wrote: post #104

At the moment, if I should switch from Rails to another Ruby framework, the killer feature would be a well integrated built-in streaming support (something like Lotus::Live in this case), which nowadays is a must for a web framework; otherwise the stability of Rails and the big community around it (people, gems) would win against this project, as against the many other current Ruby frameworks. Anyway I wish good luck…

Rails has http://api.rubyonrails.org/classes/ActionController/Streamin... which I never used. It seems that Lotus::Live isn't ready yet. I can't find any docs for it so I don't know how they compare. Could you point me to an URL. Thanks.

Yes, but ActionController::Streaming is not made for long pooling; what I mean is 1) web sockets and/or server side events support and 2) Raisl streaming helpers (models watching, client events, etc.); essentially, the good parts of node.js frameworks.

Lotus::Live doesn't exist, it is a name example for the feature of which I feel the missing.

Re: Lotus, a web framework for Ruby

#120

Post by izietto »

shime wrote: post #109
izietto wrote: post #104

At the moment, if I should switch from Rails to another Ruby framework, the killer feature would be a well integrated built-in streaming support (something like Lotus::Live in this case), which nowadays is a must for a web framework; otherwise the stability of Rails and the big community around it (people, gems) would win against this project, as against the many other current Ruby frameworks. Anyway I wish good luck…

stop complaining and start a Rome Ruby meetup group. I did that couple of months ago with Ruby Zagreb meetup group. Europe, and especially eastern Europe needs more meetup groups!

I wasn't complaining about it, I just reminded when I met him. I don't feel the missing of meetups, I prefer internet communities (mailing lists, GitHub, HN...)
Post reply on HN