Permalink
Cannot retrieve contributors at this time
Name already in use
A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
past_present_future_cgi/proposal
Go to fileThis commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
24 lines (19 sloc)
1.02 KB
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This talk aims to give an overview of the past, present, and future | |
of the CGI.pm module. | |
As the new primary maintainer of CGI.pm i would like to explain what | |
i plan to do with the module, i would also like to bring people up | |
to speed with recent changes related to CGI.pm - especially the fact | |
that it will soon no longer be a core module. | |
I will also point out the state of the module with regards to issues | |
and highlight that it is still a commonly used module in some perl | |
development shops; that there are still some perl developers who will | |
advocate its use and why they shouldn't, with a heavy nod towards | |
Sawyer's recent "CGI.pm must die" talk. | |
The "future" will include suggestions for refactoring the module once | |
existing issues have been addressed. These may include: | |
+ Documentation to dissuade the use of CGI.pm | |
+ Increasing test coverage | |
+ Removal of duplicate functionality | |
+ Replacing pre-re-invented wheels with CPAN equivalents | |
+ Deprecation of HTML generation functions | |
The talk is planned as a lightning talk. |