<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div><a href="https://www.ruby-toolbox.com/categories/Background_Jobs">https://www.ruby-toolbox.com/categories/Background_Jobs</a> </div><br><div><div>On 6 Jul 2014, at 22:26, James Ladd <<a href="mailto:ladd.james@gmail.com">ladd.james@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><meta http-equiv="content-type" content="text/html; charset=utf-8"><div dir="auto"><div>Hi Andrew and others,</div><div><br></div><div>You ask what trouble we are having here in Australia on my project.</div><div><br></div><div>Simply we want to test our app which receives a http request through rails and in response to that request it can fire off background events also via http to the same application.</div><div>This causes all sorts if trouble, and hangs, and even a nil doesn't understand reverse in the SQL layer.</div><div><br></div><div>We need to test our app in confidence and we cannot.</div><div><br></div><div>Yes we have tried jruby as well.</div><div><br></div><div>- James<br><br>Sent from the holodeck.</div><div><br>On 7 Jul 2014, at 7:09 am, Mark Burns <<a href="mailto:markthedeveloper@gmail.com">markthedeveloper@gmail.com</a>> wrote:<br><br></div><blockquote type="cite"><div dir="ltr">I feel like hoping and waiting for such things as the GIL issue to be solved by the ruby core team, (IMHO it probably won't happen) and for complex concurrency issues to be solved by the Rails team are not the most proactive approaches you could take to solve what at heart are probably application performance concerns.<div>
<div><br><div>Have you considered things like <a href="http://www.rabbitmq.com/tutorials/tutorial-one-ruby.html">AMQP</a> or <a href="https://github.com/brandonhilkert/sucker_punch">actors</a>?</div></div></div><div><br></div>
<div>I think these are some of the most common ways people in the ruby community seem to solve performance issues.</div><div><br></div><div>> <span style="font-family:arial,sans-serif;font-size:12.800000190734863px">About to drop Ruby/Rails because this support is so bad.</span></div>
<br style="font-family:arial,sans-serif;font-size:12.800000190734863px"><div>Statements like this can sound like threats. There's a lot of coordinated work that would have to be done by a ton of unrelated open source unpaid contributors. </div>
<div>Ruby/Rails is not a product/service you are paying for, but a community of people building software. </div><div><br></div><div>In a word, suggesting one may stop paying for a service has a lot more effect than suggesting one may leave a community.</div>
<div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 5 July 2014 04:00, James Pike <span dir="ltr"><<a href="mailto:lrug@chilon.net" target="_blank">lrug@chilon.net</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I'd like to see the entire Rails community move away from blocking IO<br>
(optionally together with threads) as the IO model and I think Rails is<br>
in a unique position to offer some leadership/motivation/guidance there<br>
to the entire Ruby community on that issue. The context switching<br>
overhead (+ GIL problems) make the IO model seem rather anachronistic<br>
and we lose a lot of good people to node.js and the less-pragmatic<br>
language that is JavaScript purely due to concerns of this nature.<br>
<br>
Instead the use of asynchronous IO + Fibers (so we get the advantages of<br>
ASIO with the readability of blocking IO style) would make Rails seem<br>
more compelling than node.js without needing code to become the tangled<br>
mess of callback hell that many node.js projects become. It's also worth<br>
noting that EcmaScript 7 will have the "async function" feature which<br>
will essentially provide what Ruby Fibers already do. It's sad to see<br>
our community becoming fragmented and outpaced by a language that most<br>
of us will probably agree is inferior to Ruby :(<br>
<br>
Cheers, James<br>
<div class=""><br>
On Fri, Jul 04, 2014 at 04:21:39pm +0100, Najaf Ali wrote:<br>
> Genuinely interested: do you have any specific complaints? What could they<br>
> do to address them?<br>
><br>
> On Thu, Jul 3, 2014 at 11:56 PM, James Ladd <<a href="mailto:ladd.james@gmail.com">ladd.james@gmail.com</a>> wrote:<br>
><br>
> Please can someone ask the Rails maintainer when they will focus<br>
> properly on concurrency!<br>
> About to drop Ruby/Rails because this support is so bad.<br>
> I'd ask myself but I'm in Australia<br>
> - James<br>
><br>
> Sent from the holodeck.<br>
><br>
> > On 4 Jul 2014, at 7:02 am, <a href="mailto:chat-request@lists.lrug.org">chat-request@lists.lrug.org</a> wrote:<br>
> ><br>
> > Send Chat mailing list submissions to<br>
</div>> > A A <a href="mailto:chat@lists.lrug.org">chat@lists.lrug.org</a><br>
<div class="">> ><br>
> > To subscribe or unsubscribe via the World Wide Web, visit<br>
</div>> > A A <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<div class="">> > or, via email, send a message with subject or body 'help' to<br>
</div>> > A A <a href="mailto:chat-request@lists.lrug.org">chat-request@lists.lrug.org</a><br>
<div class="">> ><br>
> > You can reach the person managing the list at<br>
</div>> > A A <a href="mailto:chat-owner@lists.lrug.org">chat-owner@lists.lrug.org</a><br>
<div class="">> ><br>
> > When replying, please edit your Subject line so it is more specific<br>
> > than "Re: Contents of Chat digest..."<br>
> ><br>
> ><br>
> > Today's Topics:<br>
> ><br>
</div>> > A 1. Ruby on Rail 4.2 networking breakfast (Graeme McCubbin)<br>
<div class="">> ><br>
> ><br>
> > ----------------------------------------------------------------------<br>
> ><br>
> > Message: 1<br>
> > Date: Thu, 3 Jul 2014 16:42:52 +0100<br>
> > From: Graeme McCubbin <<a href="mailto:graeme.mccubbin@unboxedconsulting.com">graeme.mccubbin@unboxedconsulting.com</a>><br>
> > To: <a href="mailto:chat@lists.lrug.org">chat@lists.lrug.org</a><br>
> > Subject: [LRUG] Ruby on Rail 4.2 networking breakfast<br>
> > Message-ID:<br>
</div>> > A A <<a href="mailto:A7074772-6D14-4340-B285-75DD6254D55D@unboxedconsulting.com">A7074772-6D14-4340-B285-75DD6254D55D@unboxedconsulting.com</a>><br>
<div class="">> > Content-Type: text/plain; charset="windows-1252"<br>
> ><br>
> > Hi there,<br>
> ><br>
> > If you?re interested in what?s coming up in Rails 4.2, Unboxed<br>
> Consulting are holding a networking breakfast session with CTO, Andrew<br>
> White, a Ruby on Rails contributor and Rails Core Team Member, to let<br>
> you know.<br>
> ><br>
> > The session will begin with a light breakfast at Unboxed Consulting<br>
> HQ. Andrew will then be covering:<br>
> ><br>
</div>> > ? A What?s coming in Rails 4.2<br>
> ><br>
> > ? A Awareness of Rails opportunities to students<br>
> ><br>
> > ? A Encouraging contributions to Rails from the UK Ruby community<br>
<div class="">> ><br>
> ><br>
> ><br>
> > A short Q&A session will also follow this, giving attendees the<br>
> opportunity to ask away.<br>
> ><br>
> > This is a one-off session and we?d love for you to attend.<br>
> ><br>
> > Here are the whens and wheres:<br>
> ><br>
> > Date: Friday 18th July<br>
> ><br>
> > Time: 09:00 (for 09:15) until 10:15<br>
> ><br>
> > Location: 17 Blossom Street, Liverpool Street, London, E1 6PL<br>
> ><br>
> ><br>
> ><br>
> > You can register here:<br>
> <a href="http://www.eventbrite.co.uk/e/ruby-on-rails-42-networking-breakfast-tickets-12152397147?aff=es2&rank=1" target="_blank">http://www.eventbrite.co.uk/e/ruby-on-rails-42-networking-breakfast-tickets-12152397147?aff=es2&rank=1</a><br>
> ><br>
> > It should be a great event, lasting about an hour, and there?s free<br>
> breakfast!<br>
> ><br>
> > Graeme McCubbin<br>
> > Unboxed<br>
> > Consulting<br>
</div>> > E: A A <a href="mailto:graeme.mccubbin@unboxedconsulting.com">graeme.mccubbin@unboxedconsulting.com</a><br>
> > M: A A <a href="tel:%2B44%2075%208300%200634" value="+447583000634">+44 75 8300 0634</a><br>
> > T: A A <a href="tel:%2B44%2020%203137%202938" value="+442031372938">+44 20 3137 2938</a><br>
> > F: A A <a href="tel:%2B44%2020%207183%204251" value="+442071834251">+44 20 7183 4251</a><br>
<div><div class="h5">> > 17 Blossom Street<br>
> > London, E1 6PL<br>
> > United Kingdom<br>
> > <a href="http://www.unboxedconsulting.com/" target="_blank">www.unboxedconsulting.com</a><br>
> > -------------- next part --------------<br>
> > An HTML attachment was scrubbed...<br>
> > URL:<br>
> <<a href="http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20140703/668947b8/attachment.html" target="_blank">http://lists.lrug.org/pipermail/chat-lrug.org/attachments/20140703/668947b8/attachment.html</a>><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > Subject: Digest Footer<br>
> ><br>
> > _______________________________________________<br>
> > Chat mailing list<br>
> > <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
> > <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
> ><br>
> ><br>
> > ------------------------------<br>
> ><br>
> > End of Chat Digest, Vol 102, Issue 2<br>
> > ************************************<br>
> _______________________________________________<br>
> Chat mailing list<br>
> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
> <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br>
> _______________________________________________<br>
> Chat mailing list<br>
> <a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
> <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
<br>
<br>
--<br>
</div></div><a href="http://chilon.net/" target="_blank">http://chilon.net</a><br>
<div class="HOEnZb"><div class="h5">_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
<a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><br>
</div></div></blockquote></div><br></div>
</blockquote></div>_______________________________________________<br>Chat mailing list<br><a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>http://lists.lrug.org/listinfo.cgi/chat-lrug.org<br></blockquote></div><br></body></html>