Re: [Mason] ANNOUNCE: Mason 2

oops is there any big player using Mason these days?

On Tue, Feb 22, 2011 at 2:24 AM, Perrin Harkins wrote:
> In case any of you Mason users on the mod_perl list aren't on the Mason l=
ist...
>
> - Perrin
>
> ---------- Forwarded message ----------
> From: Jonathan Swartz
> Date: Mon, Feb 21, 2011 at 11:16 AM
> Subject: [Mason] ANNOUNCE: Mason 2
> To: Mason-Users List
>
>
> I'm pleased to announce Mason 2, the first major version of Mason in ten =
years:
>
>    http://search.cpan.org/perldoc?Mason
>
> Mason 2 has been rearchitected and reimplemented from the ground up,
> to take advantage of modern Perl techniques (Moose, Plack/PSGI) and to
> correct long-standing feature and syntax inadequacies. Its new
> foundations should allow its performance and flexibility to far exceed
> Mason 1.
>
> Though little original code or documentation remains, Mason's core
> philosophy is intact; it should still "feel like Mason" to existing
> users.
>
> Major changes:
>
> * Name. The name is now Mason, instead of HTML::Mason.
>
> * Component classes. Each component is represented by its own (Moose)
> class, rather than just an instance of a common class. This means that
> components have their own namespaces, subroutines, methods, and
> attributes, and can truly inherit from one other. See
> http://search.cpan.org/perldoc?Mason::Manual::Components
>
> * Filters. A single powerful filter syntax and mechanism consolidates
> three separate filter mechanisms from Mason 1 (filter blocks,
> components with content, and escape flags). See
> http://search.cpan.org/perldoc?Mason::Manual::Filters
>
> * Plugins. Moose roles are utilized to create a flexible plugin system
> that can modify nearly every aspect of Mason's operation. Previously
> core features such as caching can now be implemented in plugins. See
> http://search.cpan.org/perldoc?Mason::Manual::Plugins
>
> * Web integration. Mason 1's bulky custom web handling code
> (ApacheHandler, CGIHandler) has been replaced with a simple PSGI
> handler and with plugins for web frameworks like Catalyst and Dancer.
> The core Mason distribution is now completely web-agnostic. See
> http://search.cpan.org/perldoc?Mason::Plugin::PSGIHandler
>
> * File naming. Mason now facilitates and enforces (in a customizable
> way) standard file extensions for components: .m (top-level
> components), .mi (internal components), and .pm (pure-perl
> components).
>
> See http://search.cpan.org/perldoc?Mason::Manual::UpgradingFromM ason1
> for a more detailed list of changes.
>
> Mason 2 is obviously still in alpha status, but it has a fair sized
> test suite and I'm eager to start building web projects with it. I
> hope you'll give it a try and let us know what you think!
>
> Best
> Jon
>

Re: [Mason] ANNOUNCE: Mason 2

Lovefilm big enough for you?

On 24 Feb 2011, at 10:49, xiaolan wrote:

