HNHacker News
TopNewBestAskShowJobs

nesquena

110 karma · joined March 5, 2010

Ruby Developer in San Francisco
submissionscomments
nesquena··on Padrino 0.10.0 Released Rubinius support, speed and much more Check it out
I agree with you that our documentation isn't as thorough as Rails guides but I would argue that the Padrino guides we do have and the blog tutorial + screencast are not a bad tool to get started. I recognize though that to get started with Padrino you do need to have some basic handle on Sinatra. I would love to improve the beginner's documentation even further and I hope that Sinatra's docs get better over time as well possibly with our help.

As Florian touches on, Padrino is fundamentally about embracing the power of modularity. Understanding Rack, Rack Middleware, Sinatra, Padrino and a suite of chosen tools does ultimately become necessary. However, like Sinatra you can also learn the basics within 15 minutes. I like to think that Sinatra/Padrino can grow with you as you need it.

If anyone reading this has any interest in helping us with documentation, please let us know. Especially if you are a beginner. We are a very open community and would love some help or even suggestions on how to make our framework more inviting.

nesquena··on Padrino 0.10.0 Released Rubinius support, speed and much more Check it out
I would love to hear your take on how we can improve on the first 2 aspects. I am not too worried about Rails because I use Rails and I use Padrino but despite the increasing modularity, using Rack/Sinatra/Padrino is a qualitatively different development experience.

But in terms of the first 2. How can we improve our documentation, please let me know, we have a bunch of guides http://www.padrinorb.com/guides and decent (I hope) READMEs as well as a written and recorded blog tutorial screencast. Also Padrino is just Sinatra, so all the Sinatra docs here http://www.sinatrarb.com/documentation http://sinatra-book.gittr.com/ work just as well.

How can we be more effective at evangelism?

nesquena··on Show HN: My inherently "viral" experiment: 3Pics.me
Awesome project bryan! Glad we could be helpful during your first Ruby / Padrino project. Look forward to future projects.
nesquena··on Terminal workflow automation with Terminitor
Perhaps not yet, but we'd like it to get there. Perhaps the name was too ambitious until we really fleshed out some of the nicer features we have in store.
nesquena··on Terminal workflow automation with Terminitor
Yeah, we are aware of the limitations and actually we did start this project over an afternoon. We thought it would be cool to have our terminal setup automated so we packaged this up as a gem. Our intent is to absolutely extract things into adapters to make this dead easy to port to linux and windows. Heres the issue for it on github which we plan to tackle soon: http://github.com/achiu/terminitor/issues#issue/5
nesquena··on Padrino: a Ruby framework built upon Sinatra
Fair enough. I can't blame you I want this functionality built into Padrino too and I am one of the core developers. I just haven't had the time to do it right yet and this is a piece that I want to be particularly easy to use and well-done.
nesquena··on Padrino: a Ruby framework built upon Sinatra
If you have ever used Sinatra, absolutely loved it and wanted an all-encompassing way to use it for a more complex problem seamlessly without having to move to Rails, then the need for Padrino becomes clear. Perhaps our post addressing some of these concerns will help explain our reasoning: http://www.padrinorb.com/blog/addressing-concerns-about-padr...
nesquena··on Padrino: a Ruby framework built upon Sinatra
Yes, we have quite a lot of benchmarks here: http://github.com/DAddYE/web-frameworks-benchmark

They show comparisons with many popular ruby frameworks and I would say Padrino does fairly favorably in tests.

nesquena··on Padrino: a Ruby framework built upon Sinatra
Padrino still doesn't support those out of the box. That is the intent of the padrino-cache gem which hasn't been fleshed out yet. It is the last major set of functionality that needs to be sorted out. In the meantime, the sinatra-cache from here:

http://github.com/kematzy/sinatra-cache

seems to provide most of the needed functionality for now and since Padrino supports all rack / sinatra based extensions, it is a reasonable alternative until we finish integrated caching.

nesquena··on Padrino Ruby Web Framework (sits on top of Sinatra)
I agree Vimeo version was unwatchable. We have uploaded a better version to blip.tv here: http://blip.tv/file/3432970/ and updated our blog tutorial to reflect this: http://www.padrinorb.com/guides/blog-tutorial . Also thanks for your feedback.
nesquena··on Padrino Ruby Web Framework (sits on top of Sinatra)
Thanks for pointing that out RattaPack. We have actually recently released a blog post addressing some concerns we have noticed since our release here: http://www.padrinorb.com/blog/addressing-concerns-about-padr... . Hope that helps clarify certain things about our framework!
nesquena··on Padrino Ruby Web Framework (sits on top of Sinatra)
Haha yeah you got us! Our original tagline was that our framework was 'The Godfather of Sinatra'.
nesquena··on Padrino Ruby Web Framework (sits on top of Sinatra)
Padrino developer here. I also like monkrb but if you check out the Padrino guides (http://www.padrinorb.com/guides) you will see that Padrino is quite a bit more full-featured but also modular. You can enable / disable various features of Padrino and even include certain pieces in existing Sinatra apps.

Our team has used Rails and Sinatra both extensively for contract work and I would argue if you give Padrino + Sinatra a try that you will find it does not defeat the mentality of Sinatra. Instead Padrino simply complements the existing feature set with optional enhancements you might frequently need such as form helpers, tag helpers, localization, mailers and more.

I agree that community support for Sinatra and Padrino are considerably lacking in comparison to Rails. I don't think this is something that cannot be fixed however. Sinatra has only recently hit 1.0 stable which means that the community has just begun to grow. I can say our team at least is committed to helping anyone with problems associated with Sinatra/Padrino. Feel free to post any issues here: http://github.com/padrino/padrino-framework/issues if you find any specific problems.

Thanks guys!

nesquena··on Padrino Ruby Web Framework (sits on top of Sinatra)
Glad you like what you have seen so far. Be sure to checkout the guides (http://www.padrinorb.com/guides) and specifically the blog tutorial (http://www.padrinorb.com/guides/blog-tutorial) and if you have any issues, post them here: http://github.com/padrino/padrino-framework/issues
← PreviousPage 2 of 2