Currently the focus of the work on the js backend is on making nqp-js emit code that runs at a reasonable speed (so that compiling Rakudo and its setting doesn't take eons and I can iterate on it more easily).
Being able to easily profile nqp-js code is very useful for that.
The js profilers I have tried didn't work out so well
- devtools had trouble with native modules as it runs in
- running directly inside chrome require webpacking
- node-inspector didn't support console.profile/console.profileEnd and it's interface locked up while profiling
- some other ones were bitrotted
For the people who use Windows, I've released berrybrew v1.04.
This software was originally written by David Farrell. While I was writing Test::BrewBuild, I needed some additional features (particularly the --with option for exec, and better PATH management). I wrote a couple of PRs, but they were rejected (not by David, but by the new maintainer). Not long after that, the person who had taken over the project disappeared, so I decided to permanently fork it, and nearly completely rewrite the whole thing.
It does everything the original does, but now includes far more:
Read this article on Perl6.Party
Be sure to read Part I of this series.
As I was tagging tickets in my bug ticket helper
app, I was surprised by how
often I was tagging tickets with this particular tag:
It may have been the most used tag of them all. And so, it made be think
PART II: The Experienced Contributor
I will be referring to "core developers," but this generally applies to any
person who has great familarity with the project, how it should, does, and
will work —The Experienced Contributor. When it comes to bug queues, can
this type of people do more than just pick the bug they like the most and fix
LESSON 3: Many Tickets Can Be Fixed With A Single Comment
On my date with the bug queue, I found many tickets that looked relatively
easy to fix, from a technological point of view, but I couldn't even begin
working on them for a simple reason: I didn't know what the correct behaviour
HI! I continue blogging about sparrowdo - a simple perl6 configuration management tool.
This is what we've learned so far:
Consider out latest example with installing CPAN packages:
$ cat sparrowfile
task => 'install CGI',
plugin => 'cpan-package',
parameters => %( list => 'CGI' ),
What we are trying to do here is to install CGI CPAN module using cpan-package plugin. Here is little trick is hidden. A cpan-package implies you have a cpanm client pre-installed at your system. Let's see what will happen if it is not:
Following is the p5p (Perl 5 Porters) mailing list summary for the past week. Enjoy!
Read this article on Perl6.Party
Recently, I decided to undertake a quick little journey down to the
Perl 6's Bug Queue. A quest for fame and profit—some
easy game to hunt for sport. There's plenty of tickets, so how hard can
it be? The quick little journey turned out to be long and large, but I've
learned a lot of good lessons in the process.
PART I: The Newbie Contributor
Right away, I hit a snag. Some tickets looked hard. On some, it wasn't clear
what the correct goal was. And some looked easy, but I wasn't sure whether
I wanted to work on them just yet. While the ticket queue has the tag system,
I needed some personal tags. Something special just for me....
The Ticket Trakr
So I wrote a nice little helper app—Ticket
Trakr. It fetches all the
tickets from the bug queue onto one page and lets me tag each of them
with any combination of:
Thames Valley Perl Mongers, aka TVPM,
are now having monthly social meetings at various locations
in the Thames Valley (in the UK).
Our next meeting is next Monday (18th July) at 8pm, at The Jam Factory in Oxford.
We're not going for the jam, but the beers.