2016.5,6 Rakudo Starring

The past two weeks first saw a 2016.01 Rakudo compiler release, followed by a 2016.01.1 release with a hot-fix for packagers, both done by Will [Coke] Coleda. Then we had the first post-Christmas Rakudo Star Release, done by Tobias Leich. Followed by the Windows MSI installers, also done by Tobias Leich. Many kudo’s to Will and Tobias for the hard work getting this together for the first time in the Perl 6 Post-Christmas world!

Thank You Sponsors!

Will [Coke] Coleda wrote an addendum to the original Christmas Announcement to thank all of the corporate sponsors of Perl 6 over the years.

Javascript Backend for Rakudo

Paweł Murias, already known for his work on the Javascript backend work for Rakudo, has made a Grant Application for 4 months of full time development work on the Javascript backend. The list of deliverables is impressive:

  • Upload rakudo-js to npm and CPAN.
  • Have this rakudo-js be able compile our chosen subset of the 6.c roast (official Perl 6 test suite) to JavaScript and pass them in a modern browser.
  • Write a simple REPL in Perl 6 that will run in a modern browser.
  • Write a tutorial showing how to use the JavaScript backend.

Please check it out and let your voice be heard! It would be so nice to have this!

Experimental Multi-Line REPL

Rob Hoelz is working on a experimental multi-line REPL and wants you to test it out and receive any feedback you may have. This looks like a really exciting new development for REPL lovers!

Atom Perl 6 Editor Tools

Ahmad M. Zawawi introduced an impressive Github repository of Atom Perl 6 Editor Tools. If Atom is your favourite editor, then this is definitely a place to check out!

FOSDEM 2016

It was busy, and the Perl DevRoom was filled to the rim for most of the day. Unfortunately, no videos available as of now, but they are expected soon (especially since we had Tom Bloor of ShadowCat also taping all of the presentations with 2 cameras). There are also some pictures by Chris Jack. And there are some interviews with Wendy van Dijk, Curtis “Ovid” Poe and Mark Keating made by Hacker Public Radio. And reports by Steve Mynott and Mark Keating.

Other developments

  • Elizabeth Mattijsen has done a lot of incremental optimizations, mostly about Map/Hash access, object creation, dynamic variable lookups, phaser handling, which made some programs of some users go about 10% faster
  • Jonathan Worthington has been optimizing MoarVM and plugging memory leaks. These have not been merged yet, but could have dramatical memory savings for some applications. More about this probably next week!

Blog Posts

Ecosystem Additions

Almost an average of 2 additions per day!

Winding down

Sorry everybody about the Weekly taking 2 weeks again. But after FOSDEM, I was pretty much exhausted. If you are annoyed by the unweekliness of the Perl 6 Weekly, please consider becoming part of the P6W writing team! Contact timotimo or lizmat on the #perl6 IRC channel on Freenode.

2016.1,2,3 What Are We Waiting 4?

It felt a bit like a postpartum depression since the previous Perl 6 Weekly 4 weeks ago. Just before the Christmas release, Jonathan Worthington put his thoughts about post 6.c release policy in a gist. Early January, Stefan Seifert started working on creating a 6.d setting in a branch.  But nothing much apparently changed after that. Will Coleda explains it all in his recent blog entry.

FOSDEM 2016 Is Coming

This coming Saturday/Sunday (30/31 January), FOSDEM will be happening again in Brussels. We’re also going to have a Perl DevRoom on Sunday. These are the Perl 6 related presentations that will be given there:

More specific information about Perl at FOSDEM can be found in Wendy’s blog post.

Mike Friedman’s Journey Into Perl 6

Mike Friedman started a series of Exploring Perl 6 blog posts about his experiences trying to use / get used to Perl 6. It is a nice introduction for those of you who would consider themselves uninitiated: Up And Running, Signatures, Part 1, Sigil Invariance, Numeric Types, Meta Operators and Hyper Operators.

The Perl 6 User Experience

In a blog post, Zoffix Znet announced a repository dedicated to documenting the many aspects of the Perl 6 user experience. Let those Pull Requests come in to make the Perl 6 user experience better and better!

What Jonathan Did While Recovering

Jonathan Worthington wrote a series of blog posts about finally being able to use Perl 6 as a user: Not Guts But 6 parts 1, 2, 3, 4 and 5, in which he fleshes out the STOMP client into a fully functional module. Check out this work in progress.

