Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2015-02-25

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

All times shown according to UTC.

Time Nick Message
00:48 ronsavage joined #marpa
00:49 ronsavage judurand: OK. Thanx.
00:50 jeffreykegler ronsavage: How has testing that last Marpa::R2 developers release gone?
01:24 ronsavage I've stopped trying. I'm re-evaluating all the XML parsers to see what I have available to patch MarpaX :: Languages :: SVG :: Parser, so that I can run it under Perl 5.20.2. Then I'll look at the other 2 which don't run, MarpaX :: Grammar :: *. All this is something I don't need, since I'd like to get back to the 2 real issues: (1) My Mojolicious code needs patching after upgrading jQuery, jQuery UI and DataTable. The 2 jQuery packages are pr
01:52 ronsavage joined #marpa
01:52 flaviu joined #marpa
01:52 ernimril joined #marpa
01:52 sadmac joined #marpa
01:52 Aria joined #marpa
01:52 koo7 joined #marpa
01:52 sivoais joined #marpa
01:52 shadowpaste joined #marpa
01:52 hobbs joined #marpa
01:52 btyler joined #marpa
01:52 lucs joined #marpa
02:29 ronsavage Hmm. Truncation. The 2 jQuery packages are presumably only a small proble. DataTable is rather bigger, since it's re-design. Then there's the on-going clean-up of all my modules' metadata files. Sigh.
02:49 ilbot3 joined #marpa
02:49 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Pastebin: http://scsys.co.uk:8002/marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today
03:08 ronsavage OK. I can replace XML :: SAX :: ParserFactory with XML :: Tiny, and a bit of post_processing. Will start that next, and soon.
05:03 ronsavage joined #marpa
07:44 basiliscos joined #marpa
12:59 lwa joined #marpa
18:39 jeffreykegler joined #marpa
18:41 jeffreykegler Paul Bennett shared this https://plus.google.com/u/0/+D​avidFormosa/posts/ERKaTraZrJS
18:41 jeffreykegler It's about literary criticism techniques as applied to programming.
18:42 jeffreykegler A problem many programmers (and others) have with literary criticism is that it seems to be a lot of unfalsifiable theories --
18:43 jeffreykegler that is, it is explanations afterwards of why things are the way they are, without an exact procedure and with 20/20 hindsight.
18:43 jeffreykegler There are no experiments and no predictions.
18:44 jeffreykegler But, actually, literary criticism *does* have a successful prediction --
18:44 jeffreykegler http://morgenstern.jeffreykegler.com/
18:47 jeffreykegler There supposedly had been a document about Goedel's citizenship hearing, but it seemed to be either lost, and Dawson, author of the best Goedel biography, came to the conclusion it had never existed.
18:48 jeffreykegler I found it "in plain sight", and used literary criticism techniques to show that what appeared to be just another 55-th hand retelling of the tale was in fact the original document, or close to it: http://jeffreykegler.blogspot​.com/2008_12_01_archive.html
18:49 jeffreykegler This prediction was confirmed when, using my identification, Dawson was able to find the original document itself.
18:51 jeffreykegler I consciously was using literary criticism techniques in formulating my prediction -- I'd studied these for many years.
19:57 basiliscos joined #marpa

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