The web in a box - a next generation web framework for the Perl programming language

IRC log for #mojo, 2017-11-21

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

All times shown according to UTC.

Time Nick Message
00:08 gryphon joined #mojo
00:33 Grinnz repair from 0.099/s to 313.700/s with a couple more...
00:33 Grinnz that solves the easy problems :P
00:46 mohawk #winning
00:49 aborazmeh joined #mojo
01:04 ed207 joined #mojo
01:04 ed207 Hello
01:11 ed207 ?
01:12 ed207 I had dropped by because mojomojo.org is now just redirecting back to Github. Was looking for information on the state of that module.  I'm not sure if mojolicious is mojomojo or not.
01:14 ed207 Attempting to install a good wiki, and since I'm going to start developing in Catalyst, thought that using something based on Catalyst would be a good idea.
01:14 pink_mist mojomojo has nothing to do with mojolicious
01:15 pink_mist even though the author is part of the mojolicious team
01:17 ed207 Am I correct that mojolicious is using Catalyst?
01:17 pink_mist noooo
01:17 pink_mist Mojolicious is a competing product
01:17 ed207 It must be the mojo that was confusing me :)
01:18 ed207 I've been developing for a while on OpenBSD and using Perl, so I wanted an API that was well suited for OpenBSD
01:18 ed207 I've written some APIs before, but that was in Linux/PHP. Trying to get away from PHP
01:19 pink_mist not sure what you mean by API here
01:21 ed207 It was a homegrown MVC used to produce web pages, but also was used by native programs over the network to use the MVC. A bunch of automation and a specialized site.
01:37 klapperl joined #mojo
01:50 gordonfish joined #mojo
02:52 webart1 mojomojo was written in Catalyst I think
02:54 kaare joined #mojo
02:54 webart1 Catalyst is still a good a framework ...  Mojolicious rox :)
03:06 noganex joined #mojo
03:07 asthman joined #mojo
03:57 kaare joined #mojo
04:21 jamesaxl joined #mojo
04:35 zivester joined #mojo
05:04 dboehmer_ joined #mojo
05:32 Sebbe joined #mojo
05:50 kaare joined #mojo
06:13 Vandal joined #mojo
06:29 inokenty-w joined #mojo
06:41 Heartless_Jack joined #mojo
07:06 Sebbe joined #mojo
07:14 dod joined #mojo
07:20 dod joined #mojo
07:27 karjala_ joined #mojo
07:55 AndrewIsh joined #mojo
08:05 dod joined #mojo
08:19 kaare joined #mojo
08:26 kaare joined #mojo
08:30 trone joined #mojo
09:03 anon joined #mojo
09:11 kaare joined #mojo
09:32 kaare joined #mojo
09:39 dod joined #mojo
09:44 itaipu joined #mojo
10:10 zivester joined #mojo
10:13 geospeck joined #mojo
10:23 PsimanX1 joined #mojo
10:28 trone joined #mojo
10:48 kaare joined #mojo
10:50 tchaves joined #mojo
10:56 kaare joined #mojo
11:01 Heartless_Jack joined #mojo
11:51 ashimema joined #mojo
11:54 ashimema joined #mojo
12:00 dod joined #mojo
12:31 zivester joined #mojo
12:32 nic joined #mojo
12:33 ChmEarl joined #mojo
12:50 dod joined #mojo
13:07 geospeck joined #mojo
13:45 exp-innit is there a nice way for me to call 'include' in an ep template, but without all the args on one line? i don't actually know how it gets parsed
13:45 exp-innit but i have a helper to display a database field and i need to use it everywhere with many different options
13:45 exp-innit and it's quite hard to read single line comma delimited options
13:47 nic what's happening when you try?
13:48 sri <%= ... %> can be split over as many lines as you like
13:49 exp-innit nic: syntax error using % prefixes
13:49 exp-innit sri: thanks, that will do perfectly
13:49 exp-innit w
13:49 exp-innit more like :w, anyhow sri that is perfect tyvm
13:58 marcus hmm, seems I missed a potential customer :)
14:12 kaare joined #mojo
14:17 gryphon joined #mojo
14:43 kaare joined #mojo
14:56 gizmomathboy joined #mojo
15:43 mtths joined #mojo
16:07 geospeck joined #mojo
16:09 disputin joined #mojo
16:19 sh14 joined #mojo
16:22 disputin joined #mojo
16:40 zivester joined #mojo
16:49 itaipu joined #mojo
17:02 perlpilot someone is balking because I used a module for this dancer app that uses mojo to do some work.   Anyone have any good words of reassurance that having 2 web app frameworks installed isn't going to hurt?
17:02 sri mojo is a web dev toolkit
17:03 sri the framework is merely an example application for the toolkit
17:04 Grinnz as long as you aren't trying to use the event loop in a dancer app, you can piecemeal whatever you want
17:04 Grinnz the main event loop, anyway
17:04 jberger I concur with sri 100%, the Mojo namespace is intended to be reusable
17:05 perlpilot danke.
17:05 jberger I routinely encourage use of the Mojo toolkit in non-Mojolicious apps
17:06 jberger Grinnz: I could even make a case for using the IOLoop, as a simple backend-agnostic interface that isn't AnyEvent
17:06 perlpilot me too, but this is the first time some one has slightly freaked out about it  :)
17:06 jberger what is their actual concern
17:06 jberger ?
17:06 sh14|2 joined #mojo
17:07 perlpilot That it's "like installing catalyst so that you can use a plugin"
17:07 jberger ah, but that's where you point out that Mojo has no non-core dependencies and is only like 8k lines of code
17:08 perlpilot yeah, I got that.
17:08 Grinnz jberger: hence "the main event loop anyway", as in don't expect it to be running in the dancer app unless you start it yourself inside one request
17:08 jberger if they think that its like installing Catalyst I can see their concern, it explodes their footprint
17:08 jberger Grinnz: ah, fair point
17:22 disputin joined #mojo
17:27 itaipu joined #mojo
17:29 dod joined #mojo
18:08 jamesaxl pink_mist: do you like Ace Of Base?
19:03 disputin joined #mojo
19:31 disputin joined #mojo
19:32 karjala_ joined #mojo
19:47 brunoramos joined #mojo
19:57 ghenry joined #mojo
20:04 jabberwok joined #mojo
20:22 mib_i0y28a joined #mojo
20:22 mib_i0y28a what is this
20:22 purl well, this is is not possible over a remote connection?
20:22 Grinnz irc?
20:22 purl somebody said irc was serious fucking business or internet relay chat or more boring these days.... or hard, let's go shopping
20:22 mib_i0y28a got any mrijuana
20:23 Grinnz left #mojo
20:23 Grinnz joined #mojo
20:23 mib_i0y28a was kicked by Grinnz: no
20:23 mib_i0y28a joined #mojo
20:23 pink_mist Grinnz++
20:49 CandyAngel Okay, before I hit the "Create pull request", should I ask if I should submit it first?
20:51 pink_mist if you're one of the people who have annoyed sri too much before, for example kes, then you should get confirmation that you should submit it first, but if you're not one of those people you can probably just hit it
20:51 CandyAngel Oh.. hmm.. I don't know if I am still in that group? It's been [34] days since I last annoyed sri
20:52 CandyAngel :P
20:52 pink_mist lol :P
20:53 trone joined #mojo
20:56 geospeck joined #mojo
21:28 jberger It is always good too discuss a change first IMO
21:28 jberger Especially in #mojo a PR is considered ready to vote
21:29 CandyAngel I will try to remember >.<
21:30 mib_c18jyd joined #mojo
21:48 brunoramos joined #mojo
21:57 sri pink_mist: it's not about annoying, with kes there's big communication problems
21:57 pink_mist ah, my mistake
21:58 sri which was why i wanted him to convince someone else first that a problem is really a problem, so all the details have been explained well enough
21:58 Grinnz he had a habit of throwing poorly-vetted issues at p5p as well
21:59 sri actually i was hoping the mailing-list would work better for kes, but his mail is the only one in months without an answer
21:59 sri not sure there is much else that can be done
22:00 disputin joined #mojo
22:02 sri CandyAngel: your pull request is an instant reject i'm afraid
22:02 CandyAngel Not something you want in Minion?
22:03 sri aside from the usual tests+documentation or if i want it personally, when you make changes to the backend you have to make sure it's easy for alternative backends to support the change as well
22:03 disputin joined #mojo
22:04 sri that said, i think the change goes against the fundamental design of minion
22:04 sri everything is designed around the idea of volatile jobs
22:05 sri how would a redis backend cope with persistent jobs>
22:05 sri s/>/?/
22:06 * sri is very very picky about backend features
22:06 sri since all backends have to support them
22:06 CandyAngel yeah, makes sense
22:06 sri the barrier is very very high for getting one accepted
22:06 CandyAngel And... the same way it would handle it if you set it to the number of seconds in 60 years?
22:07 CandyAngel Which is totally going to be my workaround :P
22:08 sri well, that's only abusing an existing feature
22:08 sri ¯\_(ツ)_/¯
22:08 CandyAngel Hence the PR to make it explicit and not abuse :D
22:09 CandyAngel But that's fine. Want me to close the PR?
22:09 * sri nods
22:10 sri btw. it's surprisingly easy to move most of the worker code from the command to a Minion::Worker method
22:15 CandyAngel I'll just set it to 9007199254740992 seconds. If they are still using it in 286,401,075 years.. someone's really messed up
22:16 pink_mist the y286403.092k problem :P
22:16 CandyAngel Maybe I can add a job with a 9007199254040992 delay that tells someone to change that value in the config
22:17 Grinnz rofl
22:17 sri lol
22:17 jberger :D
22:28 itaipu joined #mojo
22:58 sri ok, this is a little risky, since there is so much potential for breakage https://github.com/kraih/minion/commit/0f1fb74e80480fddd1b87d1a79b9c8d3acdbf171
22:58 sri so, please test
23:04 disputin joined #mojo
23:41 jberger fyi, I've made some changes to Mojolicious::Plugin::Multiplex so that the javascript-side channels adhere more to the websocket interface (well actually more to the EventTarget interface)
23:41 jberger but then also added a jsonmessage event so you can get json parsed directly
23:41 jberger something I needed for $work

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