<story><title>Things I do every time I start a Django project</title><url>https://brntn.me/blog/six-things-i-do-every-time-i-start-a-django-project/</url></story><parent_chain><item><author>xcambar</author><text>Tangent comment on JSX&amp;#x2F;TS&amp;#x2F;JS and a snippet found on reactivated.io. Not a comment on the article or reactivated.io in any way.&lt;p&gt;&amp;gt; export const Flavor = () =&amp;gt; &amp;lt;Select options={flavors} &amp;#x2F;&amp;gt;;&lt;p&gt;When I read the above, I fear for the new devs. The number of concepts to grasps and the level of parsing and mind bending to do is incredible.&lt;p&gt;I used to teach code, before arrow functions and React. And I am convinced I would have lost some students to this snippet, especially the &amp;quot;= () =&amp;gt;&amp;quot; segment.&lt;p&gt;Are we gone too far syntactically for the sake of compactness rather than understandability, allin the name of (fake, IMO) readability?</text></item><item><author>silviogutierrez</author><text>If you want a batteries-included, zero-config Django + React framework, check out &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reactivated.io&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reactivated.io&lt;/a&gt; .&lt;p&gt;It incorporates most of these best practices, along with React server side rendering in addition to regular Django templates.&lt;p&gt;Full disclosure: I&amp;#x27;m the creator.</text></item></parent_chain><comment><author>WorldMaker</author><text>Some of that shifts with syntax highlighting: drawing the eyes to which bits are more specifically related. The arrow =&amp;gt; should highlight as a single operator (just as &amp;gt;= does), for instance. Most people call these &amp;quot;arrow functions&amp;quot; so thinking of &amp;quot;=&amp;gt;&amp;quot; as the arrow operator is a habit that quickly builds.&lt;p&gt;They are controversial and everyone has different opinions, but I also think this is where programming ligatures come in extremely handy. When =&amp;gt; looks more like ⇒ and is even more obviously an arrow, I think that also starts to make it easier to visually &amp;quot;parse&amp;quot; the flow of code like that.&lt;p&gt;For what it is worth, arrow functions weren&amp;#x27;t added solely for compactness, but also to fix some historic issues with classic function syntax. (Lexically scoped `this` versus caller scoped `this` being the big one.) A new type of function syntax was desired anyway for those reasons, and the compact syntax was the icing on the cake.&lt;p&gt;I haven&amp;#x27;t had the pleasure of teaching such things to students at this point in my career, but I have given a hand to many a junior developer to grasping some of these ideas and I don&amp;#x27;t think it is that tough, though it can be a shock&amp;#x2F;surprise if the last JS you touched was many years before. Especially if you are trying to also learn what JSX and&amp;#x2F;or TSX add on top of all the changes in ES2015+.</text></comment>
<story><title>Things I do every time I start a Django project</title><url>https://brntn.me/blog/six-things-i-do-every-time-i-start-a-django-project/</url></story><parent_chain><item><author>xcambar</author><text>Tangent comment on JSX&amp;#x2F;TS&amp;#x2F;JS and a snippet found on reactivated.io. Not a comment on the article or reactivated.io in any way.&lt;p&gt;&amp;gt; export const Flavor = () =&amp;gt; &amp;lt;Select options={flavors} &amp;#x2F;&amp;gt;;&lt;p&gt;When I read the above, I fear for the new devs. The number of concepts to grasps and the level of parsing and mind bending to do is incredible.&lt;p&gt;I used to teach code, before arrow functions and React. And I am convinced I would have lost some students to this snippet, especially the &amp;quot;= () =&amp;gt;&amp;quot; segment.&lt;p&gt;Are we gone too far syntactically for the sake of compactness rather than understandability, allin the name of (fake, IMO) readability?</text></item><item><author>silviogutierrez</author><text>If you want a batteries-included, zero-config Django + React framework, check out &lt;a href=&quot;https:&amp;#x2F;&amp;#x2F;www.reactivated.io&quot; rel=&quot;nofollow&quot;&gt;https:&amp;#x2F;&amp;#x2F;www.reactivated.io&lt;/a&gt; .&lt;p&gt;It incorporates most of these best practices, along with React server side rendering in addition to regular Django templates.&lt;p&gt;Full disclosure: I&amp;#x27;m the creator.</text></item></parent_chain><comment><author>muspimerol</author><text>If you work with JSX daily, which 99% of React developers do, this is not hard to grok. It&amp;#x27;s a very typical functional composition pattern in React. Since this framework is targeted at those who want to use React, and presumably already use it, I don&amp;#x27;t see the issue. It&amp;#x27;s a snippet to show how Reactivated lets you use the React ecosystem, not &lt;i&gt;how to use React&lt;/i&gt; - that&amp;#x27;s what the docs are for.</text></comment>