Categories
Posts in this category
- A shiny perl6.org site
- Creating an entry point for newcomers
- Sprixel, a 6 compiler powered by JavaScript
- Another perl6.org iteration
- Blackjack and Perl 6
- Why I commit Crud to the Perl 6 Test Suite
- Report from the Perl 6 Hackathon in Copenhagen
- Custom operators in Rakudo
- Defined Behaviour with Undefined Values
- Dissecting the "Starry obfu"
- Perl 6: Failing Softly with Unthrown Exceptions
- The first Perl 6 module on CPAN
- Google Summer of Code Mentor Recap
- Building a Huffman Tree With Rakudo
- Immutable Sigils and Context
- Is Perl 6 really Perl?
- Perl 6: Lost in Wonderland
- Lots of momentum in the Perl 6 community
- Musing and the future of feather and the Pugs repository
- Musings on Rakudo's spectest chart
- My first executable from Perl 6
- Trying to implement new operators - failed
- Let's build an object
- Perl 6 is optimized for fun
- How to get a parse tree for a Perl 6 Program
- Perl 6 in 2009
- Perl 6 ticket life cycle
- The Perl 6 Advent Calendar
- How to Plot a Segment of a Circle with SVG
- Publicity for Perl 6
- Rakudo architectural overview
- Rakudo Rocks
- Rakudo "star" announced
- Rakudo's rough edges
- Rats and other pets
- Releasing Rakudo made easy
- Set Phasers to Stun!
- Starry Perl 6 obfu
- Recent Perl 6 Developments August 2008
- Strings and Buffers
- Subroutines vs. Methods - Differences and Commonalities
- A SVG plotting adventure
- A Syntax Highlighter for Perl 6
- Test Suite Reorganization: How to move tests
- The Happiness of Design Convergence
- Perl 6 Tidings from September and October 2008
- Perl 6 Tidings for November 2008
- Perl 6 Tidings from December 2008
- Perl 6 Tidings from January 2009
- Perl 6 Tidings from February 2009
- Perl 6 Tidings from March 2009
- Perl 6 Tidings from April 2009
- Perl 6 Tidings from May 2009
- Perl 6 Tidings from May 2009 (second iteration)
- Perl 6 Tidings from June 2009
- Perl 6 Tidings from August 2009
- Perl 6 Tidings from October 2009
- Timeline for a syntax change in Perl 6
- Visualizing match trees
- We write a Perl 6 book for you
- When we reach 100% we did something wrong
- Where Rakudo Lives Now
- Why was the Perl 6 Advent Calendar such a Success?
- What you can write in Perl 6 today
- Why you don't need the Y combinator in Perl 6
Tue, 29 Sep 2009
Lots of momentum in the Perl 6 community
Permanent link
Usually I try to tell you something intelligent about Perl 6, but this night's frustrating hours of debugging very simple mistakes demonstrated that my wits have left to 90% at least. Still there's the Iron man blogging challenge, so I'll write a few lines about something entirely subjective.
I've found that there's really momentum in the Perl 6 community, and I'm even more happy to to observe that people hack on other people's projects.
For example Johan Viklund, co-author of the November wiki chimed in with the
installed-modules branch of proto, making it usable rather
quickly. Martin Berends jumped on the train that diakopter set off by starting
his new pet project, a Perl 6 interpreter that emits javascript and runs it
through the V8 engine (more on that
project in one of the next blog posts).
Solomon Foster joined the Rakudo development and did some very significant
work on the trigonometric functions and the corresponding tests. However it
suffered from rather weird dispatch where some some methods that are defined
in parrot's Complex PMC were not overridable. So today I started a branch
which aims to implement the Complex class completely in Perl 6,
and using the Complex PMC only by delegation through inline PIR. I just ripped
out all the old stuff, and Solomon and I started to re-add them.
On a completely unrelated note I want to point out that we have some SQL support in Perl 6 now, through Tene's perl6-sqlite module.
The image above shows the development of the numbers of projects known to proto over time - another indication of the momentum we're gathering.
Comments / Trackbacks:
Trackback URL:
/blog-en/perl-6/lots-of-momentum.trackback
Write a comment
The comments on this blog post have been disabled; the comment form below will not work.