Again, this one is tricky, so Yes I<and> No.
-First let me say that I<nothing> in life is free, and that some
-Moose features do cost more than others. It is also the
-policy of Moose to B<only charge you for the features you use>,
-and to do our absolute best to not place any extra burdens on
-the execution of your code for features you are not using. Of
-course using Moose itself does involve some overhead, but it
-is mostly compile time. At this point we do have some options
-available for getting the speed you need.
-
-Currently we have the option of making your classes immutable
+Firstly, I<nothing> in life is free, and some Moose features
+do cost more than others. It is also the policy of Moose to
+B<only charge you for the features you use>, and to do our
+absolute best to not place any extra burdens on the execution
+of your code for features you are not using. Of course using
+Moose itself does involve some overhead, but it is mostly
+compile time. At this point we do have some options available
+for getting the speed you need.
+
+Currently we provide the option of making your classes immutable
as a means of boosting speed. This will mean a slightly larger compile
time cost, but the runtime speed increase (especially in object
-construction) is pretty significant. This is not very well
-documented yet, so please ask on the list or on #moose for more
-information.
-
-We are also discussing and experimenting with L<Module::Compile>,
-and the idea of compiling highly optimized C<.pmc> files. In
-addition, we have mapped out some core methods as candidates for
-conversion to XS.
+construction) is pretty significant.
+
+We are regularly converting the hotspots of L<Class::MOP> to XS.
+Florian Ragwitz and Yuval Kogman are currently working on a way
+to compile your accessors and instances directly into C, so that
+everyone can enjoy blazing fast OO.
=head3 When will Moose 1.0 be ready?
projects / gitmo/Moose.git / blobdiff