More IRC Channels

Apart from the #perl6 channel on Freenode (irc.freenode.org), the #perl6 channel on irc.perl.org has been revived as the “Funofficial Perl 6 channel”. Also, to channel discussions about the Perl 6 tool-chain and the Perl 6 release process, there are now two more channels on Freenode: #perl6-toolchain and #perl6-release.

More Documentation

Praise to all of the people working on the documentation: about 300 commits since Christmas! Of course, documentation can always be improved: so let those Pull Requests come in!

Assorted Blog Posts And Other Items

Many, many blog posts and news items about the release of Perl 6. And of course, the normal flow of Perl 6 related blog posts. Here they come, in more or less chronological order:

Notable Links from the Backlog

Scanned the backlog until January 15th. Here are what I thought were notable links mentioned in that backlog.

Ecosystem Additions

Around 60 distributions were added in the past 4 weeks. That’s about 2 a day! Definitely not up to par with CPAN uploads just yet, but a good development nonetheless. So, without further ado, the additions:

Signing Off

Hopefully, everybody in Perl 6 land is more or less on the same page again. Next week Perl 6 Weekly is going to be a bit difficult for yours truly to make, because of FOSDEM and associated activities. Hopefully, timotimo++ will be able to pick it up again.

2015.53: It is out!

Yes, you’ve read the title correctly! We now have a release of the Perl 6 language (the specification) that we commit to keep fixed for a long-ish time. Also, there’s a version of Rakudo that implements a very big chunk of that specification: 2015.12 (you can find the download on http://perl6.org/ now). Please note that we don’t have a Rakudo Star release yet, so you’ll be building from source for now. We are hoping to get a Rakudo Star release out in the coming days (perhaps with a little bug-fix release of Rakudo up front) and a bit later yet publish .msi installers for our Windows users.

The release notes are quite something. This time it contains an overview of what Perl 6 does in general, but also a list of changes since the last release. You can read the release announcement for Rakudo on the advent blog. The day before that release, TimToady wrote a nice and sort of poetic text on the same blog.

Even though the time leading up to the release has been quite exhausting, there’s been many changes before and after the release itself. Here’s a list of things I thought were notable in the last 7 days:

  • The DateTime, Date, and Dateish classes/role have seen a bunch of speedups to their methods including the constructor. (lizmat)
  • loop (…) loops can now return values! (TimToady)
  • METAOP_ASSIGN (which powers +=, -=, ~=, max=, …) now uses .DEFINITE instead of .defined, which gives us not only a speed improvement, but also makes Failure objects correctly explode. (timotimo & jnthn)
  • Precompiled files will now have the same base filename that the installed source files have.
  • Promise.anyof and Promise.allof will now not throw exceptions when one of the passed promises breaks. Instead, it’s now a combinator based solely on completion. (jnthn)
  • The “as Foo” coercion syntax has been thrown out, as it has been replaced by “Foo()” coercion type syntax some time ago. (jnthn)
  • “pack” and “unpack” are now marked experimental and thus you have to “use experimental :pack” if you want to use them as currently implemented. Here’s Juerd’s draft of a new more perl6ish API. (Juerd)
  • Multi-Dimension candidates for BIND-POS will no longer cause an infinite recursion when the object doesn’t actually implement binding (found by Zefram, fixed by timotimo)
  • When building and installing rakudo with an unprivileged user that doesn’t have access to the runtime paths nqp was installed to, RAKUDO_PREFIX in the environment shall help you. (flussence)
  • Rakudo now not only supports Linenoise, but also Readline (hoelzro, DrForr)
  • Creating Instant objects is now 8x faster, DateTime.now is 4x faster (lizmat)
  • pmurias has been adding many more tests for NQP ops and implemented a bunch of ops for the JS backend.
  • No longer infinitely recurse when trying to mkdir / (timotimo)

And here’s also some ecosystem additions:

With this, the ecosystem is at 485 modules. Neat, huh?

I must admit I’m a bit tired from the last few days, so I’m not going through the trouble of collecting every article that covered the Perl 6 release. Maybe you’ll even help me by linking to articles in the comments section under this post :)

Now I need to get to bed and rest up for tomorrow :)

See you in the new year, have a nice NYE celebration, and take care!