> oops is there any big player using Mason these days?
>=20
> On Tue, Feb 22, 2011 at 2:24 AM, Perrin Harkins =
wrote:
>> In case any of you Mason users on the mod_perl list aren't on the =
Mason list...
>>=20
>> - Perrin
>>=20
>> ---------- Forwarded message ----------
>> From: Jonathan Swartz
>> Date: Mon, Feb 21, 2011 at 11:16 AM
>> Subject: [Mason] ANNOUNCE: Mason 2
>> To: Mason-Users List
>>=20
>>=20
>> I'm pleased to announce Mason 2, the first major version of Mason in =
ten years:
>>=20
>> http://search.cpan.org/perldoc?Mason
>>=20
>> Mason 2 has been rearchitected and reimplemented from the ground up,
>> to take advantage of modern Perl techniques (Moose, Plack/PSGI) and =
to
>> correct long-standing feature and syntax inadequacies. Its new
>> foundations should allow its performance and flexibility to far =
exceed
>> Mason 1.
>>=20
>> Though little original code or documentation remains, Mason's core
>> philosophy is intact; it should still "feel like Mason" to existing
>> users.
>>=20
>> Major changes:
>>=20
>> * Name. The name is now Mason, instead of HTML::Mason.
>>=20
>> * Component classes. Each component is represented by its own (Moose)
>> class, rather than just an instance of a common class. This means =
that
>> components have their own namespaces, subroutines, methods, and
>> attributes, and can truly inherit from one other. See
>> http://search.cpan.org/perldoc?Mason::Manual::Components
>>=20
>> * Filters. A single powerful filter syntax and mechanism consolidates
>> three separate filter mechanisms from Mason 1 (filter blocks,
>> components with content, and escape flags). See
>> http://search.cpan.org/perldoc?Mason::Manual::Filters
>>=20
>> * Plugins. Moose roles are utilized to create a flexible plugin =
system
>> that can modify nearly every aspect of Mason's operation. Previously
>> core features such as caching can now be implemented in plugins. See
>> http://search.cpan.org/perldoc?Mason::Manual::Plugins
>>=20
>> * Web integration. Mason 1's bulky custom web handling code
>> (ApacheHandler, CGIHandler) has been replaced with a simple PSGI
>> handler and with plugins for web frameworks like Catalyst and Dancer.
>> The core Mason distribution is now completely web-agnostic. See
>> http://search.cpan.org/perldoc?Mason::Plugin::PSGIHandler
>>=20
>> * File naming. Mason now facilitates and enforces (in a customizable
>> way) standard file extensions for components: .m (top-level
>> components), .mi (internal components), and .pm (pure-perl
>> components).
>>=20
>> See http://search.cpan.org/perldoc?Mason::Manual::UpgradingFromM ason1
>> for a more detailed list of changes.
>>=20
>> Mason 2 is obviously still in alpha status, but it has a fair sized
>> test suite and I'm eager to start building web projects with it. I
>> hope you'll give it a try and let us know what you think!
>>=20
>> Best
>> Jon
>>=20

Re: [Mason] ANNOUNCE: Mason 2

Four years ago, Amazon.com was completing a huge conversion to a new =
site platform including Mason as the primary templating language. While =
they may be moving away from it in newer development, I'd have to guess =
a substantial part of the site still uses it. They still mention Mason =
in many current job postings.

Jon

On Feb 24, 2011, at 5:06 AM, Dave Hodgkinson wrote:

>=20
> Lovefilm big enough for you?
>=20
> On 24 Feb 2011, at 10:49, xiaolan wrote:
>=20
>> oops is there any big player using Mason these days?
>>=20
>> On Tue, Feb 22, 2011 at 2:24 AM, Perrin Harkins =
wrote:
>>> In case any of you Mason users on the mod_perl list aren't on the =
Mason list...
>>>=20
>>> - Perrin
>>>=20
>>> ---------- Forwarded message ----------
>>> From: Jonathan Swartz
>>> Date: Mon, Feb 21, 2011 at 11:16 AM
>>> Subject: [Mason] ANNOUNCE: Mason 2
>>> To: Mason-Users List
>>>=20
>>>=20
>>> I'm pleased to announce Mason 2, the first major version of Mason in =
ten years:
>>>=20
>>> http://search.cpan.org/perldoc?Mason
>>>=20
>>> Mason 2 has been rearchitected and reimplemented from the ground up,
>>> to take advantage of modern Perl techniques (Moose, Plack/PSGI) and =
to
>>> correct long-standing feature and syntax inadequacies. Its new
>>> foundations should allow its performance and flexibility to far =
exceed
>>> Mason 1.
>>>=20
>>> Though little original code or documentation remains, Mason's core
>>> philosophy is intact; it should still "feel like Mason" to existing
>>> users.
>>>=20
>>> Major changes:
>>>=20
>>> * Name. The name is now Mason, instead of HTML::Mason.
>>>=20
>>> * Component classes. Each component is represented by its own =
(Moose)
>>> class, rather than just an instance of a common class. This means =
that
>>> components have their own namespaces, subroutines, methods, and
>>> attributes, and can truly inherit from one other. See
>>> http://search.cpan.org/perldoc?Mason::Manual::Components
>>>=20
>>> * Filters. A single powerful filter syntax and mechanism =
consolidates
>>> three separate filter mechanisms from Mason 1 (filter blocks,
>>> components with content, and escape flags). See
>>> http://search.cpan.org/perldoc?Mason::Manual::Filters
>>>=20
>>> * Plugins. Moose roles are utilized to create a flexible plugin =
system
>>> that can modify nearly every aspect of Mason's operation. Previously
>>> core features such as caching can now be implemented in plugins. See
>>> http://search.cpan.org/perldoc?Mason::Manual::Plugins
>>>=20
>>> * Web integration. Mason 1's bulky custom web handling code
>>> (ApacheHandler, CGIHandler) has been replaced with a simple PSGI
>>> handler and with plugins for web frameworks like Catalyst and =
Dancer.
>>> The core Mason distribution is now completely web-agnostic. See
>>> http://search.cpan.org/perldoc?Mason::Plugin::PSGIHandler
>>>=20
>>> * File naming. Mason now facilitates and enforces (in a customizable
>>> way) standard file extensions for components: .m (top-level
>>> components), .mi (internal components), and .pm (pure-perl
>>> components).
>>>=20
>>> See =
http://search.cpan.org/perldoc?Mason::Manual::UpgradingFromM ason1
>>> for a more detailed list of changes.
>>>=20
>>> Mason 2 is obviously still in alpha status, but it has a fair sized
>>> test suite and I'm eager to start building web projects with it. I
>>> hope you'll give it a try and let us know what you think!
>>>=20
>>> Best
>>> Jon
>>>=20
>=20

Re: [Mason] ANNOUNCE: Mason 2

Also, I realize now that "first major version in ten years" was a =
potentially misleading choice of words. Mason was actively developed =
until 2006, and has had maintenance releases since then. It's just that =
1.00 was released ten years ago.

On Feb 24, 2011, at 2:49 AM, xiaolan wrote:

> oops is there any big player using Mason these days?
>=20
> On Tue, Feb 22, 2011 at 2:24 AM, Perrin Harkins =
wrote:
>> In case any of you Mason users on the mod_perl list aren't on the =
Mason list...
>>=20
>> - Perrin
>>=20
>> ---------- Forwarded message ----------
>> From: Jonathan Swartz
>> Date: Mon, Feb 21, 2011 at 11:16 AM
>> Subject: [Mason] ANNOUNCE: Mason 2
>> To: Mason-Users List
>>=20
>>=20
>> I'm pleased to announce Mason 2, the first major version of Mason in =
ten years:
>>=20
>> http://search.cpan.org/perldoc?Mason
>>=20
>> Mason 2 has been rearchitected and reimplemented from the ground up,
>> to take advantage of modern Perl techniques (Moose, Plack/PSGI) and =
to
>> correct long-standing feature and syntax inadequacies. Its new
>> foundations should allow its performance and flexibility to far =
exceed
>> Mason 1.
>>=20
>> Though little original code or documentation remains, Mason's core
>> philosophy is intact; it should still "feel like Mason" to existing
>> users.
>>=20
>> Major changes:
>>=20
>> * Name. The name is now Mason, instead of HTML::Mason.
>>=20
>> * Component classes. Each component is represented by its own (Moose)
>> class, rather than just an instance of a common class. This means =
that
>> components have their own namespaces, subroutines, methods, and
>> attributes, and can truly inherit from one other. See
>> http://search.cpan.org/perldoc?Mason::Manual::Components
>>=20
>> * Filters. A single powerful filter syntax and mechanism consolidates
>> three separate filter mechanisms from Mason 1 (filter blocks,
>> components with content, and escape flags). See
>> http://search.cpan.org/perldoc?Mason::Manual::Filters
>>=20
>> * Plugins. Moose roles are utilized to create a flexible plugin =
system
>> that can modify nearly every aspect of Mason's operation. Previously
>> core features such as caching can now be implemented in plugins. See
>> http://search.cpan.org/perldoc?Mason::Manual::Plugins
>>=20
>> * Web integration. Mason 1's bulky custom web handling code
>> (ApacheHandler, CGIHandler) has been replaced with a simple PSGI
>> handler and with plugins for web frameworks like Catalyst and Dancer.
>> The core Mason distribution is now completely web-agnostic. See
>> http://search.cpan.org/perldoc?Mason::Plugin::PSGIHandler
>>=20
>> * File naming. Mason now facilitates and enforces (in a customizable
>> way) standard file extensions for components: .m (top-level
>> components), .mi (internal components), and .pm (pure-perl
>> components).
>>=20
>> See http://search.cpan.org/perldoc?Mason::Manual::UpgradingFromM ason1
>> for a more detailed list of changes.
>>=20
>> Mason 2 is obviously still in alpha status, but it has a fair sized
>> test suite and I'm eager to start building web projects with it. I
>> hope you'll give it a try and let us know what you think!
>>=20
>> Best
>> Jon
>>=20

Re: [Mason] ANNOUNCE: Mason 2

Jonathan Swartz wrote:
> Also, I realize now that "first major version in ten years" was a potentially misleading choice of words. Mason was actively developed until 2006, and has had maintenance releases since then. It's just that 1.00 was released ten years ago.
>

Hi.

I do not really know Mason (yet), but I just want to say that it is an /immense/ tribute
to its developer(s) that a package that was developed more than 10 years ago is still in
active use now, by many sites, and many very large sites.
(The same goes for mod_perl of course).

And when one compares the average of 2-3 minor releases per year over the last 5 years,
with the monthly MS patches ...
(http://www.microsoft.com/technet/security/bulletin/ms11-feb .mspx)


This being said, I would like to report a small bug, I believe more of the web server than
Mason, on the very reference page mentioned by Perrin :

http://masonhq.com/code/history.html

The last line of the "1.43 Dec 25, 2009" section shows an encoding problem.
The name of Frédéric Brière seems to be encoded as UTF-8, but the page is rendered in
iso-8859-1.
The Content-type header returned by the server does not provide a character encoding (and
neither does the html page itself) so the browser defaults to iso-8859-1.

Since this is a "marketing" kind of page, it would look nicer if it appeared correctly.
;-)



(Request-Line) GET /code/history.html HTTP/1.1

(Status-Line) HTTP/1.1 200 OK
Date Thu, 24 Feb 2011 21:55:59 GMT
Server Apache/1.3.33 (Unix) mod_perl/1.29
Content-Type text/html
X-Cache MISS from www.masonhq.com
Keep-Alive timeout=15, max=100
Connection Keep-Alive
Transfer-Encoding chunked

Re: [Mason] ANNOUNCE: Mason 2

Thanks Andr=E9. I haven't touched the site in a while but it's due for =
an overhaul (and conversion to Mason 2) so will hopefully fix things =
then.

On Feb 24, 2011, at 12:56 PM, Andr=E9 Warnier wrote:

> This being said, I would like to report a small bug, I believe more of =
the web server than Mason, on the very reference page mentioned by =
Perrin :
>=20
> http://masonhq.com/code/history.html
>=20
> The last line of the "1.43 Dec 25, 2009" section shows an encoding =
problem.
> The name of Fr=E9d=E9ric Bri=E8re seems to be encoded as UTF-8, but =
the page is rendered in iso-8859-1.
> The Content-type header returned by the server does not provide a =
character encoding (and neither does the html page itself) so the =
browser defaults to iso-8859-1.
>=20
> Since this is a "marketing" kind of page, it would look nicer if it =
appeared correctly.
> ;-)
>=20
>=20
>=20
> (Request-Line) GET /code/history.html HTTP/1.1
>=20
> (Status-Line) HTTP/1.1 200 OK
> Date Thu, 24 Feb 2011 21:55:59 GMT
> Server Apache/1.3.33 (Unix) mod_perl/1.29
> Content-Type text/html
> X-Cache MISS from www.masonhq.com
> Keep-Alive timeout=3D15, max=3D100
> Connection Keep-Alive
> Transfer-Encoding chunked
>=20
>=20
>=20