-
Notifications
You must be signed in to change notification settings - Fork 289
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 this package still maintained? #406
Comments
apparently, no |
You could fix it yourself but Hacktober is over so no shirt for you 😄 |
@dwenaus Do you still use Klein? If not, what did you switch to? |
I know you didn't ask me, but I'm going to throw some thoughts up here, on the off chance that someone will find them useful. I used it on a project I was heavily involved in a few years ago. I'm no longer involved with it, but the project is going strong, still using Klein. I've been doing a lot of Node work lately, and not as much PHP. The project has not had updates in quite a while, but it was stable and ran without issues. It has a pretty limited scope and you don't necessarily need constant updates for it. That said, when I need a PHP routing framework for a project last year, I ended up going with Slim (https://www.slimframework.com/), rather than Klein. I don't remember all the factors that went into that decision, lack of updates was probably in there somewhere, though. The good thing about Klein is that it's so small, you could actually go through it and learn how the whole thing works in a moderate amount of time, so even if it's not supported, it wouldn't be that hard to maintain a fork yourself, should the need arise. On the other hand, Slim has regular updates and a decent-sized community (last time I looked). They support PSR7 Request/Response objects if that's important to you. I don't know how many people that matters too, though. I've never really needed my Request/Response objects to be interoperable with other frameworks. I never use more than one framework on the same project. Slim has a somewhat more traditional/conventional middleware mechanism. Although Klein has a way that you can provide middleware functionality, using the '*' route, which works fine, and is quite elegant in its simplicity. I think if I'm choosing a tool for a team, or for a project with a lot at stake, I would be a little hesitant to go with Klein. Even though it's been pretty solid for me. Slim provides the same benefits for the most part, with stronger community support. If it's a personal project or something else where I expect to be the only developer, the simplicity and "knowability" of the smaller code footprint might justify choosing Klein. Of course, with a project like that, it really comes down to using whatever you want. If you want a whole lot of extra bells and whistles beyond routing, and don't mind being told what to do a lot, there's always Laravel and Symfony, but that's really a completely different use case if you ask me. |
I was using this and just wondering if the package is still maintained. I see a number of issues and PRs but no activity. Does the package need a new owner?
The text was updated successfully, but these errors were encountered: