Perl 6 - the future is here, just unevenly distributed

IRC log for #perl6-release, 2016-01-12

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:01 b2gills joined #perl6-release
00:44 b2gills I think that it might be a good idea to make a bad release. That is make a release that probably has backwards compatibility problems, and just announce it as a learning exercise that is not recommended for production. (You can't learn from a mistake that hasn't happened yet)
00:47 Zoffix -1 on that. There's enough confusion with out releases as it is. Adding a "practice release" to the mix just compounds the problem.
00:47 Zoffix s/out/our/;
00:54 TimToady I think we'll get plenty of practice without trying :)
01:02 Zoffix :P
02:49 ilbot3 joined #perl6-release
02:49 Topic for #perl6-release is now »r« - Discussions about Perl 6 and Rakudo release strategies - http://irclog.perlgeek.de/perl6-release/2016-01-11
03:24 b2gills I mean rather than put it off for more than, say a month, which may become a habit.
07:33 FROGGS joined #perl6-release
07:46 nine b2gills: I don't see us putting it off that long. Progress is somewhat slow but steady
07:49 [GeekNerd] joined #perl6-release
07:49 Topic for #perl6-release is now »r̈« - Discussions about Perl 6 and Rakudo release strategies - http://irclog.perlgeek.de/perl6-release/today
07:50 FROGGS [GeekNerd]: worked now, I dunno why
07:50 [GeekNerd] FROGGS, are you an official representative of whichever organization created or develops Perl 6?
07:51 FROGGS [GeekNerd]: kinda, yes
07:51 [GeekNerd] good
07:51 FROGGS :o)
07:51 [GeekNerd] because that is part of the criteria for creating a # instead of ## channel on freenode
07:52 [GeekNerd] anyway  see ya later
07:52 [GeekNerd] left #perl6-release
08:13 FROGGS btw, I was thinking about 'use rakudo' statements this morning and I think we want to have them...
08:13 FROGGS so that one could state that (s)he wants rakudo:ver(v2016.04) or rakudo:moar or something like that
08:14 FROGGS and these statements, identical to how 'use v6.c' is being put in the metafile of a dist, should be putable in the metafile
08:22 nine What for?
08:23 FROGGS to state that your programs needs a certain compiler version or backend
08:23 FROGGS like, if you use jvm-interop
08:26 nine That would abandon the distinction between compiler and language. JVM-interop can be provided in other ways than through a backend. See Inline::Java for Perl 5.
08:27 FROGGS nine: I dont see why the language has to ignore the fact that there are different compilers out there
08:27 FROGGS that's like if you say that one should not be allowed to check what platform one is running on
08:28 FROGGS because the hardware, the os, the vm and the compiler are just platforms
08:28 nine A use rakudo would tie a module or program to one specific compiler. As we only really have one compiler right now, people will use it freely, because it doesn't hurt. This will eventually force a competing compiler to support "use rakudo", too.
08:28 FROGGS no
08:29 nine We already have $*PERL.compiler.name
08:29 FROGGS if there pops up another compiler the authors will adjust
08:29 FROGGS but that's only useful at the time you attempt to install something
08:29 nine The _active_ authors will. There will be lots of abandoned code.
08:29 nine will be afk for meetings for a couple of hours
10:50 _Gustaf_ joined #perl6-release
11:20 TimToady joined #perl6-release
15:12 FROGGS joined #perl6-release
16:19 jnthn On the JVM interop case, that's likely better handled by a "use" decl that brings that in, except I think we already do it that way anyway.
16:19 jnthn (use ...:from<jvm> iirc)
17:16 nine Yes, we do. So a module may plugin into that.
19:00 FROGGS joined #perl6-release
19:49 nine Sooo....what's actually keeping us from merging language_versions?
19:56 jnthn No idea. Am I meant to know what it is and look at it? :)
19:56 FROGGS it is a rakudo branch
19:57 nine jnthn: it's a start of an implementation of your post 6.c proposal
19:58 jnthn ah,ok
20:00 FROGGS so core/ is always about 6.c which we (almost) wont touch ever?
20:01 nine FROGGS: oh, I do hope we'll do lots of performance optimization and a couple of bug fixes there :)
20:01 FROGGS sure
20:02 FROGGS but the rest of my statement is correct?
20:02 FROGGS because if that's true, I'd vote for renaming it to core.c, to help future contributors knowing what it is
20:04 nine Sounds reasonable
20:25 Zoffix joined #perl6-release
20:51 FROGGS joined #perl6-release
22:14 ZoffixWin joined #perl6-release
22:17 ZoffixWin Something of a quick fix: could someone with access add a note on http://rakudo.org/how-to-get-rakudo/ under the Windows installers that there's no 6.c R* release yet? If you're coming in as a Windows user from http://perl6.org/ you land on http://perl6.org/downloads/ and then the instructions lead you to http://rakudo.org/how-to-get-rakudo/ and the Windows section is clearly visible with "Windows Installer packages are available as MSI
22:17 ZoffixWin files here:
22:17 ZoffixWin http://rakudo.org/downloads/star/"
22:17 ZoffixWin And the non-quick-fix: that page needs to be shortened (like half the size) and have a table of contents. I can do the work if anyone can give me a commit bit.
22:51 PerlJam Hmm...
22:52 * PerlJam notices that rakudo.org is running WP 3.8.12
23:38 stmuk_ " wp-includes/class-wp-customize-widgets.php in the widget implementation in WordPress 3.9.x before 3.9.2 might allow remote attackers to execute arbitrary code via crafted serialized data. "
23:38 stmuk_ oh 3.9 not 3.8
23:39 stmuk_ there are still a shedload of XSS and one SQLI listed

| Channels | #perl6-release index | Today | | Search | Google Search | Plain-Text | summary