Re^2: Best Practice for Replacing Globals

I have to say that this has not been my experience. It has proven quite easy in the past to migrate old, crusty CGI-based applications to mod_perl using ModPerl::Registry and especially so compared to having to re-engineer the entire codebase to work with a new framework.

The various web frameworks are fine for green-field projects but impose a significant burden on the developer when migrating in an existing application like this.

🦛

Comment on Re^2: Best Practice for Replacing Globals

Replies are listed 'Best First'.
Re^3: Best Practice for Replacing Globals by marto (Cardinal) on Apr 20, 2023 at 08:43 UTC
"compared to having to re-engineer the entire codebase to work with a new framework." "The various web frameworks are fine for green-field projects but impose a significant burden on the developer when migrating in an existing application like this. In this use case, mojolicious has you covered, adding one hook allows the existing codebase to work as expected. I've used this in the past without issue. "I have to say that this has not been my experience." I've rewritten several legacy CGI::Application codebase with Mojolicious/(or Mojolicious::Lite), the learning curve wasn't steep, I ended up with something faster, fewer lines of code and less cludgy than before. Of course YMMY Update: Also, for the uninitiated, mod_perl binds you to using Apache.	[reply]
Re^4: Best Practice for Replacing Globals by hippo (Archbishop) on Apr 20, 2023 at 13:34 UTC
adding one hook allows the existing codebase to work as expected. I've used this in the past without issue. Thanks for the link - that's very interesting. I will give it a go in due course with the latest project and see how that pans out. 🦛	[reply]