Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Is Padrino dead? #2256

Open
webrockers opened this issue Jun 13, 2022 · 4 comments
Open

Is Padrino dead? #2256

webrockers opened this issue Jun 13, 2022 · 4 comments

Comments

@webrockers
Copy link

I desperately try to get into Padrino. It looked promising.

But it seems every documentation, every tutorial is outdated.

The simplest of examples aren't working.

The padrinorb.com blog .. a desert.

Reddit? Zilch.

Why?

@nesquena
Copy link
Member

nesquena commented Jun 14, 2022

Thanks for taking a look! I think it's fair to say Padrino development has halted at this point. We started Padrino way back in 2008-2009 about 13 years ago. Since then we've had several waves of active contributors, and I am proud of what we built. That said, we no longer have an active development team at this time.

@jorgefuertes
Copy link
Contributor

Padrino was a great project, I have a ton of developments yet running in padrino, waiting for its turn to be migrated or cancelled. Its a great project which didn't found a way to be supported, by a company, a team of entusiasts or by us, its users.

In addition I guess the Ruby fashion has fall down too. When I was developing all in ruby I remember myself hating the Gemfiles, the deployments, the rvm and all the stack, of course I was hating it less than javascript, the worst dependency management ever.

Finally I'd migrate my brain to Golang, was painful at first, but now I'm very happy, its another world.

When I need to fix something in an old padrinorb project I feel again how easy and quick was that development again, a weird and contradictory feeling.

Anyway, I'm very thankful with padrino, sinatra, and all the people involved in any way. Padrino helped to earn my life for several years.

@nesquena
Copy link
Member

nesquena commented Jun 14, 2022

Padrino was a great project, I have a ton of developments yet running in padrino, waiting for its turn to be migrated or cancelled. Its a great project which didn't found a way to be supported, by a company, a team of entusiasts or by us, its users.

In addition I guess the Ruby fashion has fall down too. When I was developing all in ruby I remember myself hating the Gemfiles, the deployments, the rvm and all the stack, of course I was hating it less than javascript, the worst dependency management ever.

Finally I'd migrate my brain to Golang, was painful at first, but now I'm very happy, its another world.

When I need to fix something in an old padrinorb project I feel again how easy and quick was that development again, a weird and contradictory feeling.

Anyway, I'm very thankful with padrino, sinatra, and all the people involved in any way. Padrino helped to earn my life for several years.

Appreciate the message Jorge! Believe it or not, I still have many many different Padrino projects that I maintain and some are still being actively developed. And the framework has been working for me very well for the better part of 10+ years in some of these cases. I still enjoy working on my past Padrino apps as much as I did when we first created it 😄

I appreciate everyone that went along for the ride with us 😄

@webrockers
Copy link
Author

Thanks for taking a look! I think it's fair to say Padrino development has halted at this point. We started Padrino way back in 2008-2009 about 13 years ago. Since then we've had several waves of active contributors, and I am proud of what we built. That said, we no longer have an active development team at this time.

You can definitely be proud. I am not giving up yet. Rails looks to overbloated for my ideas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants