Skip to content

The future of padrino - moving forward from 0.15.2 #2270

Description

@wakatara

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. :-/ )

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions