Perl 6 - the future is here, just unevenly distributed

IRC log for #marpa, 2017-12-05

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

All times shown according to UTC.

Time Nick Message
00:16 ronsavage joined #marpa
01:06 kaare__ joined #marpa
03:00 ilbot3 joined #marpa
03:00 Topic for #marpa is now Start here: http://savage.net.au/Marpa.html - Code paste/run: https://f.perlbot.pl/#marpa - Jeffrey's Marpa site: http://jeffreykegler.github.io/Marpa-web-site/ - IRC log: http://irclog.perlgeek.de/marpa/today - Youtube channel: https://www.youtube.com/channel/UCYKVfGBtfTqbs1JdYq-dc5g
03:18 ronsavage joined #marpa
06:18 idiosyncrat joined #marpa
06:19 idiosyncrat Demat!
06:19 idiosyncrat left #marpa
11:28 Cheery been contemplating over this thing few days now.. I've tried out ideas and read through papers
11:29 Cheery I think most of my concerns are performance related
11:31 Cheery it is a bit wrong. First one should get stuff to work, then contemplate whether it's efficient or not.
11:31 Cheery but other concern I have is in the readability of the grammars if I do this.
19:58 idiosyncrat joined #marpa
19:59 idiosyncrat Cheery: Currently the fashion is against attempts at efficiency at least until some "later" which very often is "never".
20:00 idiosyncrat And I've worked with a lot of programmers who disguised their inability to get code to work by reporting that they were focused on optimizing.
20:01 idiosyncrat So an effect of the current anti-efficiency trend has been to correct some real abuses.
20:02 idiosyncrat But there things always go too far in the other direction.
20:02 idiosyncrat With Marpa, the actual problem had already been solved in the 1970's, so most of what Marpa is about is efficiency.
20:03 idiosyncrat (I also added left-eideticism and Ruby Slippers to the Earley/Leo algorithm, so there also are new capabilities in Marpa.)
20:04 idiosyncrat Very often, yes, we think about efficiency too early.  But sometimes we think about it too late and wind up wasting our time.
20:07 idiosyncrat These days the result of the "don't bother with optimizing" trend is evident in browers and apps.  The hardware is not extremely fast, but browsing seems to be getting slower.
20:08 idiosyncrat I suspect because we're dealing with layer upon layer of code whose authors were trained to ignore efficiency.
20:10 idiosyncrat In Marpa, I paid serious attention to efficiency from day zero, because that was the only issue -- the problem itself was solved (and I didn't see the possibility of left-eideticism and Ruby Slippers until I was deep into writing Marpa).
20:11 idiosyncrat At times I went too far -- there are places that are over-optimized, and other places where things would have gotten done faster if I'd waited on some of the optimizations.
20:11 idiosyncrat But if I hadn't focused on optimization in Marpa, almost nobody would be using it.
20:17 idiosyncrat left #marpa

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