<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Rishi Goomar on Medium]]></title>
        <description><![CDATA[Stories by Rishi Goomar on Medium]]></description>
        <link>https://medium.com/@rgoomar?source=rss-6e1db24b1a19------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*ySaUPjIyuhVExT3g.jpeg</url>
            <title>Stories by Rishi Goomar on Medium</title>
            <link>https://medium.com/@rgoomar?source=rss-6e1db24b1a19------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 14:21:50 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@rgoomar/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Installing League of Legends on Ubuntu 17.04]]></title>
            <link>https://medium.com/@rgoomar/installing-league-of-legends-on-ubuntu-17-04-47ffcbb437a9?source=rss-6e1db24b1a19------2</link>
            <guid isPermaLink="false">https://medium.com/p/47ffcbb437a9</guid>
            <category><![CDATA[gaming]]></category>
            <category><![CDATA[ubuntu]]></category>
            <category><![CDATA[linux-gaming]]></category>
            <dc:creator><![CDATA[Rishi Goomar]]></dc:creator>
            <pubDate>Wed, 10 Jan 2018 07:40:29 GMT</pubDate>
            <atom:updated>2018-01-10T20:02:27.990Z</atom:updated>
            <content:encoded><![CDATA[<p>I am a software engineer, but I also enjoy playing games. My game of choice is <a href="https://leagueoflegends.com/">League of Legends</a> (LoL), but my operating system of choice is something Linux-based like Ubuntu. I definitely prefer it over Windows or Mac as a development environment and the flexibility to customize the system as I see fit (I use i3wm as my window manager).</p><p>LoL doesn’t have a native Linux client and <a href="https://www.reddit.com/r/leagueoflegends/comments/66k4oo/riot_support_on_linux_client_hopefully_in_the/dgj8f34/">they don’t plan to support it</a> in the near future. Although, there is this <a href="https://www.change.org/p/riot-games-petition-to-support-league-of-legends-linux-client">petition</a> for it, I still want to play the game and there are a few solutions out there on how to get it to work on an Ubuntu (using 17.04 as of writing this) machine. I went through a bunch of different methods using PlayOnLinux, Wine hacks, etc., which had some issue or another that made it difficult to play. I finally got it working properly after I found this open gaming platform called <a href="https://lutris.net/">Lutris</a>.</p><h3>Check 3D Graphics Support</h3><p>First, you should make sure that you have the proper graphics driver installed and 3D support.</p><p>Check your graphics card:</p><pre>sudo lshw -c video</pre><p>Should output something like this:</p><pre>*-display               <br>       description: VGA compatible controller<br>       product: NVIDIA Corporation<br>       vendor: NVIDIA Corporation<br>       physical id: 0<br>       bus info: pci@0000:01:00.0<br>       version: a1<br>       width: 64 bits<br>       clock: 33MHz<br>       capabilities: pm msi pciexpress vga_controller bus_master cap_list rom<br>       configuration: driver=nvidia latency=0</pre><p>Check if your graphics driver has 3D acceleration support so you can actually play the game:</p><pre>/usr/lib/nux/unity_support_test -p</pre><p>Which should output something like:</p><pre>OpenGL vendor string:   NVIDIA Corporation<br>OpenGL renderer string: GeForce GTX 1060 3GB/PCIe/SSE2<br>OpenGL version string:  4.5.0 NVIDIA 384.111</pre><pre>Not software rendered:    yes<br>Not blacklisted:          yes<br>GLX fbconfig:             yes<br>GLX texture from pixmap:  yes<br>GL npot or rect textures: yes<br>GL vertex program:        yes<br>GL fragment program:      yes<br>GL vertex buffer object:  yes<br>GL framebuffer object:    yes<br>GL version is 1.4+:       yes</pre><pre>Unity 3D supported:       yes</pre><p>You want to make sure that the last one Unity 3D supported: is set to yes . Otherwise, depending on your graphics card, you will have to figure out the right way to get 3D support. Which, in my case, was going with the proprietary NVIDIA driver.</p><h3>Installing Lutris + LoL</h3><p>Lutris has some easy steps that you run in the terminal to install. You can see the installation steps <a href="https://lutris.net/downloads/">here</a>. The commands are listed below, but they are subject to change and the link in the previous sentence should be the reference to install (for Ubuntu 16.04, 17.04, 17.10):</p><pre>ver=$(lsb_release -sr); if [ $ver != &quot;17.10&quot; -a $ver != &quot;17.04&quot; -a $ver != &quot;16.04&quot; ]; then ver=16.04; fi</pre><pre>echo &quot;deb http://download.opensuse.org/repositories/home:/strycore/xUbuntu_$ver/ ./&quot; | sudo tee /etc/apt/sources.list.d/lutris.list</pre><pre>wget -q http://download.opensuse.org/repositories/home:/strycore/xUbuntu_$ver/Release.key -O- | sudo apt-key add -</pre><pre>sudo apt update</pre><pre>sudo apt install lutris</pre><p>Once installed, open up Lutris and click the card icon at the top left to browse games. That should open up a browser with the <a href="https://lutris.net/games/">Lutris Games list</a>. For the sake of speed, here’s the link to the <a href="https://lutris.net/games/league-of-legends/">LoL installer</a>. On that page, click the “Install” button shown below and that should prompt you to “xdg-open” which should use that install script on Lutris and get LoL going for you.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/926/1*_isU2xjOm6dC_oRL5ymH0Q.png" /><figcaption>Lutris - League of Legends Install</figcaption></figure><p>Once that is finished, follow the very simple GUI installer and you should have League of Legends on your machine ready-to-go! I personally added a desktop shortcut and launcher as an easy way to spin it up. Makes it so that “League of Legends” shows up as an app in my menu.</p><p>And… that’s it! You should be good-to-go to play LoL!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=47ffcbb437a9" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why I think Elm is the Future of Front End Development]]></title>
            <link>https://medium.com/@rgoomar/why-i-think-elm-is-the-future-of-front-end-development-21e9b091fa05?source=rss-6e1db24b1a19------2</link>
            <guid isPermaLink="false">https://medium.com/p/21e9b091fa05</guid>
            <category><![CDATA[elm]]></category>
            <category><![CDATA[functional-programming]]></category>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[software-development]]></category>
            <dc:creator><![CDATA[Rishi Goomar]]></dc:creator>
            <pubDate>Sat, 15 Oct 2016 23:30:47 GMT</pubDate>
            <atom:updated>2016-10-21T04:08:25.809Z</atom:updated>
            <content:encoded><![CDATA[<p><a href="http://elm-lang.org/">Elm</a> is a ML-style functional language with enforced immutability that compiles down to optimized JavaScript. It solves a lot of problems that developers writing JavaScript end up facing in a day-to-day workflow. I believe that it is going to be the future of front end development. I’ll be going over a few aspects of Elm that I think make it so powerful.</p><h3>“JavaScript Fatigue”</h3><p>I think that one of the biggest reasons to use Elm is to avoid trying to put together all the different libraries and tools to get a scalable JavaScript project going. There are constantly new libraries being released. I think that’s great and it shows that the ecosystem is vibrant, but I also believe it makes it hard to keep up with and build larger applications. Elm comes with everything you need to get started building a scalable front end.</p><h3>Architecture</h3><p>The concepts around the Elm architecture at its core are starting to be more widely used. For those of you familiar with <a href="http://redux.js.org/">Redux</a>, it is very similar to that. The Redux project has looked at Elm for <a href="http://redux.js.org/docs/introduction/PriorArt.html#elm">inspiration</a>. It is a simple architecture and the documentation does the best job of simplifying it:</p><blockquote>The logic of every Elm program will break up into three cleanly separated parts:</blockquote><blockquote><strong>Model</strong> — the state of your application</blockquote><blockquote><strong>Update</strong> — a way to update your state</blockquote><blockquote><strong>View</strong> — a way to view your state as HTML</blockquote><p>This architecture is being used by many companies like Prezi, NoRedInk, and CarFax. It allows for complex web applications to scale well and to be refactored easily. The best part is that this is already built-in to the platform. There is no need to setup a bunch of different libraries, you simply install the Elm CLI and start developing.</p><h3>Compiler</h3><p>Elm is a statically-typed language with type inference. The compiler is the biggest reason why companies working with Elm gets no run-time exceptions. It acts as a very friendly assistant for you while developing. Rather than going through a use case, let me just show you this:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/568/1*powKWHdOJP4v8fhekd_zug.png" /><figcaption>Elm Error Messages</figcaption></figure><p>As you can see from the message above, the compiler is extremely friendly and tells you that your code is missing the case of an empty array as a possible input. Messages like these force you to account for cases that are missed often in developing JavaScript applications which end up throwing some sort of “undefined is not a X” exception. This allows a developer to get very fast feedback on code and helps avoid issues as the application grows. Usually, these kinds of problems are caught during a code review or a test run of the application. Instead, with Elm, you don’t have to worry about forgetting those small cases.</p><p>Elm code is translated into efficient JavaScript code. There are constant changes coming to the JavaScript language and browser engines. Rather than having to worry about it and try to refactor your application, you can write your code in Elm and when newer versions of the language are released with compiler updates, you will potentially get more efficient JavaScript code.</p><p>I see a big opportunity here with <a href="http://webassembly.org/">WebAssembly</a>. Having Elm compile to WebAssembly as a target could help significantly improve the performance of an application. Quoting directly from this <a href="http://elm-lang.org/blog/farewell-to-frp">blog post</a>:</p><blockquote>I do not expect to be compiling to JavaScript forever, especially with WebAssembly on the horizon. The smaller the interface between Elm and JS, the easier it will be to support other platforms.</blockquote><p>Also — the compiler has even <a href="https://www.youtube.com/watch?v=wpYFTG-uViE">helped developers with ADHD</a> stay focused.</p><h3>Performance</h3><p>Elm has always done well with performance due to its compilation to efficient JavaScript and use of the virtual dom model. Many companies currently using Elm have not had to compromise performance for productivity. It just comes built in.</p><p>You can see the benchmarks that were run back in <a href="http://elm-lang.org/blog/blazing-fast-html">July 2014</a> and more recently in <a href="http://elm-lang.org/blog/blazing-fast-html-round-two">August 2016</a>. They are pretty impressive and I have not read a single account of poor performance from the companies using it in production.</p><h3>Package System</h3><p>The package system is one of the most interesting aspects of the Elm ecosystem. It has one feature that isn’t anywhere else (from my knowledge) — it <strong>enforces semantic versioning based on the changes to your package</strong>. The system can tell if the package is making a breaking change and not allow for the minor version to be bumped and requires the major version bump to publish. <strong>This is powerful</strong>. There have been numerous accounts of issues in the JavaScript space of package creators publishing new versions of a package that is a minor or patch that actually end up breaking API contracts. That causes many issues and can lead to a refactor or having to change code that you were not expecting to modify. That can be avoided with how smart the Elm package system is. I think it could even be used as a tool to teach people how semantic versioning works in practice.</p><p>To quote directly from their homepage:</p><blockquote>Elm can detect all API changes automatically thanks to its type system. We use that information to force everything in <a href="http://package.elm-lang.org/">our package catalog</a> to follow <a href="https://github.com/elm-lang/elm-package/#version-rules">semantic versioning</a> precisely. No more surprises in PATCH releases!</blockquote><p>There are currently about 554 packages. This was calculated by going to package.elm-lang.org and running the following in the console:</p><pre>document.querySelectorAll(&#39;.pkg-summary&#39;).length;</pre><p>It is growing and I really like the <a href="http://package.elm-lang.org/help/design-guidelines">guidelines</a> for creating and publishing a package.</p><h3>Success Stories</h3><p>A Swedish startup that decided to <a href="https://medium.com/the-ahead-story/move-fast-and-dont-break-things-running-a-startup-on-elm-b5491082fe8b#.7r0m8byem">use Elm from the beginning</a> for their project and they describe the benefits and output of that decision.</p><p>NoRedInk has been using Elm in production for over a year now (if my math is right). They talked about the experience of <a href="https://youtu.be/R2FtMbb-nLs">running it in production for 6 months</a> back in February.</p><p>Futurice used it and wrote up their <a href="http://futurice.com/blog/elm-in-the-real-world">success around using Elm</a> and how it helped their code base.</p><h3>Conclusion</h3><p>Elm is definitely on the right track. I think that if you are trying to figure out what to use for your next project, you should give Elm a try. You can even use it with existing projects due to the interoperability with JavaScript. It has a lot of benefits and lasting positive effects on a team and code base.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=21e9b091fa05" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Meteor Newsletter]]></title>
            <link>https://medium.com/@rgoomar/new-meteor-newsletter-b3fa414c61a7?source=rss-6e1db24b1a19------2</link>
            <guid isPermaLink="false">https://medium.com/p/b3fa414c61a7</guid>
            <category><![CDATA[newsletter]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[meteor]]></category>
            <dc:creator><![CDATA[Rishi Goomar]]></dc:creator>
            <pubDate>Sun, 25 Oct 2015 20:33:10 GMT</pubDate>
            <atom:updated>2015-10-25T20:33:10.410Z</atom:updated>
            <content:encoded><![CDATA[<p>For a long time now, I have been writing and managing <a href="http://thisweekinmeteor.com/">This Week in Meteor</a>. It is a Differential product and I have been the primary source for the content behind it. Unfortunately, I will no longer be writing for that newsletter.</p><h4>Why?</h4><p>Sometimes we come to a point where we want to venture down an alternative path on a project. In order to make choices like that it’s often easier when you control all aspects of what you’re working on yourself and a simple way to work around differences in opinion. This was the case with This Week in Meteor.</p><p>This Week in Meteor will still continue without me, and I encourage you to stay on the list to see where it will go from here.</p><h4>Moving Forward</h4><p>I will still be writing an awesome weekly curated analysis of Meteor news every week, <a href="http://meteorweekly.com/">Meteor Weekly</a>. If you are still interested in seeing what I have to write and have it delivered to your inbox every week, feel free to subscribe to <a href="http://meteorweekly.com/">Meteor Weekly</a> and follow on twitter <a href="https://twitter.com/WeeklyMeteor">@WeeklyMeteor</a>.</p><h4>Shout Outs</h4><p><a href="https://twitter.com/arunoda">Arunoda Susiripala</a> — “Meteor Weekly” name and domain<br><a href="https://twitter.com/KarlDanninger">Karl Danninger</a> — Logo Design<br><a href="https://twitter.com/joshowens">Josh Owens</a> — For pushing me</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=b3fa414c61a7" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>