timotimo out.

2015.52: Closer and closer to the Release

Wow, the last week certainly flew past quickly. At least that’s how it feels to me. Or perhaps that’s just how cryo chambers work? Anyway, the Perl 6 IRC channel has been really, really busy and there’s been a whole lot of commits zipping past. Let’s see what’s in it for our users:

  • Multi methods in roles are now a whole lot more useful, as you can put multiple candidates with an implementation of { … } in a role to force classes that are supposed to do the role to implement them. (jnthn)
  • EVAL with non-literal strings is now loudly complained about unless you make your intention extremely clear by using the pragma “MONKEY-SEE-NO-EVAL” (to go with other pragmas like MONKEY-TYPING, MONKEY-GUTS (which used to be called “use nqp”), …). (TimToady)
  • Dependencies of precompiled modules are now directly found rather than searched for in the whole precompilation database, which causes a dramatic speed-up when a module with multiple dependencies are loaded. (nine)
  • Supply blocks now get a CLOSE phaser, which will fire when a tap is closed or the supply otherwise completes. (jnthn)
  • The annoying warning about using an undefined %ENV in string context is fixed! (ugexe)
  • NativeCall now understands an extra version parameter to its “is native” trait, which gets translated to per-platform naming. (Skarsnik)
  • Newline handling was changed again. Here’s jnthn‘s commit message for the change:
    Now, \n always means \x0A by default (the newline pragma currently is still available, pending a decision from TimToady++ on its future). We translate \r\n on file/pipe input to \n, and \n to \r\n on output. We don't perform any such translation on sockets, nor on explict .encode
    and .decode calls (providing an escape hatch). \r\n remains a single grapheme, though you're now much less likely to run in to one. This brings us in line with how the problem has commonly been tackled in other languages; logical \n turned out not to work out so well in real life, even if avoiding the cost of boundary translation was nice. Note that we translate at grapheme, not codepoint, level, so a \r\n will never accidentally become \r\r\n (as can happen in some translation layers).
  • We now have much more support for sized as well as signed/unsigned ints. That means you can now do my int8 $foo = -1; my uint8 $bar = -1; and get -1 and 255 respectively. 32bit floats are now also a thing with “num32”. Different native ints used to only make a difference when using NativeCall or in Buf and such. (jnthn)
  • Rakudo now understands × and ÷ operators for multiplication and division respectively. Thus, a WhateverCode that multiplies its two arguments can now be * × * instead of * * *. Also, if you accidentally paste a unicode “MINUS SIGN” instead of the commonly used “HYPHEN-MINUS” (any TeX users in the crowd tonight?), it’ll still give you the subtraction operator.  (TimToady)
  • Also, I think I’ve neglected to mention this, but Rakudo has supported unicodey numbers (only as single digits) for a while now (say ৪ + ૪ outputs “8”). On top of that, numeral unicode superscripts are also supported now (even with more than one digit!). So if you’re so inclined, you can write say 5⁸⁸ == 5 ** 88 and it’ll give “True”.
  • pre-increment and pre-decrement are now a bit faster yet. (TimToady)
  • Getting the .elems of a .combinations iterator is now blazing fast (grondilu)
  • IO::Handle::Seek now expects SeekFromBeginning, SeekFromEnd, or SeekFromCurrent as its whence argument. (lizmat)
  • We have a bool type based on stdbool.h now! (FROGGS)
  • X, Z, and roundrobin now understand itemization (this also fixes the metaop versions of X and Z – not only X, and Z,). (jnthn)
  • The xx operator now no longer gets rid of structure. (jnthn)
  • The JS backend of NQP now implements a whole bunch of mathematical operators. This includes a whole lot of tests for these operators. (pmurias)
  • MoarVM no longer throws an exception when trying to delete non-existing files. (cygx)
  • Thanks to ilmari, MoarVM now accesses unaligned values much less often.
  • UDP reads with length 0 (which libuv sometimes uses to signal a specific states) now no longer trip up MoarVM (hoelzro)

That’s all the interesting changes that immediately stood out to me from a cursory glance over the changelog.

More Adventing

Of course the advent calender didn’t sleep during the last 7 days:

(Yup, that’s 8. I’m giving you a little extra bonus. Because I like my viewers so much!)

Ecosystem catch-up

