#Bugzilla hosting code#

And the fact that $1 and $2 don't get reset if there's no match.

That numbers are compared with '=' but strings are compared with 'eq', even though in other places strings are interpreted as numbers if used numerically.

The fact that %var is a () (which is also the array notation) but ].

Certain elements of syntax can be confusing for new users, by long experience in training new Perl users:.

Multiple Inheritance can be problematic in extreme edge cases.

Private Methods aren't well supported require additional scaffolding.

Moose allows complex class definitions, though it isn't part of Perl itself.

Core is actively developed but not released as often as Python and Ruby.

Would make us not have to port, avoiding possible Second System Effect and making any transitions (such as to a web framework) easier.

mod_perl is very mature and extremely fast.

They are very well tested due to distributed test system. This section goes over the various advantages and disadvantages of the languages themselves, from Bugzilla's perspective.

The 'serious PHP framework' space it boiling down to one of two these days - Symfony, which yahoo! have used or Zend's Framework which has serious backers like IBM (financially and contributing manpower I believe).

Mako for templating, or use the upcoming Python TT port.

Easy short-term goal, stepping stone towards Frameworks like Catalyst, Maypole, Jifty, etc.

This lists the particular frameworks that we're actually considering. Enforcement of Good Code: One place where Perl falls down is that it doesn't enforce any good coding standards.

We want a language that has good security-oriented features, and that has a community with a history of paying attention to security issues.ħ. Security: Perl has a Taint mode, which encourages security. Anything supporting GNU Gettext in an easy way would be great.Ħ. i18n and l10n: We want to be able to easily localize Bugzilla in different languages without people having to re-write the templates like they do now. We also want libraries generally available or built-in to the language that we can use in the future.ĥ. Available libraries: We don't want to have to re-write the things that we're using now from CPAN. Performance: It shouldn't perform significantly worse than current Bugzilla code.Ĥ. The more 'abstraction' opportunities a language or framework offers, the better off we are.ģ.

#Bugzilla hosting code#

Ease of Modification: We want to be able to change the code without too much work. Ease of Development: We want to rapidly create new features and not have to wory about little details.Ģ. Primary Considerations in Picking a Languageġ. 1 Primary Considerations in Picking a Language.This is only some research being done, and it may or may not ever happen (and consensus among the developers currently says it won't, but the discussion is probably worth having anyway). The existance of this page does not mean that Bugzilla is abandoning Perl. If one particular language has a framework that would be perfect for us, that could swing the decision. For example, Python has Pylons and lots of other frameworks, and Ruby has Rails and Nitro. In addition to looking at the languages themselves, we should also investigate various tookits available for the languages that would make our development easier. That doesn't necessarily mean it has the best frameworks or libraries available. Of all of the ones I (mkanat) have used, I'm most in favor of Ruby as a language, because I think it'd be the fastest to write code in and it seems well-designed for writing large applications. This page is only for technical pros and cons of each language from the perspective of Bugzilla. Please put discussion on the discussion page. This is a basic overview of various possible languages that we could move to, for Bugzilla.