Perl 6 - the future is here, just unevenly distributed

IRC log for #perl11, 2017-01-05

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary

All times shown according to UTC.

Time Nick Message
00:09 willthechill joined #perl11
01:52 stephen joined #perl11
04:16 willthechill stephen: howdy  :-)
04:47 stephen hey willthechill
04:47 stephen how are you mate?
04:50 willthechill good thanks, just working on some long-overdue RPerl bugs!  :-)
04:51 stephen nice
04:52 willthechill if you would like to truly start on your journey as an RPerl contributor, this is the place to start:   https://github.com/wbraswell/rperl/blob/master/docs/devs_getting_started.txt
04:52 stephen nice
04:52 stephen +1
04:58 willthechill let me know when you are done reading and ready to start work, then we will work the process to make you an authorized RPerl contributor
05:04 stephen ah that would be a bit difficult right now as I am in the process to figure out how to work with WordPress
05:04 stephen when I find some time, I will make sure to cover RPerl thoroughly
05:04 willthechill okay
05:08 stephen but for sure, RPerl is into my plans for permanent use in the near future
05:08 stephen ;)
05:08 willthechill great, I'm glad to hear that!  :-)
05:09 stephen question: more and more language designers are into LLVM and use its IR to implement their language as the front-end for this compiler. Do you think RPerl could take advantage of this mechanism and produce binary output like it already does when used accordingly?
05:11 willthechill LLVM support is a very old item on the to-do list, so yes, that has been planned from the very beginning in 2012
05:11 willthechill also, not at all critical for today's RPerl, because gcc works just fine and is faster and more widely supported, etc.
05:12 stephen nice
05:12 stephen development-wise, what are the long-term plans of RPerl?
05:12 willthechill if you become an authorized RPerl developer and reach an expert level of knowledge, then you can contribute to RPerl-on-LLVM if you like
05:13 stephen I'm a GCC die-hard fan myself lol
05:13 willthechill long-term plans?  support all of Perl 5, then all of Perl 6, then merge them together into Perl 11, then take over the world, then leave in a giant fleet of warp-capable space vessels running Perl v11
05:13 willthechill should only take about 30 years
05:13 willthechill or did you mean more long-term than that?
05:13 stephen 30 years are more than enough! hahaha
05:14 willthechill okay great, there you go!  Saint Larry has plans for Perl 6 to last 100 years.  our Perl 11 plans extend for at least triple to quadruple that length of time.
05:16 stephen lol more than fine, just purrfect
05:19 willthechill yup!
05:20 willthechill Jan 1 2017 marked 4 years of RPerl and 4.5 years of Perl 11
05:20 willthechill slow & steady wins the race
05:25 stephen always
05:26 stephen is there a list somewhere with companies or people that have started using RPerl in production?
05:26 stephen or is this kind of information still classified?
05:51 travis-ci RPerl build passed. Will Braswell says 'Authors, Remove Non-Authorized, D. Nielson & P. Bennett'
05:51 travis-ci https://travis-ci.org/wbraswell/rperl/builds/189077067 https://github.com/wbraswell/rperl/compare/f82ee364ada2...bab46f5d6afe
06:17 willthechill stephen: haha no there are no production uses of RPerl yet as far as I know
06:17 willthechill sorry!  it is still "early days" yet
06:17 stephen :/
06:17 stephen oh well...
06:17 willthechill we have only just now launched our web platform, as I have directed you to visit and login to cloudforfree.org
06:18 willthechill it is an uphill battle for the next decades
06:18 willthechill "slow & steady" as I said before
06:19 stephen yeah, I haven't tried it yet, but eventually I will
06:19 stephen I follow the same motto myself
06:19 stephen slow and steady like a good tortoise
06:20 stephen than fast and clumsy hare
06:26 willthechill that's the one
06:27 willthechill of course, there very well COULD be people out there using RPerl for production purposes and we'll never know!
06:27 willthechill so really, the answer is "I have no idea"
06:31 stephen true true
09:38 anton_p joined #perl11
11:01 travis-ci perl11/cperl#2098 (smoke/master - 831b164 : Reini Urban): The build passed. https://travis-ci.org/perl11/cperl/builds/189133467
11:05 anton joined #perl11
11:11 yukikimoto joined #perl11
12:10 travis-ci perl11/cperl#2099 (smoke/master - e20f5f0 : David Mitchell): The build passed. https://travis-ci.org/perl11/cperl/builds/189151532
14:13 travis-ci perl11/cperl#2100 (smoke/master - 46c9068 : Reini Urban): The build passed. https://travis-ci.org/perl11/cperl/builds/189181962
16:18 vytas joined #perl11
17:54 travis-ci perl11/cperl#2101 (smoke/master - bf9673a : Reini Urban): The build was broken. https://travis-ci.org/perl11/cperl/builds/189246682
19:15 travis-ci perl11/cperl#2102 (smoke/master - 42bbdb3 : Reini Urban): The build is still failing. https://travis-ci.org/perl11/cperl/builds/189268192
19:19 willthechill plenty of badmouthing rurban happening over in #toolchain, I did my best to defend the honor of Perl 11 and all parties!  :-P
20:15 travis-ci perl11/cperl#2103 (smoke/master - d8e6f54 : Reini Urban): The build is still failing. https://travis-ci.org/perl11/cperl/builds/189279108
20:55 willthechill joined #perl11
21:13 ilbot2 joined #perl11
21:13 Topic for #perl11 is now Perl5 + Perl6 == Perl11; # http://irclog.perlgeek.de/perl11/
23:13 travis-ci perl11/cperl#2104 (smoke/master - b14d5a7 : Reini Urban): The build was fixed. https://travis-ci.org/perl11/cperl/builds/189336481
23:33 stephen joined #perl11

| Channels | #perl11 index | Today | | Search | Google Search | Plain-Text | summary