Since I forgot it last week, here’s the ecosystem additions of two weeks:

Not bad for “before the release”, eh? :)

 

Anyway, I’m pretty tired and it’s pretty late. That’s why I’ll end this post here. Thank you for reading! Be sure to follow Perl 6-related news channels later this week when Christmas hits and release-related things start happening!

2015.51: UPD, DUP, PUD, DPU, and other permutations

‘Sup everybody, it’s timotimo again with the weekly Perl 6 change recap! Before any of the nice changes this past week has to offer, I’ll link to all the lovely advent calendar posts that were published in that time:

Advent Calendar

Changes

  • Rakudo finally has support for UDP sockets via IO::Socket::Async (jnthn)
  • Also, you can now get the native descriptor behind an IO Handle (fileno on linux) (jnthn)
  • permutations is now multiple times faster and more improvements are already on the way (grondilu)
  • $foo++ and ++$foo on native ints can now become extra fast under many circumstances (TimToady)
  • This nasty case of precompilation issues is now no more (nine)
  • A whole bunch of operations – methods and subs – have been reviewed for their interaction with shaped and native shaped arrays (jnthn)
  • Pair.perl will now give the LHS parenthesis so that round-tripping works for things that look like identifiers (like undefined values/type objects) (zefram and lizmat)
  • Code-related objects (which users are very unlikely to want to override) like Code, Regex, Block are now looked up directly in the Setting by the compiler (jnthn)
  • Handling of “need to sink this” in the compiler has been refactored quite a bit (“Great Sink Refactor”, TimToady)
  • More methods on roles are now exempted from punning, which prevents a bunch of errors claiming you’d have to implement some methods because a role requires them (jnthn)
  • Native shaped arrays can now be used together with subs and operators that operate on natives arguments with “is rw” – notably ++ and — (timotimo)
  • CompUnit::RepositoryRegistry is the new CompUnitRepo and a bunch of things have been moved around (nine)
  • .hyper.map and .race.map work again (though .hyper.grep and .race.grep are still broken) (timotimo)
  • “fail” now reliably gives an error when used outside any routine (jnthn)
  • Many metaops (reduce ops, Z and X metaop) will now respect and inherit thunkyness (like the xx op re-evaluating its LHS every time, or short-circuiting behavior of && and friends) (TimToady)
  • A few features that won’t be properly specified in time for christmas have been marked experimental and now require “use experimental” statements: macros and “is cached” (jnthn)
  • Installing distributions that have more than one binary now locates the corresponding scripts properly (hoelzro)

I think that’s about everything. But even if I forgot to mention something, you can clearly see that there’s some nice progress going on here! :)

Starting today, The Perl Foundation is looking for feedback from the community to see if Jonathan’s grant should be extended to pay for another 110 hours.

And with that I’ve already reached the finish line of todays advent calendar weekly post!

See you again next week!

2015.50: Adventing Commences

With this Christmas being The Christmas™, there was no way we’d pass up the opportunity to bring you daily blog posts until Christmas on the Perl 6 Advent Calendar! If you’re unfamiliar with the Perl 6 Advent Calendar, feel free to have a look through each Table of Contents post for each previous year. There is quite a lot of really good content in there, even though some of the older posts may be outdated by now. On a similar note, a page called “Advent of Code” has been mentioned multiple times on the Perl 6 IRC channel. It offers a little programming puzzle every day. Could be great to try out Perl 6 with ;)

Advent Posts So Far

Perl 6 In The News

Blog Posts

Ecosystem Additions

On top of the additions, Math::Tau got thrown out of the ecosystem, as rakudo now ships tau in core.

Notable Changes

After the curli branch merge, module loading, installing and precompilation wasn’t quite perfect yet, so nine++ put in a lot more work to fix bugs found after people finally started testing the code. If you experience more trouble with latest rakudo/nom — which is not unlikely — you’re welcome to report them on #perl6 on irc.freenode.net or via mail to rakudobug@perl.org. Perhaps deleting the folder your Rakudo is installed to (for example, using rakudobrew nuke) helps you, though.

Array subscripting with listy objects is now more consistent. When you have a lazy thing (like an infinite range or something marked with “lazy”), the current size of the array will be used to cut off the subscripting, whereas anything non-lazy will give you assignable containers past the end. In other words, my @a; @a[^2] = 1, 2; will now work.

