<?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 HolyJS on Medium]]></title>
        <description><![CDATA[Stories by HolyJS on Medium]]></description>
        <link>https://medium.com/@HolyJSconf?source=rss-91eaadf816c8------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*k6IxiyQOC9vyuSHF.jpg</url>
            <title>Stories by HolyJS on Medium</title>
            <link>https://medium.com/@HolyJSconf?source=rss-91eaadf816c8------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 08:33:32 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@HolyJSconf/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[“No one would tell to someone else what they should do”: Nicolò Ribaudo on developing Babel and…]]></title>
            <link>https://medium.com/@HolyJSconf/nicolo-ribaudo-984b4dc917bc?source=rss-91eaadf816c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/984b4dc917bc</guid>
            <category><![CDATA[holyjs]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[nicolò-ribaudo]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[HolyJS]]></dc:creator>
            <pubDate>Wed, 06 Nov 2019 10:19:11 GMT</pubDate>
            <atom:updated>2019-11-06T13:44:01.860Z</atom:updated>
            <content:encoded><![CDATA[<h3>“No one would tell someone else what they should do”: Nicolò Ribaudo on developing Babel and other things</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*qyyg0a-RppmTVgQrdRyAQA.jpeg" /></figure><p><em>Nicolò Ribaudo is both a core Babel developer and a TC39 invited expert — while also being a mathematics student.</em></p><p><em>He’ll give a </em><a href="https://holyjs-moscow.ru/2019/msk/talks/7msh8nbogriz7o8ttedise/?utm_source=medium&amp;utm_medium=ribaudo&amp;utm_campaign=holyjs19msc"><em>talk</em></a><em> soon at HolyJS 2019 Moscow. In anticipation of that, HolyJS program committee members Dmitry Makhnev and Eugene Kot asked him about developing Babel, being an invited expert, studying, coming to conferences… and finding time to sleep.</em></p><p><strong>Eugene:</strong> Let’s start with a simple question. Could you please tell us about yourself, what you’re doing?</p><p><strong>Nicolò:</strong> I have been developing Babel for two years. I study math, and I started the second year a few weeks ago. Programming and studying are how I spend most of my time; I have been programming for ten years now, and JavaScript is my favorite language. I think that I’ve started contributing to open source thanks to JavaScript, and it was a few years ago.</p><p><strong>Eugene:</strong> Right now you are working with the Babel core team and that’s pretty impressive because majority of the JavaScript products all around the world use Babel in the everyday work cycle. So, how did you join the team?</p><p><strong>Nicolò:</strong> I started contributing because I used Babel, and I wanted to do something for the community. When I first approached the open source community, I contributed to some other projects and then learned about Babel, and I was interested in it. Actually, there was another reason, which is a bit selfish: I wanted to become famous! I wanted to work on something that many people know. But then I understood the real reason why people work on open source, and I just continued because I loved it.</p><p><strong>Eugene:</strong> But why Babel? There are a lot of other open source projects all around the world.</p><p><strong>Nicolò:</strong> Before Babel, I contributed to JSHint, and I liked it. I learned about parsers. And this was one of the reasons Babel got my attention. In fact, I started contributing not to the transformer, but I started contributing to the Babel parser. And I already knew about this project, because I used it for some personal projects and I’ve thought that it was a good idea to start.</p><p><strong>Eugene:</strong> Right now, you are studying math, and it’s a pretty complicated thing. And open source is not so easy to do. So how did you combine all these things together? Do you have 30 hours in a day or what?</p><p><strong>Nicolò:</strong> I mean, last year it wasn’t that hard, because I studied like 20 hours per week and then I had a lot of free time. Now it’s a little harder because I study 30 hours a week. And I want to work at least 20 hours per week on open source projects. I must do it during evening and night, or in the weekends.</p><p><strong>Eugene:</strong> So you don’t sleep at all?</p><p><strong>Nicolò:</strong> After dinner I work maybe three hours or four hours. I’m trying not to overwork. But sometimes it’s hard because if you are solving a problem, and if you are having fun doing it, you have to force yourself to stop, to stay awake the day after.</p><p><strong>Eugene:</strong> How is it regulated from the Babel side? I mean, do you have some backlog, or you can do anything you want… how does it work?</p><p><strong>Nicolò:</strong> We don’t have a strict organization. We try to set up some roadmaps, but we mostly decide ourselves what we need to do. For example, we choose some issues to focus on for the next release, and everyone can work on any of those issues.</p><p><strong>Eugene:</strong> There always will be super cool feature requests. And there also always will be something boring that nobody wants to do. How to mix that? Do you have, I don’t know, a product manager who decides what should be done in the next week or month?</p><p><strong>Nicolò:</strong> We have a meeting every two weeks, and during these meetings, if there’s something to do that isn’t that much interesting, we usually decide how we should approach it. For example, one of the most boring tasks is triaging all the issues: we have like 700 open issues and many of them are not valid anymore. Maybe they are already fixed, or perhaps they were a problem in the user configuration. And we try to triage them anyway, maybe once a month or once every two weeks. No one would tell someone else what they should do: we only “impose” those tasks to ourselves.</p><p><strong>Dmitry:</strong> Will you work on Babel as a full-time job after your education?</p><p><strong>Nicolò:</strong> We are trying to understand if we have enough money in our Open Collective so that another person in the team or I can start working part-time already this year and be paid. Since we’re dedicating a lot of time to the project, it would be really cool to consider it an actual job. Even if we find out that it isn’t possible to have other people working part-time or full-time on Babel, I’d like to work on open-source projects anyway after university.</p><p><strong>Eugene:</strong> I’m not familiar with this Open Collective scheme… Do you have donations and some money, and the team decides who will work as a full-time developer, and who will work part-time?</p><p><strong>Nicolò:</strong> This is a difficult topic and we usually discuss it for hours, maybe without finding a conclusion. Currently, Henry is the only person working on Babel full-time. And it’s also because he was the first person being able to do so , and he is the one who has been a maintainer for the longest time. But now we are trying to understand if there are other people in the team who have the time to work on Babel and actually want to work.</p><p>Working on this kind of projects, funded by the community, can be hard: if you work for a regular company, you always have the same salary, and it’s guaranteed that you’ll get it. But since we rely on donations, it’s hard to make important life decisions, because there is an inherent risk. It’s hard to find people who want to work full-time or part-time on it and that we trust, so there isn’t a lot of competition inside the team. The main problem is finding money for the few people who would like to do it.</p><p><strong>Eugene:</strong> You had raised some money from your Open Collective, and you decided that this person should work fulltime, but what would be the salary? Who’s deciding that?</p><p><strong>Nicolò:</strong> We don’t know yet. It’s a hard problem to solve, because we have to decide how much we should be paid together. Also, no one wants to track time so an hourly salary doesn’t work. And you can’t pay people based on how much they do because there are some long-term tasks, maybe dull tasks, which don’t produce a lot of visible value. For example, it’s triaging issues or helping people in our Slack. Thus, we would like to decide a monthly salary but it’s really hard to determine how much it should be. Also, because we are in different parts of the world and something that may seem a lot to me may seem a tiny salary to someone else. It’s really hard.</p><p><strong>Eugene:</strong> Yeah, that’s true! But you said that after the university, after graduation, you will work on open source. But all these financial and other things… On the other side, there are a lot of good commercial companies like Google or Apple, and they pay a lot. What do you think about that? Working in a big super-international company may have some advantages and disadvantages.</p><p><strong>Nicolò:</strong> It’s possible to do both because there are many companies with big open source projects. You can work for a big company and for an open source project at the same time. I don’t know if I will work for one of them. I don’t need a lot of money now, but I’ll need to find a job after university.</p><p><strong>Dmitry:</strong> As far as I know, you’re an invited expert in the TC39. And I was really impressed when Sergey Rubanov told me that there are just 20 invited experts. Could you please tell us how you became one of them?</p><p><strong>Nicolò:</strong> An invited expert is a role for people who either have a lot of knowledge about a specific topic, or who are helping with many proposals, or who are helping TC39 within the community. I am an invited expert because of my role in Babel. I have been working on all the class-related proposals (like decorators or class fields). I also have to analyze many other proposals to implement them in Babel and to help external contributors implementing them.</p><p>I have participated in a TC39 meeting only once, but I would love to help TC39 in the future as much as I can.</p><p><strong>Dmitry:</strong> Sounds really interesting. Do you want to join TC39 as a delegate in the future?</p><p><strong>Nicolò:</strong> Maybe. TC39 isn’t for individuals: you usually have to work in a company, and that company should join TC39. But if I will work for a company which is a TC39 member, I would like to help and become a delegate.</p><p><strong>Eugene:</strong> Why do you think of joining TC39, and why working with them is important to you?</p><p><strong>Nicolò:</strong> It’s because I love JavaScript and I really like helping moving it forward. It would be another way to help improving JavaScript. We should make it for the community, and listen to people to make JS a language which is better for everyone.</p><p><strong>Dmitry:</strong> What do you think, is a university education that necessary to be a successful developer nowadays?</p><p><strong>Nicolò:</strong> I don’t think so. I’m not studying computer science and I don’t think that I will. I have been programming since way before joining the university. And I’ve joined the active Babel team when I still was in high school. There are many other people I know who are young and don’t have a computer science degree but are great developers, and they can have good jobs.</p><p><strong>Eugene:</strong> But still a higher education and university can give you something for your job, for your development career or something like that. Why did you join the university to study math?</p><p><strong>Nicolò:</strong> I agree that a university can give you something more, but I think that you can manage to become a successful developer even without it. I decided to study math because I like math. And it has been my favorite subject since I was about ten years old. I have not chosen math because I need it, but because I like it.</p><p>If I had to choose a university depending on what I need, I would probably have chosen computer science. On the other hand, if you like to learn, university is one of the best ways to do so.</p><p><strong>Dmitry:</strong> If you love math, why did you choose JavaScript as your primary language? Why didn’t you choose Haskell or languages used for ML/data science?</p><p><strong>Eugene:</strong> Yeah, because the math is more about machine learning, all these complicated things. Many people at least in my environment think that JavaScript is about front-end, buttons, divs, it’s not for the scientists and mathematicians.</p><p><strong>Nicolò:</strong> I started programming in JavaScript because I have an aunt who teaches web development. When I wanted to learn about computers, I asked her, and that was one of the languages that she suggested to me. And then, I continued to use JS because… I remember that the first program I wrote was a browser extension to cheat in an online game I was playing at the time, and JavaScript was the only language that would allow me to do so.</p><p>I actually have learned a bit of Haskell, and I like it. I really like the fact that it’s similar to math. But I have never learned it enough to be able to create big applications. I think that the reason I like JavaScript is because I started learning it a long time ago, and thus it’s the language I know best.</p><p><strong>Dmitry:</strong> What do you think about solving your everyday problems with any programming languages? Can it be considered as the best way for programming education in general, for future work or something?</p><p><strong>Nicolò:</strong> I don’t really know a lot about education in programming. Usually, students don’t think about how to teach something, they just want teachers to teach them. I think we in Babel are in the position to help make it easier to teach JavaScript to beginners. For example, we talked about making it possible to translate JavaScript into the other human languages, so that if, for example, you are Russian, you could just write “если” instead of “if”. We didn’t do it yet, and I don’t know if we will do it in the future, but it’s an example of how we can lower the entry barrier for programming.</p><p><strong>Dmitry:</strong> Is knowledge of math required for JavaScript development?</p><p><strong>Nicolò:</strong> It depends on the type of applications you work on. I think that most of the JavaScript applications don’t need math or only need a tiny bit of that. If you’re doing web design, you might need like sin and cos, and that’s all. I think that there are other languages where you need math much more: if you are working on machine learning or data science, which usually do not use JavaScript, you need to know more math. But if you are building a Node server or a client-side application, probably you don’t need it.</p><p><strong>Eugene:</strong> How do you learn? We know that you are studying in the university, but maybe outside of it, all these things like podcasts, talks, videos, meetups, or articles…</p><p><strong>Nicolò:</strong> I mostly learn by reading online blog posts or just documentation of a library or a language. I’ve never really used videos or podcasts because I find it hard to listen to it for more than an hour. As I said before, when I was young, I had an aunt who taught me the basics of programming. Later, I started studying everything by myself. I used to have different blogging platforms like Medium installed on my smartphone. I had to remove them because I spent too much time reading programming tutorials or explanations of new things rather than focusing on what I had to do.</p><p><strong>Eugene:</strong> What do you think about offline sources like meetups or conferences? Do you attend them? What do you think?</p><p><strong>Nicolò:</strong> I don’t really know the JavaScript community in my city. I think I attended a meetup only once or maybe two times. And I was at conference for the first time a few months ago. I’d really love to get in touch with my local community, but when I tried, I found out that I was the only person who was less than 20. And I felt like it wasn’t really my place. But I mean, I will try again in the future and let’s see if it goes well.</p><p><strong>Eugene:</strong> So, do you think there is ageism in the community? Is everyone younger than 20 treated like a junior?</p><p><strong>Nicolò:</strong> If you see that all other people around are ten years older than you, you may feel like you’re not in the right place. I mean, usually, young people don’t hang out with much older people. I think that when we get older, it will be easier. I have always only been with people about my age, so it was an absolutely different environment for me. But I’ve never been told that I couldn’t attend or that it wasn’t my place because I was too young, no one ever questioned my abilities because of my age.</p><p><strong>Eugene:</strong> Many offline events like meetups, conferences, workshops are not about only knowledge but about networking too. What do you think about networking in general? I mean, to meet new people, to know local communities…</p><p><strong>Nicolò:</strong> I think that networking is important, especially because it can help you find a job or know other people who share the same interests. Currently, I haven’t felt the need to connect people offline in my city because I already study and work in Babel, and I haven’t much time for meeting new people. Also, I’m trying to get someone new to contributors involved with Babel and show them that even if it’s a popular project everyone can contribute.</p><p><strong>Eugene:</strong> Have you ever attended offline meetings of the Babel team?</p><p><strong>Nicolò:</strong> I have met part of the team once in Berlin at JSConf. It wasn’t the whole team, but a big part of the active contributors. And it’s been a perfect experience because I have always talked with these people online. We did already met each other on video calls, but meeting them in person was great.</p><p><strong>Dmitry:</strong> It’s the first time you’re in Russia. What do you expect from visiting Russia?</p><p><strong>Nicolò:</strong> Oh, when I travel, I try not to have too many expectations. I think that if I don’t have an expectation, I can be more surprised and enjoy it more. Also, it’s because the only thing I already know about Moscow is that a friend of mine suggested a bar where to go. He’s not living in Moscow now, he moved to Italy one year ago or so. Maybe it was just next to his home. Well, I try not to have expectations because I’m just going to enjoy it and see how it really is.</p><p><strong>Dmitry:</strong> I hope we’ll visit that bar! By the way, what do you expect from HolyJS?</p><p><strong>Nicolò:</strong> I expect to have a lot of fun meeting people. To meet people, to talk about Babel, to try to get them interested in what it is — it’s the most fun. I think every conference should make it possible to connect with people. From a speaker’s point of view, I just hope that everything goes well.</p><p><strong>Dmitry:</strong> Of course it’ll go well, we are working on this!</p><p><em>Nicolò will give a talk “</em><a href="https://holyjs-moscow.ru/2019/msk/talks/7msh8nbogriz7o8ttedise/?utm_source=medium&amp;utm_medium=ribaudo&amp;utm_campaign=holyjs19msc"><em>@babel/how-to</em></a><em>” at HolyJS 2019 Moscow on November 8.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=984b4dc917bc" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[HolyJS 2019 Piter Recap]]></title>
            <link>https://medium.com/@HolyJSconf/holyjs-2019-piter-recap-105072ebc07d?source=rss-91eaadf816c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/105072ebc07d</guid>
            <category><![CDATA[holyjs]]></category>
            <category><![CDATA[conference]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[HolyJS]]></dc:creator>
            <pubDate>Mon, 29 Jul 2019 02:42:48 GMT</pubDate>
            <atom:updated>2019-07-29T02:42:48.783Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*5dPTr9v56MTYTFWbZqenpg.jpeg" /></figure><p>At the end of May 2019, the 7th HolyJS conference took place — we believe it to be the best one yet. We’ve collected and analyzed the feedback, and now it’s time to show the recap. Here are the statistics:</p><p>— 900+ JS developers, 2 days of talks, 3 tracks</p><p>— 30 talks, 2 workshops</p><p>— 36 speakers</p><p>— 3 MCs</p><p>— 10 lightning talks</p><p>— 3 BOF sessions</p><p>— TCXX competition with the aid of <a href="https://twitter.com/littledan">Daniel Ehrenberg</a> (former TC39 Chairman)</p><p>— The first showing of a documentary about Ember.js in Russia</p><p>— A fellow event — Node.js Code+Learn (first of its kind in post-USSR states)</p><p>It was the second HolyJS where all the tickets were sold out, a month before the conference. Honestly, we didn’t expect that! On the one hand, it’s a legitimate success: it means more people than we thought were interested in the conference. But on the other hand, some people that did want to attend couldn’t do so, and for others the venue might have felt cramped.</p><p>We’d like to apologize to everyone who felt uncomfortable. Rest assured, this time we’ll take it into consideration: <a href="https://holyjs-moscow.ru/en/">the next <strong>HolyJS</strong></a> will take place in WTC Congress Center in Moscow, which is able to hold more than 1000 people. And in St. Petersburg HolyJS will take place in Expoforum — it can hold as many as 10 000 people, if needed.</p><h3>Program</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YVL_tHZYQDIrITZbVZTxXA.jpeg" /><figcaption>Ryan Dahl</figcaption></figure><p>As always, there were two days and three tracks of talks. We already know which talks the audience deemed the most interesting, so let’s take a look at some of them:</p><p>— <strong>Ryan Dahl</strong> (you probably know him as creator of Node.js) opened the conference with a talk about <a href="https://github.com/denoland/deno">Deno</a>, his new project. We broadcasted the first track of the first day on YouTube so everyone could watch <a href="https://youtu.be/YDBE7OM7-mM?t=4000">the video</a> right away — and now you can watch it yourself instead of reading descriptions.</p><p>— <strong>Martin Splitt</strong>, who can call himself a half-Russian (because he spoke at all the biggest Russian conferences and has learned so many Russian words, including swear-words, alas), lifted the veil of secrecy over the Google search algorithms. In our age of SPA and React, there may be a feeling that the long-forgotten art of search engine optimization has already been lost. Well, Martin showed us that even in the world of large applications and JavaScript there is still a place for magic. Here’s the <a href="https://www.youtube.com/watch?v=XF08jiOKaiQ">video</a>.</p><p>— The great duet from Progress team — <strong>Stanimira Vlaeva</strong> and <strong>Vladimir Mutafov</strong>. They talked about the bridge between Javascript and native code implemented in NativeScript. One more great example of how JS can be used at the junction of different technologies. That was the case when these core developers were able to explain complex things in simple way. You can <a href="https://www.youtube.com/watch?v=sQ8UyltZGRQ">see for yourself</a>.</p><p><strong>— </strong>For <strong>Michel Weststrate</strong> (of MobX fame) it was his second HolyJS. Previously at HolyJS 2018 Moscow he had presented a <a href="https://www.youtube.com/watch?v=JKaJ9r3xYN4">talk</a> “State management beyond the libraries”. This time the topic was “MobX and the unique symbiosis of predictability and speed”, and Michel dived deep into the design principles and implementation details of MobX. In what ways is it fundamentally different from its predecessors? What makes it so insanely fast? Most importantly, you’ll discover that predictability and speed are not competing concerns but rather catalysts for each other. Here’s the <a href="https://www.youtube.com/watch?v=NBYbBbjZeX4">video</a>.</p><p>— <strong>Lucas da Costa</strong> was also present at both HolyJS 2018 Moscow and HolyJS 2019 Piter. Last time he amazed the public with his <a href="https://www.youtube.com/watch?v=rqZuNAjT2nI">talk</a>: it is not every day that you hear so structured a well-developed talk about such a difficult topic as Y Combinator. Many people were shocked with his typing skills in vim editor. No wonder, because he even has a <a href="https://pbs.twimg.com/media/DY65vJAW0AEfF-h.jpg">“:w” tattoo</a>! So this time he had a difficult task: to talk about something equally difficult, and to do it just as elegantly and easily.</p><p>And he did it! Earrtlier this year his talk was about recursion, and not only he did explore the very concept of recursion and its mathematical origins but also showed how we can implement it without any explicit support, live-coding the Y combinator. The video recording is <a href="https://www.youtube.com/watch?v=FukpDL4-KOg">here</a>.</p><p><strong>— </strong>What comes to mind if you hear the phrase “state machine?” As a modern frontend developer you may be imagining something like Tesla with big Redux sticker? <strong>David Khourshid</strong> showed us how wonderful things can be done with finite state machines (FSMs). As the number of possible states in an app grows, developing UIs can become exponentially more complex. With the help of FSMs it’s possible to manage an app’s states in a simple, robust way, and even visualize them. *SPOILER* (It does not have to be Redux). Here’s the <a href="https://www.youtube.com/watch?v=o84Xw8qiTCw">video</a> of David’s talk.</p><p>There were <a href="https://holyjs-piter.ru/en/#schedule">many other</a> talks as well; videos of them will be published later.</p><p>We usually prepare several “reserve” talks in case of a last-minute change in our program. This time two speakers, <strong>Roman Kolesnikov</strong> and <a href="https://twitter.com/Farzad_YZ"><strong>Farzad YousefZadeh</strong></a>, were in reserve, and we are very grateful to them for their willingness to back the conference up. They hadn’t had a chance to give their talks in St. Petersburg, but their efforts were not in vain: Farzad will come to HolyJS 2019 Moscow this autumn to give his talk, “Statecharts-driven UI development”.</p><h3>Workshops</h3><p>This was probably the toughest experiment of this HolyJS: preparing a workshop took 5–10 times more time than preparing a talk. There were two workshops (one per day), both in Russian, each 2–3 hours long; they were taking place as the fourth track, in parallel to the talks.</p><p>The first day, <strong>Stas Kurilov</strong> showed us how to remove redundant code from CSS Modules runtime, using webpack — you can <a href="https://www.youtube.com/watch?v=J1gHHmABk44">watch it here</a>.</p><p>And the second day, <strong>Pavel Malyshev</strong> conducted a workshop on Svelte — Svelte Cookbook. He started with greeting from <a href="https://twitter.com/Rich_Harris">Rich Harris</a>: for the workshop participants Rich recorded an <a href="https://www.youtube.com/watch?v=I5DIcbcXzfE&amp;feature=youtu.be&amp;t=96">exclusive short video</a>. <a href="https://www.youtube.com/watch?v=I5DIcbcXzfE">The recording</a> of the workshop itself can’t exactly be called short, though: it lasts for more than three hours.</p><h3>MCs</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*Wu9BfU2W8kudGfAa" /><figcaption>Three MCs and Martin Splitt</figcaption></figure><p>Aside from the content, which was the main part, this time we also experimented with presenting the talks. This experiment involved three awesome MCs: <a href="https://twitter.com/smashingmag">Vitaly Friedman</a>, <a href="https://twitter.com/webmaxru">Maxim Salnikov</a> and <a href="https://twitter.com/bunopus">Evgeny Kot</a>. You can see for yourself how they <a href="https://youtu.be/YDBE7OM7-mM?t=3852">opened the first day</a> (in Russian) before Ryan Dahl came onstage. We’d like to thank the MCs very much for the wonderful mood they created and for the <a href="https://youtu.be/YDBE7OM7-mM?t=7424">engaging QA sessions</a>.</p><h3>Activities</h3><p><a href="https://github.com/HolyJS-TCXX/HolyJS-Piter-2019-TCXX">TCXX</a> competition for the best proposal to JS standard has already become a common practice. But this time it involved something new, too: three distinguished people came to help us choose the winner. They were the former TC39 Chairman <a href="https://twitter.com/littledan">Daniel Ehrenberg</a>, <a href="https://twitter.com/ak_239">Aleksey Kozyatinskiy</a>, and <a href="https://twitter.com/chicoxyzzy">Sergey Rubanov</a>, who just only a week after the conference <a href="https://t.me/juliarderity/585">left</a> for Berlin, for the <a href="https://github.com/tc39/agendas/blob/master/2019/06.md">June meeting</a> of the TC39 Committee. By the way, there were lots of different and interesting things established during this meeting. The results aren’t published yet, but you can check out several Telegram posts:</p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/618</a></p><p><a href="https://t.me/juliarderity/618">— t.me/juliarderity/621</a></p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/622</a></p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/623</a></p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/624</a></p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/625</a></p><p>— <a href="https://t.me/juliarderity/618">t.me/juliarderity/626</a></p><p>This time, the proposal that won the competition was <a href="https://github.com/HolyJS-TCXX/HolyJS-Piter-2019-TCXX/pull/10/files">String capitalize method</a> by <a href="https://github.com/helenjer">Elena Pravdina</a>. Now our colleagues help Elena to find a champion (a person who will advocate <a href="https://github.com/HolyJS-TCXX/proposal-to-capitalize-method-for-string-prototype">this proposal</a> in the Committee).</p><p>At the end of the first day, a party was held. There were BOF sessions, which have already become a common practice, too: the attendees were able to discuss the current situation in Node.js (with contributors of this project and Ryan Dahl), a11y and culture of communication in international multicultural projects.</p><p>Thanks to <a href="https://twitter.com/vaier">Alex Kanunnikov</a> and our amazing colleagues from <a href="https://twitter.com/honeypotio">HoneyPot</a>, in the first room attendees were able to watch Russian-dubbed <a href="https://www.youtube.com/watch?v=7Ym2ADCn77Q">documentary about Ember.js</a>. What more could one ask for? Just some popcorn, maybe.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*NKy4mrcF6Bpl1RtY" /></figure><p>At the party, there also were 10 lightning talks delivered by the conference attendees.</p><h3>Code+Learn</h3><p>It is also worth noting that the day after the conference a really cool fellow event <a href="https://twitter.com/mike1pol/status/1132998218483195904">took place</a>. <a href="https://nodejs.org/en/get-involved/code-and-learn/">Node.js Code+Learn</a> is an <a href="https://github.com/nodejs/code-and-learn/issues/95">event</a> where Node.js contributors help you make (a really small, but your first) commit to Node.js. Several HolyJS speakers as well as <a href="https://twitter.com/skovorodan">Nikita Skovoroda</a> helped to host Code+Learn. And our awesome friends from <a href="https://twitter.com/gopiterjs">PiterJS</a> played a main role in organizing this event.</p><p>This is the first — and not the last, we believe — event of its kind in post-USSR states.</p><h3>Interviews</h3><p>We held two broadcasts: one, included the first track of the first day, was public, the other, with all talks from both days, was to be paid for. (It will be the same for the next HolyJS in Moscow; you can already <a href="https://holyjs-moscow.ru/en/registration/online/">buy online ticket</a>.)</p><p>In both translations we filled in the breaks between the talks, using interviews with speakers and sponsors. Now you can watch <a href="https://www.youtube.com/playlist?list=PL8sJahqnzh8JzRGP3_YWTm109Bd5G2IHu">videos</a> of all those interviews from both days (some are in English, most in Russian).</p><p>If you speak Russian, we especially recommend that you watch the two interviews in a row: first the one with <strong>Alex Castillo</strong>, and then the one with <strong>Marina Miranovich</strong>.</p><h3>HolyJS 2019 Moscow</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*K4YpLX_7Jb79iraA" /><figcaption>That’s how much we’re excited about our next meeting!</figcaption></figure><p>It’s been three months since we started preparing for HolyJS 2019 Moscow, which takes place on <strong>November 8–9</strong>. The first list of talks will appear on the website a bit later, but you can already <a href="https://holyjs-moscow.ru/en/registration/">buy tickets</a>, which will become more and more expensive as November draws near. Our <a href="https://holyjs-moscow.ru/en/callforpapers/">Call for Papers</a> is also open — if you’d like to speak at HolyJS, now’s exactly the time to tell us!</p><p>And, finally, we’d like to say special thanks to these people: <a href="https://twitter.com/cakeinpanic">Ekaterina Pavlenko</a>,<strong> </strong><a href="https://twitter.com/_bmsdave">Vadim Gorbachev</a>,<strong> </strong><a href="https://twitter.com/kirjs">Kirill Cherkashin</a> and <a href="https://twitter.com/mike1pol">Mikhail Poluboyarinov</a>.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=105072ebc07d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[“I have only one learning technique: projects that I’m working on” — interview with Ryan Dahl]]></title>
            <link>https://medium.com/@HolyJSconf/ryan-dahl-d139d8a8fb07?source=rss-91eaadf816c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/d139d8a8fb07</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[deno]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[ryan-dahl]]></category>
            <category><![CDATA[holyjs]]></category>
            <dc:creator><![CDATA[HolyJS]]></dc:creator>
            <pubDate>Tue, 07 May 2019 09:16:14 GMT</pubDate>
            <atom:updated>2019-05-07T09:16:14.773Z</atom:updated>
            <content:encoded><![CDATA[<h3>“I have only one learning technique: projects that I’m working on” — interview with Ryan Dahl</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7YjB7mIpy7mlbrdASXcqFQ.jpeg" /></figure><p>May 25th will mark 10 years since the original release of Node.js. During that decade the project created by Ryan Dahl has achieved a lot. But Ryan himself has moved on to other things. What are those things? And what are Ryan’s views on languages, education and conferences?</p><p>On May 23th, two days prior to the anniversary, Ryan will present a talk on HolyJS conference in Saint Petersburg, Russia. In anticipation of that, HolyJS program committee members Dmitry Makhnev and Evgeniy Kot asked him a lot of questions.</p><p><strong>Eugene</strong>: Most JavaScript developers know you, but for those who don’t, could you please tell a bit about yourself?</p><p><strong>Ryan</strong>: I come from San Diego, California. I studied mathematics in undergraduate and in grad school. I was in a PhD program for algebraic topology at the University of Rochester. Three years into that I thought to myself: “What am I doing with my life? This is too weird and abstract”. I promptly dropped out of that program, ended up travelling around for a while and fell into programming, like many people do. I got into web development in mid-2000s. At the time I was quite into Ruby on Rails and Ruby in general. I was working on contract for EngineYard supporting their customers and later developing a NGINX module, which had me thinking a lot about non-blocking I/O, which lead led in early 2009, to the Node project.</p><p><strong>Eugene</strong>: Was it just luck? Or did you have some vision of the future where Node would be super-successful?</p><p><strong>Ryan:</strong> Why would you work on something if you don’t think it’s going to be successful? Most of the time you work on a project and it doesn’t work out. Eventually you give up on the project for whatever reason (and this, of course, has happened to me in all cases but one). Certainly Node was a case of the right timing. Chrome has just come out (and with it the new V8 VM), and I was thinking about non-blocking IO and how that could be exposed to web frameworks, and that all happened to fit really well with JavaScript. So yeah, it was just absolute luck.</p><p><strong>Eugene:</strong> Currently you are working on <a href="https://github.com/denoland/deno">Deno</a>. What’s your work right now? What are your future plans?</p><p><strong>Ryan:</strong> I’m trying to do a startup with a long time collaborator of mine, <a href="https://twitter.com/piscisaureus">Bert Belder</a>. We’ve been working on several projects during the last year and a half or so, one of them being Deno. Bert was very central to the development of Node, he did much of the heavy lifting required to port Node to Windows. He’s also one of the main authors of <a href="https://github.com/libuv/libuv">Libuv</a>, which is the platform abstraction backend of Node.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/991/0*zbvJoUFDMuAE9PYD" /></figure><p><strong>Eugene:</strong> Do you think that Deno will also become super successful and you will continue working on it in five years?</p><p><strong>Ryan:</strong> Whether it’s going to survive for five years I have no idea. Probably not, because most things fail. But it excites me and I enjoy working on it.</p><p>I guess I’m unsatisfied with the state of dynamic languages. I find myself wanting to have a quick go-to tool that I can deploy in various situations. Node and Python are good, but I find them unnecessarily complex or poorly designed in various ways. So this is about developing a tool that fits my own workflow, or the workflow that I want to have.</p><p><strong>Eugene:</strong> While preparing for this interview, we read another <a href="https://mappingthejourney.com/single-post/2017/08/31/episode-8-interview-with-ryan-dahl-creator-of-nodejs/">good interview</a> with you by Mapping the Journey. You told there that you were doing a project related to machine learning. And later at JSConf EU you <a href="https://www.youtube.com/watch?v=M3BM9TB-8yA">presented Deno</a>. So did you move from machine learning to Deno? What was your plan or your path?</p><p><strong>Ryan:</strong> I’ve been toying around with ML algorithms for the last couple of years and I was the middle of some project — essentially a framework for doing ML in JavaScript. It was the first time I had been using Node for a few years, and it clarified some of the issues that I had with it. So that led to a side project with a prototype in that presentation at JSConf EU. I got a lot of interest in the project after I presented it, so Bert joined and we just kept working on it. I will get back to these ML projects eventually.</p><p>In particular, I’d really like to hook up Deno to WebGL. Deno, of course, is built on top of V8, which is part of Chrome, and Chrome is a whole world of software infrastructure. Within Chrome there’s a library called Angle, which implements WebGL. Binding to this would allow Deno to program GPUs. GPUs are necessary for training many modern neural network models. I’d very much like Deno to satisfy the workflow I want for doing mathematical programming. I believe that a lot of the problems one works on in statistics (or mathematics in general) is plotting data and I think that a dynamic language is super useful for that.</p><p>There’s not that many dynamic languages in the world, especially among popular ones and fast ones. So it seems like JavaScript would be a great language for defining models. In many cases computation will be offloaded to a GPU. The actual speed of the dynamic language, or the runtime that you’re in, isn’t necessarily so important because of this. So yeah, I plan to get back to that stuff, but currently I’m distracted with Deno.</p><p><strong>Dmitry:</strong> Cool. And is Deno production ready or not? Can I use it?</p><p><strong>Ryan:</strong> I would say different people have different tolerances for pain, and for certain people who are willing to deal with bugs and lack of documentation and changing APIs, Deno could be useful for certain use cases. But in general — no, it is not ready for production. It’s version 0.3 right now, and I will label it 1.0 when I think that other people should use it. So no, it’s very much in development. It’s a fairly large undertaking. We’re essentially building a new platform. There’s a lot of things that go into this, and we’re trying to do this properly. That said, it’s somewhat usable for the hacker types out there who don’t mind getting dirt on their hands and maybe submitting an issue or PR when they hit problems.</p><p><strong>Eugene:</strong> What has to be added to Deno in order to start using it in production?</p><p><strong>Ryan:</strong> I think we’re trying to target a bit of a different use case than Node has. Node is a program that you run on your computer, right? One of the things that we’re trying to do is make Deno have more lower-level access to it. In particular to be able to import it as a <a href="https://crates.io/crates/deno">Rust crate</a> in particular, and embed it into other systems.</p><p>Suppose that you had your own web server of some sort, maybe some sort of serverless setup, and you want to give your customers the ability to execute a little bit of JavaScript, right? Maybe you don’t want to go so low as just raw V8, because raw V8 doesn’t give you that much. Maybe you want to be able to import from URLs, you want a bit of infrastructure around this, but you don’t want to go all the way towards the full runtime that somebody might have on a desktop computer. We hope that we can target this “embedding” use-case. We’re still working on how exactly that API looks. We also have some performance problems that we need to deal with which <a href="https://deno.land/benchmarks.html">we track</a>. We need to provide better documentation. So, yeah, there’s a lot to do still.</p><p><strong>Dmitry:</strong> One of the goals of Deno is to support TypeScript out of the box. Many people use TypeScript, and not only for browser stuff, but for Node.js, too. And I heard that some people from Node.js core team said that it’s good, and that TypeScript is the best language for transpiling for Node.js. Do you think TypeScript can replace JavaScript someday in the browser and have its own runtime, maybe with some VM?</p><p><strong>Ryan:</strong> The nice thing about TypeScript is that it’s a superset of JavaScript, it wouldn’t replace JavaScript. What I could see potentially happening — although this would be a very long time away — is that TypeScript gets added to the standards and JavaScript gets optional types.</p><p>Dynamic languages are very useful for the initial phase of development, like when you’re prototyping something. The nice thing about TypeScript (and the idea of optional types in general) is that as that prototype slowly matures, you can ratchet down the implementation by annotating the code with types. It doesn’t have to happen all at once, so you still have the ability to move very fast and sketch out new ideas in JavaScript.</p><p>As to whether the types can be used inside the V8 VM for runtime optimization, I don’t know. It sounds very hard and I don’t have the experience to know if there are potential wins there. In Deno we use the TypeScript compiler, which is implemented in JavaScript. One could imagine potentially having a Rust implementation of the TypeScript compiler, which could transpile to JavaScript faster. That may be possible. There’s a project called <a href="https://github.com/swc-project/swc">SWC</a> that is working on that.</p><p><strong>Eugene:</strong> But do you think TypeScript can completely replace JavaScript?</p><p><strong>Ryan:</strong> What would that mean?</p><p><strong>Eugene:</strong> There are different scenarios. For example, combining TypeScript with JavaScript in ES 2020, so it would be one language and one standard.</p><p><strong>Ryan:</strong> Yes, I could see there being types added to the standards. TC 39 controls the JavaScript standard, I could see them taking up types. From what I hear that has not been seriously considered yet. But think it will be a very long time before that happens — maybe some day.</p><p><strong>Eugene:</strong> A personal question from me: what do you think of Dart? Have you used it?</p><p><strong>Ryan:</strong> I’ve played around with it a very long time ago. Dart has similar goals to TypeScript, it was built with this optional typing idea. Which is a really nice workflow, as I said. But they chose a route of defining a different language, Dart is not a superset of JavaScript. Because of that, maybe, it hasn’t had the best adoption curve.</p><p>Flutter is doing quite well these days, so maybe I have to revise my ideas, but I would say that generally TypeScript has succeeded in these goals of having an optionally typed language by just extending JavaScript, rather than going in the direction of building your own language.</p><p>Whenever somebody proposes a new language, it’s really hard to get people to adopt it. It needs to be a lot better. For the longest time I thought this about Rust: I’m an avid C++ user, so I was like “What would Rust give me that C++ doesn’t?” I’ve learned about Rust recently, and actually it gives you a lot, it’s super useful. Adds a ton to C++ and as far as I’m concerned, essentially replaces C++. New languages need to provide something vastly better in order for them to succeed.</p><p><strong>Eugene:</strong> Yeah, languages are like cars: everybody can try it, but will still use the bus sometimes.</p><p><strong>Ryan:</strong> Yes, exactly.</p><p><strong>Eugene:</strong> TypeScript is popular these days, but JavaScript is everywhere: backend, frontend, mobile, React Native, small devices like Raspberry Pi, all those things. So it looks like a revolution has already happened, we have one language for everything. Do you agree with that? Or will there always be special languages for special needs?</p><p><strong>Ryan:</strong> This is why JavaScript is interesting: because it’s a language that runs everywhere. I would note that a lot of people think of TypeScript as a separate language, but it’s not, it compiles to JavaScript within JavaScript, it’s very much JavaScript. So as far as I’m concerned, TypeScript runs everywhere too. So yes, I believe in this idea. Certainly JavaScript will continue to run in the web browsers into the foreseeable future, and on various devices. That’s exciting, because you can target many different applications with it. That’s why I want to use JavaScript.</p><p><strong>Dmitry:</strong> Do you think this popularity of JavaScript is good or not? These days web is the necessary platform for any service, and JavaScript is the only one language for that. Maybe we need to have a choice? Maybe we need to put different VMs into browsers to have some options?</p><p><strong>Ryan:</strong> Well, I think that’s why people are excited about Wasm. This gives you the ability to compile, for example Rust, into something that can execute in browsers. That would be very awesome, but I wonder how well this will work for languages with garbage collection or other runtime facilities. While it might be possible to use, say, Python via Wasm to program a website, I suspect it will be quite unwieldy and slow. I guess we’ll have to wait and see how it turns out.</p><p><strong>Dmitry:</strong> And if I want something different from JavaScript, I need to learn something that can transpile to Wasm, yes?</p><p><strong>Ryan:</strong> Or transpile to JavaScript. The thing is that the JavaScript has a garbage collector and whatnot, and so if you have a dynamic language it probably makes more sense to transpile to JavaScript than it does to compile to Wasm and then also compile your entire runtime, including your garbage collector and stuff. Then you have a lot of overhead, while V8 is probably going to do a better job at garbage collection, no doubt. But yes, Dart compiles to JavaScript and you can use that to write websites. And there’s a couple of other languages that do that as well.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/521/1*jV78AbI1s0x2MNAs2ryfVg.png" /></figure><p><strong>Dmitry:</strong> Speaking of languages, what new or old languages would you find interesting to learn in 2019?</p><p><strong>Ryan:</strong> I really love Rust, it’s great. Rust has some new ideas in it, in particular this idea of having a single mutable object. Its compiler is very good, so you get extremely optimized code. It is an extremely steep learning curve though. It took me a couple of months to wrap my head around what was going on there. So I think Rust is super interesting, but it’s also something that I wouldn’t imagine is going to be used by everybody for everything.</p><p>If you’re writing an app, you probably are not going to be using Rust. If you’re writing business logic, you probably want to be doing this in the easiest possible language — Ruby, JavaScript or Python. Only in particular use cases would you really want to reach for Rust. But in those use cases it’s going to be super useful. If you’re writing a database or a web server — it’s a great language to choose. Or a VM, like we are. It gives you 100% control over what’s happening in your code at the expense of a lot of complexity that is exposed to the programmer.</p><p>It’s really a game changer for native code and offers something over Go. Go has a garbage collector, so I think Go is really great for high-performance servers, it’s super clean, very easy to write. But there’s still a couple of use cases where having a garbage collector is not appropriate. Like in Deno, for example. We’re wrapping V8, and V8 has a garbage collector. So using Go with V8 is fishy. We would have two garbage collectors in the same process which potentially could interact in catastrophic ways. V8 is already a monstrosity of complexity, that’s enough. So for our use case Rust is great. And I think we’ll see some interesting applications with Rust compiling to Wasm in the future.</p><p><strong>Eugene:</strong> And what do you think about functional programming, functional languages?</p><p><strong>Ryan:</strong> I think the functional style is good. I don’t think that you necessarily have to have your entire language structured as a series of maps and reduces and whatnot. I think there are certainly cases where imperative style programming is much easier to read and works out very well. Rust and JavaScript are great examples of merging these two styles of things. So I don’t think it’s an exclusive “either-or” situation. In the end CPUs are imperative, it’s a series of instructions that get sent to the CPU, so in many ways it makes sense to think about things sequentially like that.</p><p><strong>Eugene:</strong> And what paradigm or style is Deno written in? Object-oriented or functional?</p><p><strong>Ryan:</strong> Both. It depends on the various parts of the program and what we’re trying to accomplish.</p><p><strong>Eugene:</strong> We talked about languages, and what are your favorite tools for writing code? E. g. what is your preferred IDE, terminal, OS?</p><p><strong>Ryan:</strong> I use vim, iTerm2, and yes, I have a MacBook, a small, 11–12 inch laptop. I travel a lot and work out of various places, and I’ve just noticed that if I have a big screen, I get very used to having a big monitor, and switching to the laptop becomes really painful. So I’ve just trained myself to work off of a laptop. In terms of tooling I have a Linux box at home that I SSH into. I’m relatively old-school when it comes to tooling, it’s UNIX-y stuff. I use LLDB for debugging.</p><p>I’ve tried Visual Studio Code, but we’re writing our own platform, and a lot of the integrations that you expect to happen with IDEs are not there. Usually these are superficial problems not related to what I’m working on, and I find it to be a distraction. I’m used to seeing this very bare-bones thing, and I think that works better for developing low-level software. I guess if I was working on a website or app in some established platform I would probably use Visual Studio Code.</p><p><strong>Eugene:</strong> So you’re an old school programmer.</p><p><strong>Ryan:</strong> I guess so, yes.</p><p><strong>Eugene:</strong> The next question is related to this topic — it’s about new school, if you wish. It seems like basic programming skills right now or in the near future will be as necessary as math or English or something else everyone studies in the school. What do you think about that? Maybe in a slightly more distant future machine learning will become a necessary skill?</p><p><strong>Ryan:</strong> In the last 15 years that I’ve been doing programming I’ve been surprised at how much bigger it has become. I felt like I was late to the game in 2005, but looking back on that, it was a much smaller community of people. Now it seems like everybody is a programmer. It’s very clear that programming has been scaled to a much larger audience. It is a useful skill for a large number of people. Given that, yes, people should be learning this in high school. As for machine learning, it’s quite technical and I would think high school students would have more fundamental knowledge to worry about.</p><p>I do think is that statistics should be taught more in lower level mathematics. At least in the US when you are in high school, you learn a lot of algebra, the quadratic formula, you’re taught low-level calculus, taking derivatives, this sort of stuff. Algebra and calculus take up the bulk the course work, whereas quite a small segment of the population ends up using those skills often. But being able to process data statistically is a skill many more professionals need to have.</p><p>Machine learning itself, especially deep learning, is changing very fast, it’s very much under development. Who knows if it’s going to be the same thing in ten years as it is now. Probably not.</p><p><strong>Eugene:</strong> I have another question related to the new generation. We had a bunch of people from school in our office a week ago. I talked to these kids who are 15 years old, and one of them told me he tried Python and Rust. You said that you felt you were too late for the train in 2005, but we have a feeling that the young generation can probably learn faster than us. My friends have a child who is about three years old, and he already knows how to enter something in YouTube, how to play games in a device. I’m starting to feel too old.</p><p><strong>Ryan:</strong> Yeah, me too.</p><p><strong>Eugene:</strong> Do you have a feeling that we are too old for this? That we will be too stupid for the next generation?</p><p><strong>Ryan:</strong> Probably every generation has thought this. I’m sure that when we were kids people thought the same thing about our generation. But yeah, YouTube is really a game changer. It’s just amazing that you can just decide: “I want to learn physics!” and just watch the best physics lectures that have ever existed. There’s just so much opportunities for self-teaching now. I think kids are going to be very smart. It just allows people to go after what they are looking for. I remember being a kid and wanting to know something. We had this set of encyclopedia books at home, so you would just look inside it, and if it wasn’t there that was it, there was no way to know, no answer to the question that I had. That’s not the case anymore.</p><p><strong>Dmitry:</strong> In our industry we need to learn continuously through articles, books etc. How do you do that? Can you suggest something for old people such as ourselves?</p><p><strong>Ryan:</strong> I think it’s the same anywhere — it’s hard to keep up with technical subjects that are moving really fast, and I don’t have any special advice for that. One has to just keep doing it. I always tell people that you have to have a project, you can’t learn things in the abstract. It’s very difficult to learn something in detail if you’re not actually working with it. I can’t tell somebody about Rust and then they would know Rust. You have to actually use it yourself. The only technique that I have, which is not really a technique, is that I always have projects that I’m working on.</p><p><strong>Dmitry:</strong> Maybe you can suggest how I can check the results of my side project? E. g. I get Rust, I write something in Rust, and I want to talk to somebody about it, but none of my colleagues use it. What would you suggest?</p><p><strong>Ryan:</strong> I don’t know. Find some friends online?</p><p><strong>Eugene:</strong> Yes, but let’s imagine I started a side project in a completely new language, the technology is completely new to me. I think my code in Rust would be awful. How to improve upon it? Just improve the project, pull request, all those things? How to become better with some technology that you don’t know?</p><p><strong>Ryan:</strong> I can’t offer any advice, I have no idea. I wouldn’t claim to be very good at these particular things.</p><p><strong>Eugene:</strong> Well, we’re lucky, because we have so many ways to learn. You mentioned YouTube, and we have other media, blog posts and all those things. Which ones do you like? Maybe you use YouTube videos? What do you think about conferences?</p><p><strong>Ryan:</strong> I think conferences are great. As far as programming is concerned, I don’t use YouTube at all for that. I read Hacker News and some Reddits. I generally keep up to date that way, but not really. I generally just work on projects, and I’m sure I’m missing out on a whole slew of interesting technology. The programming YouTube world seems a little too newbie for my tastes. I don’t know, I would dig into documentation. But for other topics that I’m not an expert in, like physics, which I’m interested in, YouTube is really great.</p><p><strong>Eugene:</strong> And what about conferences? What, in your opinion, is the main reason for attending them?</p><p><strong>Ryan:</strong> Conferences are super useful, I love attending them. I should say, it’s worked for me. Especially if it’s a JavaScript conference, there’s always a bunch of people in there talking to me a bit. But yes, this is the best way to get introduced to new technology. You hear an interesting talk, go have a beer with somebody, they tell you about it, and they are excited about it. This is how I actually get most interesting things — hearing about it from people in person, and generally just hallway discussions about projects that aren’t public yet, what’s going on. It’s exciting and fun. So I’m really looking forward to coming out to HolyJS. How long have you guys been doing this now?</p><p><strong>Dmitry:</strong> It started <a href="https://www.youtube.com/watch?v=2vXTMXuT1gw&amp;list=PL8sJahqnzh8JST_ZwTcGG1FHGgKBMcpn6">in 2016</a>.</p><p><strong>Eugene:</strong> In the <a href="https://mappingthejourney.com/single-post/2017/08/31/episode-8-interview-with-ryan-dahl-creator-of-nodejs/">interview</a> that we mentioned earlier you said that you worked on NodeJS for about four years. That’s a lot of time. How did you combine it with your main job? Was it more of a hobby? Do you have a side project right now?</p><p><strong>Ryan:</strong> With Node it started out as a side project. I was freelancing, but after a while I got hired by Joyent. They basically told me: keep working on this, we like what you are doing. That’s how Node worked out. Whether I have side projects at the moment? I have a lot of non-programming things that I’m interested in, but at the moment Deno takes up all of my time. It’s quite a big project. I have kind of side projects within Deno.</p><p><strong>Eugene:</strong> If it’s not too personal a question, what hobbies do you have apart from programming?</p><p><strong>Ryan:</strong> I’m toying with the idea of getting into physics a bit more seriously. I find this stuff quite interesting. But I’m totally a layperson, I hear stories about it, but I haven’t actually studied it as a grad student. I’m also quite interested in machining, I guess you would call it metalworking. I have no experience with this whatsoever, but I find it fascinating how people can make these very strong machines somehow. I guess I’m fascinated by that because it’s very similar to software engineering, but in the physical realm. You’re problem-solving, you have to design things, use one tool to build another tool, make precise measurements, that sort of stuff. It’s a physical manifestation of software.</p><p><strong>Eugene:</strong> You mean, like put V8 into Volkswagen Beetle?</p><p><strong>Ryan:</strong> Yeah, exactly.</p><p><strong>Eugene:</strong> So it’s something related to V8, again.</p><p><strong>Ryan:</strong> Yes. I mean, I’m just an amateur, I don’t know anything about this stuff. I just like reading about these things. I would consider myself also an amateur in the machine learning world. I’ve done a bit of research, but by no means am I a PhD level person. So I would like to get back into that. There are some topics in the machine learning world that I would like to pursue further, but at the moment I’m a bit too busy to do that.</p><p><strong>Eugene:</strong> Let’s talk about open source. Is it worth it for a developer to write open source software? We mostly do it for fun, but as you mentioned, when we start a side project, we always want it to be successful. Is it worth it for you?</p><p><strong>Ryan:</strong> It’s absolutely worth it for me. I’ve spent my whole career working in open source, so I think it’s great. I think you make really good relationships and long lasting friendships with people across the world. It’s fun. Now that the tech industry has become so massive, and people have negative feelings about Facebook and Google and whatnot, this isn’t thought about as much. But I still believe in the idea of open source, this Richard Stallman-type idea that we’re building a better world. This is free software, and anybody can go and take it, do what they want with it. This allows people to not have to pay a huge amount of money to get access to cool technology. It’s still a driving ideal for me.</p><p><strong>Eugene:</strong> Ten years ago there were fewer people in IT industry and programming, today it’s an industry with a lot of newcomers. Do you have a feeling that it was like a private club for some people who love it? And right now the industry is more like just a job, with marketing and everything.</p><p><strong>Ryan:</strong> I wouldn’t say that it was a private club back in the day. Rather a public club, anybody was welcome to join. These days sometimes I get into a project and it starts feeling like work. I’m sure you have this experience. Maybe it is actually work. I just try not to do projects that I don’t get excited about. If it starts feeling like work, I just do something else. That keeps you doing exciting things.</p><p><strong>Eugene:</strong> Actually, it’s really motivating. Let’s talk some more about the conferences. Of course, it’s a public club, and the conference is the best way to join this club. Even if you don’t know programming, you attend a conference and listen to the talks. What are the most important things in conferences for you?</p><p><strong>Ryan:</strong> Technical talks. For myself, that’s the most interesting thing. I love hearing about some new technologies and people getting into details about those technologies. And the side chats that come after the talk, that’s good.</p><p><strong>Eugene:</strong> And the final question. As far as I understand, this is you first time in Russia?</p><p><strong>Ryan:</strong> That’s correct. I’m really excited.</p><p><strong>Eugene:</strong> What do you expect from the country, from the city, from the conference?</p><p><strong>Ryan:</strong> Well, I have this idea of Russian programmers, that you guys are extremely hardcore. I have this one friend who is extremely good and very Russian. Maybe my experience is tainted by him. So I’m expecting some hardcore Russian hackers out there. As for the city, I hear St. Petersburg is very beautiful, so I look forward to seeing that.</p><p><strong>Eugene:</strong> We’re excited too, because you’ll be talking on the HolyJS 2019 in St. Petersburg. Thank you very much for your time, it was a pleasure.</p><p><strong>Ryan:</strong> Thanks, this was fun. I look forward to coming out there.</p><p><em>We also published a </em><a href="https://habr.com/ru/company/jugru/blog/450752/"><em>Russian translation</em></a><em> of the interview.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d139d8a8fb07" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[«Your library, just as your child, one day finds its own way»: Michel Weststrate on OSS]]></title>
            <link>https://medium.com/@HolyJSconf/michel-weststrate-cd5b5ef69d10?source=rss-91eaadf816c8------2</link>
            <guid isPermaLink="false">https://medium.com/p/cd5b5ef69d10</guid>
            <category><![CDATA[mobx]]></category>
            <category><![CDATA[holyjs]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[HolyJS]]></dc:creator>
            <pubDate>Thu, 21 Feb 2019 11:34:22 GMT</pubDate>
            <atom:updated>2019-02-21T11:38:18.082Z</atom:updated>
            <content:encoded><![CDATA[<h3>«Your library is like a child. One day it will find its own way»: Michel Weststrate on OSS</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/855/1*3LbNlqwiIUiT1jP06a_AAQ.jpeg" /></figure><p>How does it feel to be a creator of a popular open source library? Sure it’s great to help a lot of people around the globe, but don’t you get overwhelmed with the amount of work? How can you deal with that? How much work can be delegated to others?</p><p><a href="https://medium.com/@mweststrate">Michel Weststrate</a> knows it all: his <a href="https://github.com/mobxjs/mobx">MobX</a> library has more than 17 000 GitHub stars and more than 100 contributors. Back in 2018 he was a keynote speaker on <a href="https://holyjs.ru/">HolyJS</a>, and HolyJS program committee members Dmitry Makhnev and Evgeniy Kot asked him a lot of questions about open source in general, MobX in particular, and also about conferences. Back then we published that interview <a href="https://habr.com/ru/company/jugru/blog/426517/">in Russian</a>.</p><p>Now we’re happy to say that Michel will come to HolyJS <a href="https://holyjs-piter.ru/speakers/6bifi3hokmiou4yqscigqy/">once again</a> — and we decided to publish that interview in English. Some things have changed since 2018 (nowadays Michel works <a href="http://michel.codes/">for himself</a>), but most of the answers are still relevant.</p><p><strong>— For those who do not know you, could you please tell us a little bit about yourself?</strong></p><p>Michel: Sure. My name is Michel Weststrate, that’s too hard to pronounce for most people. I am from Netherlands. Most people know me for my work on MobX or Immer. Actually I work for a company called Mendix. Basically we build software to build software, so we have an application development studio that’s used by lots of consultancy firms etc. We’ve automated a lot of large bank insurance companies and those kinds of systems.</p><p>I’m involved in technical side of things, that’s basically what I enjoy doing. I’ve rolled into the open source world about two years ago and since that moment I’m quite active mostly in the React community and JavaScript community in general.</p><p><strong>— What do you do at Mendix? As far as I understand you are a tech lead.</strong></p><p>Michel: I wear a few different hats over there, and the most important one is indeed the tech lead’s. It means that I’m basically responsible for making (or coordinating) the technical choices for one of our tribes. I’m working on a product I mentioned earlier, it’s a browser-based application, and I’m involved a lot in making the right restriction or the right technology choice. And I’m still programming in that area, too.</p><p>I am also involved in the open source community, and it fits very nicely with the previous part because it’s a bidirectional thing. On the one hand, Mendix itself is very much in the enterprise world, and what we’re doing is often pretty close to the outside world. And we’re doing some really cool technical stuff which we want to share at conferences, so I either talk about it myself or try to encourage my colleagues to do so. And on the other hand, the nice thing about visiting conferences frequently is that the opposite also happens: you discover something that can or could be relevant for us, then we investigate it more and apply to our own stack.</p><p><strong>— You mentioned that you are really into OSS evangelism. What is it and why is it important for you?</strong></p><p>— What I noticed is that open sourcing stuff doesn’t really save you time, but it does mean a significant increase in quality, in testing, because a library like MobX is used in a lot of ways and circumstances. And it means open sourcing software is a benefit that it’s really hard to get otherwise. That’s one thing. And there’s the other one: I do believe that what we build on the low level doesn’t make a distinction for a company itself, so why not share it? I mean, it’s the thing you build with the technologies that makes you better or worse at competition, but not the low level stuff you use. And if you collaborate, you all benefit from it and I think it just makes the tech development in general go faster.</p><p><strong>— I’ve heard some opinions that open source is a really expensive thing. So big OSS projects such as Linux require a lot of money from vendors like Oracle and Microsoft. Do you think that OSS world could live without big vendors?</strong></p><p>— I think it depends. You have smaller libraries that could live without that, but you also have really complicated projects like the one you’ve mentioned, or something like React Native: it is so complicated and so many people depend on it that it needs a super solid financial model. In that case I think it’s really hard to do it without big companies behind the software. But I don’t think that has to be a problem. I think it’s more important that companies learn to take the responsibility rather than figuring out how to make OSS without a company.</p><p><strong>— But what would happen, for example, if Facebook came to you and said “Hey, you created MobX, can we buy it or maybe become a sponsor so you will develop MobX under our brand?”</strong></p><p>— Well, actually, they do sponsor MobX. That’s kind of funny, they are one of the sponsors on the <a href="https://opencollective.com/mobx">Open Collective</a>. So in that sense it is already happening. I think Open Collective is a really nice example of how we can improve the financial world of open source because it allows companies to sponsor software in a way that works for them (it’s financially solid: you can invoice, etc). At Mendix I’m kind of already paid to do maintenance of MobX so I won’t be interested in moving in to Facebook. But I can imagine that would work for other people and I think there is nothing wrong with that. I think as long as the software and license stays open source it’s fine to attach the name of the main sponsor to a software product. It’s not different than watching soccer on TV: what matters is that everybody can see the teams playing soccer, and what brand name is on the T-shirts is not that significant.</p><p><strong>— But could a big sponsor force the library to change in some way?</strong></p><p>— I don’t think I saw it really happen or at least not so that it’s really became a problem. If I’m not mistaken, webpack basically allows that model, people can pay for features. So there is a risk, but I think it’s maintainers’ responsibility to make sure that the project stays true to its philosophy. And within that philosophy there’s probably a lot of wiggle room. And a nice thing about open source is that if something goes horribly wrong, at least there’s an escape by means of forking.</p><p><strong>— When a library gets popular, it starts to require more resources. How much time do you spend on MobX?</strong></p><p>— Lately not that much, actually. MobX is now quite stable. But of course I spent a lot of time doing it in the past. That’s very diverse. I think for the first two years on average it was at least a few evenings or afternoons a week. And a lot of moments when you just reply to small issues or quick questions on Twitter: that doesn’t really feel like investing a lot of time, but probably adds up as well. But it’s super hard to measure. It’s like checking your business mail, you also check your issues and quickly drop an answer.</p><p><strong>— How to be productive in this situation? Not everyone can work on open source during working hours, so if a library becomes more and more popular it can become a problem — how to live with that?</strong></p><p>— When I worked on MobX, at the beginning I did it in my free time as well, it became sponsored later on when it became more popular. But I noticed that there are a few things that which really helped me a lot. One of them is to really stay on top of it regarding your documentation. For example, if you notice that you receive the same question three or four times in your issue tracker, make sure that you write it down in your doc somewhere: it’s a really good time investment, because you will see the incoming issues going down.</p><p>Second thing: be very critical about the quality of the issues you accept. At the beginning, when the issue is reported, you try to reproduce it based on the description you get and then you probably find out you’re not able to reproduce it. But that’s super time-consuming, so nowadays when somebody reports an issue, I demand something I can directly run, be it a code sandbox or a pull request for unit tests. Something for me to verify whether the bug is on the library side or the consumer side. That’s super important, because that saves a lot of time. And it makes you sure that the person submitting issues is willing to invest in this as well. Some people say “I don’t have time to make a reproduction” and I’m like “Well, then I don’t have time to solve your issue.” I mean, you probably get paid for working and using my library, so why I should be willing to invest my free time in your issue? So, that helps, but that requires being able to feel more irresponsible about your library than you usually do. Naturally you want to help everybody else. But I discovered it’s simply not realistic.</p><p>So, those kinds of things help. Also, because I maintain multiple libraries, I usually don’t respond to all my issues immediately, I jump from one library to another. I work a few days on one of them answering issues and then I move on to the next one. So it can be that I answer within a few minutes if you just happen to file something on what I’m working on, or it can be days because I’m just working on one of my other libraries. And it helps me to make it more feasible and have less context switches. These are the tips that can hopefully help when your library starts to become more popular and starts to generate more work.</p><p><strong>— But if you demand unit tests or something, can it lead to people thinking “Hey, this guy acts like a superstar and cannot answer my simple issue”? Does it lead to bad attitude towards maintainers?</strong></p><p>— I think I saw it happen a few times, but very rarely, and in general people seem to understand that maintainers are quite busy and that chances are it’s on their side. If you use a filter from Lodash and something goes wrong, your initial feeling would be that it’s probably on your side, because everybody uses Lodash. So most people understand that they have to be accurate with their questions and ask kindly.</p><p><strong>— When a library gets popular you can realize that you cannot maintain it on your own. What about giving some rights to other members of the community?</strong></p><p>— That’s a super good idea and I tend to do that as soon as I see somebody submitting a few PRs that make sense (or even one big PR). I usually give people contributor rights and I think it works very well. For example, for mobx-state-tree most maintenance so far was actually done by other people, not by me. There are areas in the code base which they are more familiar with than I am and that’s actually a great place to be at.</p><p>For MobX I didn’t do that because it’s basically super settled and the algorithms itself didn’t change in the past two years, so maintenance, especially on that one, isn’t that big. But for mobx-state-tree I definitely choose people that make lot of users libraries, and also give them collaboration admissions, because it makes a lot of sense. If you use the library intensively in your day-to-day work, you will also discover patterns or common issues I’ve missed. And so if there is a developer that didn’t have control on the library, I think it’s motivating and also feels secure, because you can make it work for what you’re doing with it.</p><p><strong>— Don’t you ever feel that after giving contributor rights a library, like a baby, starts to get out of your hands? Maybe you don’t totally agree with the way it’s evolving or something like that.</strong></p><p>— Yes, a little, sometimes. But I think that’s ok. You’ve made a great analogy by comparing it to a baby: at certain point babies grow up and you have to let them go, because they have to find their own way. I think it’s partially the same with an open source library. If they are successful, you’ll see more complex situations, you’ll have to handle cases you didn’t want to handle. The code won’t be anymore this beautiful clean minimal code that you wanted it to be. That will always happen when it’s successful.</p><p>In MobX there is a great example: originally I wrote for TypeScript which has a very simple decorator model, and then people started to use it with Babel which had a completely different implementation. And some pieces in the code base are quite ugly because they try to feature detect whether you’re using a TypeScript or Babel transpiler. That sounds horrible and it looks horrible. But it’s part of the job. You don’t really like it but you ought to make sure that it works everywhere consistently. And in that sense your baby might go in directions you actually didn’t intend it to, but it’s OK, because it’s the fact that people can apply it successfully that matters in the end.</p><p><strong>— Software development changed a lot over the years, it became easier for people to contribute. What do you think about the current situation in OSS world and what could happen in the future? For example, will big corporations rule this world and will there be no individual contributors, or would it be the opposite?</strong></p><p>— It’s a hard question. I’m not sure that there will be a lot of changes. And the movement happens in both directions. I’m especially impressed by Facebook and Microsoft: how much they open source nowadays and to what level they allow individual developers to contribute. React Native is a nice example where a lot of work is not coming from Facebook itself.</p><p>On the other hand, indeed, for an individual it was probably never as easy to contribute or set up opensource project as it is now. All the tooling is getting more and more standardized, we have great online IDEs, like <a href="https://codesandbox.io/">CodeSandbox</a> or <a href="https://www.gitpod.io/">Gitpod</a>. I was working with Gitpod the last few weeks, it’s really great, I can review PRs without even having to check out stuff locally. Just run it in Docker in your browser and develop there.</p><p>So I’m not sure what’s the change in that direction, really hard to say.</p><p><strong>— Will those things like great tooling help open source grow in the future? Should we expect a lot of open source projects in five years?</strong></p><p>— I think that movement will continue. One of the reasons: both companies and developers realize more and more that open source is also super useful for the talent acquisitions. By looking at open source code that somebody produces you can tell more about the person than you can discover in a day of interviewing. How somebody responds to issues or files issues tells a lot about this person’s character. And I think both developers and companies increasingly realize the value of that.</p><p><strong>— So development of an open source library can help a developer with the interviews?</strong></p><p>— Exactly. As a company, if you have some open source libraries which are not crucial to you API, that’s great, because people will chime in and they might just be what you’re looking for. And if you can hire some of your contributors, it is easier to onboard them and you’re more sure about what to expect. So I think, even just for that reason companies got to open source interesting stuff.</p><p><strong>— Let’s move from the open source in general to MobX. First question: how and why did you started to work on MobX?</strong></p><p>— Good question. Actually it has quite a specific answer. At Mendix we had a Windows GUI application written in C# and at some point we decided to port it to the web. And we started to investigate what kind of stack do we want to use for this. React just started, Angular was around for a while, Ember was quite popular. And quite quickly we fell in love with React because of its component model and abstraction layer it provides.</p><p>But then we discovered a performance problem with updating DOM. In C# we could just update the model and redraw the canvas the whole time and nobody optimized anything because it was already fast enough. With web we suddenly discovered that you can’t just repaint everything 60 times a second because DOM can’t handle that. So we started to figure out how can we do this efficiently.</p><p>We looked into the whole immutable approach but that didn’t work for us for a few reasons. One is that from the nature of our data and how we render it. It rendered in different places. It’s really hard to normalize that data. And secondly, it felt that there were way too many details involved. You need to write selectors to make sure that you get updates for whatever data you are rendering, for example.</p><p>But what if you want to write code that is as dumb as our old C# code, “render something”, and you don’t want to care about things changing in the future? What if you don’t want to tell the components “Hey, you need this piece of data and grab that piece of data over there and then you can render something”? So we started looking into what kind of technology could make this possible. And quickly got to the programming paradigm used in Knockout<em>,</em> Meteor or (at least conceptually) even Angular. Where you don’t specify anymore what the relationship is between the dependencies of the data and the components, and you don’t specify what should render when.</p><p>And I started investigating why people often hate these approaches, especially when application becomes complex. And most things related to predictability and debugability: things might run too often or not enough times or in wrong order. And I’ve figured out that we can do better. That we can strive for the same goal, but do it smarter implementation-wise. And that’s basically where MobX is coming from.</p><p>It doesn’t just capture relationships between observers and observables, it builds entire dependency graphs so it can make sure all your observers run in the most efficient order. So a “glitch”, as it’s called in reactive programming, can not happen. That was basically taking stuff that already existed but trying to make it predictable.</p><p><strong>— So your experience tells us that if I like some approach but libraries aren’t good, I can make my own and it might become popular?</strong></p><p>— Yes, exactly! So I wrote it for internal purposes originally and then I went to ReactEurope 2016 (or so I think) and suddenly there was a lot of talking about the Flex patterns. I think that was the point when all the Flex wars were happening. And I was just sitting there feeling that people put so much effort in a problem we already solved. So that was basically the point when I figured “let’s open source this”. And it kinda worked out. Probably because it wasn’t another Flex implementation but something completely different. It appealed to a lot of people.</p><p><strong>— So the whole idea of MobX was pretty simple. But now it has lots of code and features. Don’t you ever think it became too complicated?</strong></p><p>— Yeah! I always have this feeling “I want to create the MobX Lite”. In essence, you can write some version of MobX in 200 lines of code. I even have a talk where I kinda do it. Then you can add a few hundred lines to optimize the shit out of it and make it much faster in all kinds of circumstances. And there you have entire core of MobX. But I think three quarters of MobX code is on the API surface. There’s a core idea, and then the library just addresses all the things to make sure API is as nice as possible. For example, in MobX 5 there were changed regarding <a href="https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/Global_Objects/Proxy">proxies</a>.</p><p><strong>— Most developers don’t use proxies in production yet, and you do it. Was it tricky?</strong></p><p>— It’s sometimes hard to be one of the first projects to adopt a technology. But proxies are around for quite a while, I think there were stable implementations four years ago. They are adopted so late because it’s been only like a year since they were implemented by all major browsers. And proxies had a significance overhead, but that overhead now is negligible and will be probably caused by your implementation and not the proxies themselves.</p><p><strong>— OK. Let’s talk a bit about the state. We remember days when jQuery was the ruler of web development and there was no state on the client, we stored it in a global object or something like that. Now you cannot create an application without some kind of state managing library. What has changed?</strong></p><p>— I think there are two answers to that. One is that back in jQuery time there was not that much state on the client in the first place. jQuery was often used to add interactivity when state was left on a server which nowadays is considered a bad practice.</p><p>But maybe a more important reason for moving from jQuery to a component-based model like React is that React allows us to use components in an independent way and that makes scaling your codebase easier. So moving from jQuery to React made it easier to build more complex applications.</p><p>And I think state management does for state the same that React does to UI. It allows you to split your states in more cohesive patterns. You can move to self-contained pieces of data and logic which you can unit test without your UI so you can control them way better.</p><p><strong>— What do you think about the future of the state management? Have we got to the perfect solutions, or is there a big road ahead of us?</strong></p><p>— I think we’re still not there yet. Especially when it comes to state management oriented on immutable values. We didn’t make it easy enough to work with.</p><p>I think one of the reasons Immer became so popular in 2017 is because it’s finally makes immutable states feel natural in JavaScript. But I think there’s still a lot of things to do, I feel that a lot is still not as natural as it could be. And new approaches arise, GraphQL is very interesting to mention in this area, but I don’t feel it’s there yet when it comes to local states. So in that sense I expect that would evolve as well.</p><p><strong>— Could you name one or two features that you would like to add to MobX in the coming years?</strong></p><p>— There’s one thing I really want to add, but it’s not relevant for a lot of people: I want to make data transformations more fully reactive. For example, you have a to-do list, and then you do some filtering, filter all the unfinished todos. Currently if at this point you need to recompute you will run your filter again and it will process again all your items. But it will waste more time than it could. Only the changed items can change the outcome of your filter, so your filter should not run over all your to-do items. But currently there’s no convenient way to express those kind of transformations. But data transformations can be more reactive than they are now. So it would be really cool to add this in the future.</p><p><strong>— Let’s talk about conferences and workshops. In Russia there’s a problem with the workshop culture: in general it isn’t popular and the audience thinks that it’s only for juniors. How do workshops work in Europe and what do you think about them?</strong></p><p>— I really like workshops and I think it’s a good way to learn. I personally like to learn in two ways: I either sit on a couch and read a book from front to back or attend a workshop. Personally I’m not a kind of guy that likes to learn from videos (even though I created a few video courses myself), because it’s always either too slow or too fast for me.</p><p>When I started doing Docker stuff, I just went to a workshop to learn the basics of it. And because it’s quite hands-on, you immediately get a feeling of how it works, how it feels, and how you could apply it. I don’t feel that workshops are more interesting for juniors than seniors. I think the point of workshops is that they are the quickest way to adopt a new technology which you are so far quite unfamiliar with. I think that’s the biggest value of workshops and that’s something you don’t get from a book.</p><p>A book is more like getting the bigger picture and figuring out whether something is relevant or not in the first place. But if you really want to start to work on something or you seriously consider that, a workshop is the quickest way how to approach things. People follow the workshop, but in the breaks they will also come with real problems they have or ask more questions on how they can apply what they’ve learned to their specific problems. That’s the benefit of workshops: you’re really talking to someone, you can basically ask questions related to your own situation. I do quite strongly believe in workshops as a means of adopting new technology.</p><p><strong>— Some people in Russia think that conferences are not very important because you can just read articles on Medium. What do you think, why should a person go to a conference and not just watch some videos on YouTube?</strong></p><p>— Very good question. I think, unlike workshops, the point of the conference primarily is not to learn. Not in my opinion. The primary reason why you should go to the conferences is to get inspired by what’s happening in field or what people are doing. It makes you want to learn, but that might not be on the conference itself.</p><p>With that comes all the networking. When you go to conference try not to talk too much to your own colleagues. You already know them. You already know which problems they are solving. It’s way more interesting to talk to random people which may be in the same order line for food or something. What are they doing? How they are solving problems? What experiences they have with a library somebody talked about earlier that morning?</p><p>And just find speakers if you have questions for them. A lot of people are afraid of approaching speakers, but for me as a speaker and probably for most of the other speakers, speaking to attendees is one of the coolest parts of the conference. I mean, don’t talk to me five minutes before my talk, but beyond that I’m very approachable or I try to be. So don’t hesitate to talk to me.</p><p><strong>— That’s a very cool advice. Thank you for your time!</strong></p><blockquote>Michel will come to <a href="http://holyjs-piter.ru/en/?utm_source=medium&amp;utm_medium=weststrate"><strong>HolyJS 2019 Piter</strong></a>, which takes place in Saint Petersburg, Russia, on May 24–25.</blockquote><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cd5b5ef69d10" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>