<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman",serif;}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}
.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}
@page WordSection1
{size:612.0pt 792.0pt;
margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang="EN-GB" link="blue" vlink="purple">
<div class="WordSection1">
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">Hi All,<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US">We do a lot of recruitment for Ruby in the South East, most used / in demand is React then Angular or Ember
<o:p></o:p></span></p>
<p class="MsoNormal"><span style="font-size:11.0pt;font-family:"Calibri",sans-serif;color:#1F497D;mso-fareast-language:EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif">From:</span></b><span lang="EN-US" style="font-size:11.0pt;font-family:"Calibri",sans-serif"> Chat [mailto:chat-bounces@lists.lrug.org]
<b>On Behalf Of </b>Tom Cartwright<br>
<b>Sent:</b> 13 June 2016 11:00<br>
<b>To:</b> Let me in... <chat@lists.lrug.org><br>
<b>Subject:</b> Re: [LRUG] Is turbolinks/jQuery still the dominant front-end approach with Rails devs?<o:p></o:p></span></p>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">Until recently, at Lost My Name we were using a collection of small jquery-based libs to provide validation, dom manipulation and the odd api call. We just had standard rails views and the occasional json endpoint. We didn't use the jquery-ujs
or any of the javascript helpers. I tried to use them once but I was sentenced to a solid week of tea duty.<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">The jquery approach worked well but as our storefront grew more complex it was very hard to hold state and update views with state changes. We have replaced the front-end with a nodejs app that runs React/redux, with the magic isomorphic
(I think the kids call universal these days) rendering on the server that everyone wants, allowing it to work without js on the client. I have not had much to do with the project but I have observed higher levels of developer happiness and the website seems
to be up so thats two ticks in it's favour.<o:p></o:p></p>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<div>
<p class="MsoNormal">Tom<o:p></o:p></p>
</div>
</div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<p class="MsoNormal">On Mon, Jun 13, 2016 at 10:20 AM, Jon Wood <<a href="mailto:jon@ninjagiraffes.co.uk" target="_blank">jon@ninjagiraffes.co.uk</a>> wrote:<o:p></o:p></p>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<div>
<p class="MsoNormal">I think Javascript feels pretty bleeding edge all the time to me, simply because everything is in a constant state of flux. Maybe I just need to stop chasing the new shinyness, but whenever I start a new project with React I end up relearning
half of what I did last time because its changed again.<o:p></o:p></p>
</div>
<div>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
<div>
<div>
<p class="MsoNormal">On Mon, 13 Jun 2016 at 10:14 Sleepyfox <<a href="mailto:sleepyfox@gmail.com" target="_blank">sleepyfox@gmail.com</a>> wrote:<o:p></o:p></p>
</div>
<blockquote style="border:none;border-left:solid #CCCCCC 1.0pt;padding:0cm 0cm 0cm 6.0pt;margin-left:4.8pt;margin-right:0cm">
<p class="MsoNormal">Interesting - React (the newest of the frameworks) is already more<br>
than 3 years old. Others (Angular, Ember et al) are much older. At my<br>
current client they're using React with Rails, and don't consider that<br>
at all 'new' let alone 'bleeding edge'.<br>
<br>
Modern work is moving to API+SPA, with the API in Ruby, Node or even<br>
#serverless using Firebase or similar.<br>
<br>
Is the Ruby community really this behind?<br>
<br>
@sleepyfox<br>
<br>
<br>
On 13 June 2016 at 10:04, Jon Wood <<a href="mailto:jon@ninjagiraffes.co.uk" target="_blank">jon@ninjagiraffes.co.uk</a>> wrote:<br>
> I would say that it depends on the scale of your frontend at the moment. If<br>
> you're building a web app which can function with just some generated HTML<br>
> and the odd sprinkle of Javascript then jQuery is probably the way to go as<br>
> you get all the benefits of Rails' gem ecosystem and years of tooling to<br>
> build HTML quickly.<br>
><br>
> If you're building a rich application then you'll probably want the extra<br>
> structure provided by something like React or Ember, but you'll pay the<br>
> price in initial bootstrapping of your application, and being somewhat on<br>
> the bleeding edge. You do get the advantage of a proper API backing<br>
> everything though, which pays off rapidly as your application gets larger.<br>
><br>
> Finally, there's the option of having a REST API, and a Rails generated<br>
> interface built on top of that. If you're web application is the only API<br>
> client then I'm not sure I'd recommend that approach. If you need an API for<br>
> other clients anyway then this can be a really nice way of working because<br>
> every feature you build for any client requires API endpoints which can<br>
> quite dramatically reduce the overheads in supporting the feature for other<br>
> clients.<br>
><br>
> On Mon, 13 Jun 2016 at 09:47 gvim <<a href="mailto:gvimrc@gmail.com" target="_blank">gvimrc@gmail.com</a>> wrote:<br>
>><br>
>> Is turblinks/jQuery still the dominant approach to front-end development<br>
>> in the Rails community or is there a shift towards Ember/Angular/React<br>
>> backed by a Rails api?<br>
>><br>
>> gvim<br>
>><br>
>> _______________________________________________<br>
>> Chat mailing list<br>
>> <a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br>
>> Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">
http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
>> Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
>> List info: <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>
> Chat mailing list<br>
> <a href="mailto:Chat@lists.lrug.org" target="_blank">Chat@lists.lrug.org</a><br>
> Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">
http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
> Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
> List info: <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" target="_blank">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">
http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><o:p></o:p></p>
</blockquote>
</div>
</div>
</div>
<p class="MsoNormal" style="margin-bottom:12.0pt"><br>
_______________________________________________<br>
Chat mailing list<br>
<a href="mailto:Chat@lists.lrug.org">Chat@lists.lrug.org</a><br>
Archives: <a href="http://lists.lrug.org/pipermail/chat-lrug.org" target="_blank">
http://lists.lrug.org/pipermail/chat-lrug.org</a><br>
Manage your subscription: <a href="http://lists.lrug.org/options.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/options.cgi/chat-lrug.org</a><br>
List info: <a href="http://lists.lrug.org/listinfo.cgi/chat-lrug.org" target="_blank">
http://lists.lrug.org/listinfo.cgi/chat-lrug.org</a><o:p></o:p></p>
</blockquote>
</div>
<p class="MsoNormal"><br>
<br clear="all">
<o:p></o:p></p>
<div>
<p class="MsoNormal"><o:p> </o:p></p>
</div>
<p class="MsoNormal">-- <o:p></o:p></p>
<div>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif">Tom Cartwright</span><o:p></o:p></p>
<div>
<p class="MsoNormal"><span style="font-size:10.0pt;font-family:"Arial",sans-serif"><a href="http://tecartwright@gmail.com/" target="_blank"><span style="background:white">tecartwright@gmail.com</span></a><span style="color:#474747;background:white"> 07969 977300
<a href="http://www.tomcartwright.net" target="_blank">Portfolio</a> </span><span style="color:#474747">·
<span style="background:white"><a href="http://github.com/tomcartwrightuk" target="_blank">GitHub</a></span></span></span><span style="font-family:"Arial",sans-serif;color:#474747"> ·
</span><a href="https://www.linkedin.com/in/tomcartwrightuk" target="_blank"><span style="font-family:"Arial",sans-serif">LinkedIn</span></a><o:p></o:p></p>
</div>
</div>
</div>
</div>
</div>
</body>
</html>