The ** operator (exponentiation) now throws errors in case an under- or overflow happens. (TimToady)

When making a socket listen, the backlog parameter can now be passed. (JimmyZ)

The “earliest” syntax is now gone. The much simpler to understand supply/react blocks have taken its place. On that note, Channel now has a proper Supply implementation, so Channel objects can be used inside supply/react blocks. Inside “earliest” blocks, trying to multiplex multiple channels forced busy waiting. (jnthn)

For more lovely things jnthn has done you can read his blog post, too (find the link in the “Blog Posts” section above.)

Parameters to MAIN that have a .WHY attached will now show it in the auto-generated USAGE. (donaldh)

NativeCall now supports arguments of type Pointer with an “is rw” attached. (FROGGS)

pmurias has been working on nqp-js for a long time and I’m sure he hasn’t been given enough shout-outs from the weekly yet!

Of course there have also been changes in our doc. Of note, jonathanstowe replaced examples for “earliest” with examples of “react”. Other contributions from dhaZoffix Znet, Skarsnikgfldexawwaiidmoleculeslizmatflussencestmuk, and raiph are of course also much appreciated!

And I must never stop mentioning usev6 (Christian Bartolomaeus) going through the bug tracker making sure to try to reproduce older bugs regularly to point out bugs that have long been fixed and close corresponding tickets. Thanks!

Don’t forget there’s a WANTED document in the doc repo that could surely benefit from your input!

Back to the Cryo Chamber

It’ll be another week until the next post on this blog. Until then it gets to rest in its cryo chamber :)

Except, maybe not this time. I just stumbled upon an idea I had earlier in the year: To go through all evaluated pieces of code in the irclog and highlight some of them in this blog on some other day of the week. Maybe I’ll have a look at that again and actually do it this time!

Have a splendid week, and see you again after the 3rd advent has passed!

2015.48/49 Arrays Shape Up, Curli Lands and Supply Splits

It has been a busy two weeks.  It’s getting harder and harder to keep up.  So here we are with two weeks of goodies! Let’s first get some of the shorter items on the road:

Rakudo Star 2015.11 (Now In Beta!)

Moritz Lenz made sure we have another good starting place for people interested in trying out Rakudo Perl 6!

A New Perl 6 Introduction

Naoum Hankache has created another excellent online Perl 6 Introduction. Most of the comments on Hacker News were quite positive. Weird! :-)

Perl6 Advent Calendar

Jonathan Scott Duff wrote the the introduction to this year’s very special Perl 6 Advent Calendar. Be sure to check out a new blog post every day until Christmas!

London Perl Workshop

Quite a few Perl 6 related presentations at the London Perl Workshop on 12 December 2015:

Several other presentations appear to be interesting from the Perl 6 point of view as well, although they do not appear to be about Perl 6:

Blog Posts

And now, for the more in-depth, code related happenings:

Shaped Arrays

Jonathan Worthington hooked one of the last remaining bits of the GLR into the language: array shapes. That means you can now say:

my @a[3;3] = 1..3, 4..6, 7..9;
say @a;
# [[1 2 3] [4 5 6] [7 8 9]]

Since the system knows the shape of this two dimensional matrix, it can give good error messages:

say @a[4;2];
# Index 4 for dimension 1 out of range (must be 0..2)

Apart from making this feature well performant (which will not happen on this side of Christmas, as Jonathan Worthington points out in his blog post), there are still some features to be filled in:

say @a[2;*];
# Partially dimensioned views of arrays not yet implemented. Sorry.

This just means we have more to look forward to! :-)

Pre-Compilation Returns To Panda

Or in other words: The Curli Has Landed.

About a month ago Jonathan Worthington wrote a gist describing some of a design for better module management and pre-compilation. Since then, Stefan Seifert has been working on implementation of this design in the curli branch. It was felt that that work has sufficiently advanced to merge it back into the main branch, which happened yesterday. This now means that e.g. the standard core modules such as Test.pm and NativeCall.pm are now pre-compiled and installed as any other module from the ecosystem.

This also brings back pre-compilation to modules installed with panda. At the moment of this writing, there are still some rough edges being worked on, but things are looking good for Christmas in that respect. This should also make it (finally) possible to have multiple versions of the same module installed at the same time!

