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

The future of padrino - moving forward from 0.15.2 #2270

Open
wakatara opened this issue Jan 29, 2023 · 0 comments
Open

The future of padrino - moving forward from 0.15.2 #2270

wakatara opened this issue Jan 29, 2023 · 0 comments

Comments

@wakatara
Copy link

It's kinda interesting after upgrading the scientific app to 0.15.2 (with very few issues), just how much I enjoyed working with padrino again (thank you to the maintainers for all the hard work). And looking at projects like hanami etc it made me think about what would be needed to make padrino a default choice for people who say are targeting apps deliverable in Sinatra.

I'd be very curious about other peoples' opinions on this. Before the 0.15.2 update happened, I briefly looked at rewriting the app in Rails or hanami both of which looked overly complex, as well as Nest (I don't think I'll ever love js frameworks. =] ).

What would people need to see and what would padrino have to support in order to come back in the Godfather 2.0?

(In terms of upgrading a 4 year old app, written 10 years ago, the padrino update was really unproblemaic. All my time has been spent on upgrading frontend frameworks (Bootstrap, javaascript) and dealing with the fact Excel doesn't seem to supoprt the old Open XML spec for spreadsheets anymore. :-/ )

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

1 participant