HN user

nyrb

536 karma
Posts14
Comments34
View on HN

Objectify is a nice framework, but after reading the examples in README made me feel like I am required to take extra iterations: create new responder files, write more codes for each Responder class, etc. This approach is little tedious.

I personally think that writing reusable libraries using Decorator/Presenter patterns or Modules with ActiveSupport::Concern is simple approach.

Avdi's slides: https://speakerdeck.com/u/avdi/p/making-little-classes-out-o...

I highly recommend Objects on Rails book: http://objectsonrails.com/

Was going to pledge the project, but saw "it is browser-based, it will packaged in a webview of some kind so that it feels like a normal app". Nothing wrong with browser-based editor, but I am comfortable with native app. That's my personal preference.

I was experimenting the new version of Twitter Bootstrap 2.0 and the responsive design. It turned out pretty great and then I have decided to extended it to more additions as the following:

* http://bootstrap.io/ for layout design / responsive design

* http://backbonejs.org/ for router (collection/view will be added soon)

* http://url2png.com for web thumbnail

* http://subtlepatterns.com for background wallpaper

* http://icanhazjs.com for rendering template

I am still improving the site as I am learning more about bootstrap and backbone.js. I hope you guys are enjoying the site.

Sorry if I have to ask, what part is not 100% true? You mean that padrino app can be still faster with large app?

You said there are more than "Hello World" benchmarks? I looked at the link that you provided and then looked at this source code of the Padrino app and its still "Hello World":

https://github.com/DAddYE/web-frameworks-benchmark/blob/more...

I expected to see something more than just Hello World app.

I am trying to see why you are suggesting me that Padrino is better than Rails. :-) Sounds like you are completely against Rails. Maybe I am wrong.

I am not against the Padrino web framework. I still like it. :-)

So your benchmark only have tested against the small "Hello World" app. Maybe that's why I suggested that Padrino framework is pretty ideal for small/personal/API projects for fastest responses.

Have you tried benchmarking your one of biggest padrino apps?

Padrino is really nice web framework for Ruby. I have used it for experimental projects.

My work was using latest Padrino framework at work, but extremely unhappy with the its performance (slow response). We had ported the app to Rails 3.1 for better performance. (We will upgrade it to 3.2 soon)

In fact, I think Padrino is pretty ideal for personal and small apps. Not really ideal for medium to large apps.

Just my opinion and experience.