There was one casualty with this change: @*INC is no longer with us, but $*REPO is! I’m pretty sure we will see an advent post about what this all means soon!

A side effect of this merge, is that the bare startup time of Rakudo has dropped with about 10% to around .105 seconds. So, kudo’s to Stefan Seifert for hanging in there and unwind this gnarly set of issues to make Rakudo Perl 6 ready for the future!

Small Supply Refactor

While Jonathan Worthington was working on some Supply related Christmas RT tickets, he realised there was a logic error in the way a Supply can be made from another Supply, like my $mapped = $supply.map will give you another Supply $mapped. This $mapped is supposed to only get emitted values from the original $supply, but technically it would be possible to also emit values on $mapped yourself. And this creates all sorts of logic and composability issues. With Christmas this close, it was decided it would be better to bite this bullet now, rather than have to deal with this after Christmas. So a small refactor was done, which basically splits off the functionality of a Supply you can emit on, to a new Supplier class.

Or, as Jonathan Worthington described in the original commit message:

Supply is now much more like Seq, in that it’s a container around a large number of implementations. Those implementations now do the Tappable role. Tapping a Supply still returns a Tap, but now it only has a .close method. A Supply no longer has a list of taps; it’s just something that can be tapped. This allows for far cleaner and more efficient implementation of the Supply combinators. More importantly, it removes the design issues that rogue code could in theory take any Supply and emit values into it.

Creating an on-demand Supply is now the role of a separate class, at present called Supplier. A Supplier has a Supply method to obtain a Supply. The Supply can be tapped many times, and the Supplier used to emit/done/quit to all those tappers (thus making it the typical way to do live supplies). Code can therefore expose a Supply, but keep the right to publish values to itself, which will be more robust.

The on meta-combinator is gone, in favor of using supply blocks. Some of the built-in combinators using on have been rewritten in terms of Supply blocks. A number remain to be refactored.

Finally, the notion of serial and sane supplies has been introduced. A serial supply promises it’ll never emit more than one value at a time. A sane supply promises it’ll follow the Supply protocol, that is [emit* [done|quit]], and in addition implies serial. All of the built-in combinators provide sanity; Supplier also enforces this, but does provide an escape hatch just in case. This simplifies the implementation of many combinators, and will also help prevent a number of situations that existed before where it was all too easy to write code using supplies that had data races.

So, now you can no longer emit to a Supply:

Supplier.new.Supply.emit: "foo";
# Method 'emit' not found for invocant of class 'Supply'

Note that you create a Supply by coercing a Supplier. This also means you can no longer say:

my $s = Supply.new;
# Cannot directly create a Supply. You might want:
# - To use a Supplier in order to get a live supply
# - To use Supply.on-demand to create an on-demand supply
# - To create a Supply using a supply block

But as you can see, you get a very nice error message instead. The few people already using Supply, only had to do marginal fixes, and in many cases could simplify their code because of this small refactor.

Other Noticeable Happenings

  • Tim Toady added an approximately-equal operator, infix:<≅> (Texas version =~=), to do approximate numerical equal with a threshold as defined by the $*TOLERANCE dynamic variable.
  • Jonathan Worthington fixed several RT tickets by getting the interface to IO::Handle and IO::Socket::Async more in line. He also fixed a number of spurious data loss issues with async sockets.
  • Elizabeth Mattijsen implemented Range.rand, to give you a random number within the given Range.
  • To bring the List and Supply more in line, the Supply.last method was renamed to Supply.tail.
  • Tim Toady implemented numeric superscripts, inspired by the short-lived Operators::Math::Superscripts by Zoffix Znet. This means that say 3² will just work and do the right thing (9 for the mathematically challenged).
  • Elizabeth Mattijsen implemented gistseen and perlseen helper functions to allow classes to implement a .gist/.perl that potentially could contain recursive data-structures.
  • List.first will now just give the first element of the list. List.first(:end) will now just give the last element of the list.
  • IO::Handle.t now works on MoarVM: it indicates whether the handle is opened on a TTY (which is tech-speak for: is there any person watching this?).
  • Arne Skjærholt is still looking for people help him on the IPerl6 kernel project. There is some Low Hanging Fruit there that is just waiting for someone to be plucked!

Ecosystem Additions

Winding Down

It has been a busy 2 weeks. We’re about to enter December 2015. It’s this Christmas. The tension is mounting :-)