From the “new number format” to “code as a UI”: how HolyJS 2017 Piter went
Since everything is changing so quickly, what was at the conference itself compared to the previous one? How did the eminent Douglas Crockford speak ? What were the other notable talks about? All this is under the cut.
The first significant difference is organizational. The conference became two-day, not trying to push the maximum possible number of reports into the grid, but instead providing half-hour breaks: it was possible and how to question the speakers in the discussion zones, and participate in activities at the sponsor stands, and discuss painful with each other.
By the way, about sponsor stands - this time everything went on a grand scale. There were not just a lot of stands, something was constantly happening around them. It seems that VKontakte attracted the most attention , having organized a contest according to the Code in the Dark rules . Opponents made up the page according to the given layout “blindly”, they could not see the result of their own actions - but all the spectators could see the result and the code. They wrote more about what was happening on the official page of the contest (and it is not surprising that this page is a VK public).
And what about the reports themselves, for which everyone gathered? Two days not entirely retell, but we note some points.
Martin Splitt has already become a regular hero of HolyJS. In December, the audience at the Moscow conference really enjoyed his performanceabout WebVR, and now he has performed with the theme “Rendering performance from the ground up”. This was a sharp contrast: instead of looking into an exciting future with new interesting devices, this time he started from the bottom - because in the present many users are not as powerful devices as we would like, and think about the price of displaying any items still have to.
Imad Elyafi talked about the experience of migrating a huge service on React, which he got on Pinterest. Moreover, the interesting experience of Imad is not limited to this: earlier he also worked on Facebook, where React appeared. Since he can compare what it is like to work with React “inside” and “outside” Facebook, I immediately wanted to ask him about it. And since we did interviews with speakers in the HolyJS online broadcast between the reports, they asked.
The answer was this: on the one hand, on Facebook, the proximity to the creators of React is really felt (since the office is a “big hangar”, different developers often intersect with each other, and it’s easy to communicate with the team of interest). On the other hand, a third-party company can often afford more bold decisions when using React than Facebook itself. Not surprisingly, in the end, Zuckerberg himself had already moved away from his early motto “Move fast and break things” to the much more cautious “Move fast with stable infra”.
Interviews were done with Alexey Ivanov(Evil Martians), at a conference talking about the internal structure of the webpack bundle. And as a person who actively climbed inside the webpack, we asked, among other things: “But did you get the feeling“ well, it’s all right, you should do it like that ”, and if so, I’d like to change first of all? ”Alexey replied that the sensation, of course, arose, and most of all was caused by the CSS loader: they say, now he does too much, and even the creators of webpack recognize this.
In general, the words "setting webpack" are associated with many unpleasant and at the same time inevitable procedures. But Alexey Zolotykh, who compared ECMAScript, TypeScript and Dart in his report, noted that at least one way to avoid this pain exists: “There are many different build tools for ECMAScript / TypeScript, the only problem is that they are all difficult to configure. And Dart is simple: he has Pub, and he is out of the box. " In the case of package managers, the situation turned out to be similar - a single “boxed” version of Dart against a number of available options for ECMAScript and TypeScript, where even npm ceased to be an unambiguous standard with the advent of Yarn.
In addition to the three languages listed, front-end vendors have recently added another option. Bay Bashorov(JetBrains) spoke at HolyJS about using Kotlin in the frontend, and those who knew the Java world could experience deja vu in his talk. A couple of years ago, at Java and Android conferences, one could hear “introductory” reports about Kotlin: “there is such a young Java-compatible language that you might like more than Java, and here are its main features like nullability”. Time passed, the language gained momentum in the Java ecosystem, a lot of developers using it appeared, and conversations moved from “it exists” to a discussion of narrower and more specific issues - such as the implementation of coroutine.
Finally, she closed the conference with her keynote, Lia Veru , cheerfully starting “I am from the island of Lesbos, which technically makes me a geographic lesbian.” While someone divides everyone into “tech developers” and “humanities designers,” Leah loves both the code and the design, so much so that an hour before the performance, she corrected the color hex codes in her presentation so that the color reproduction on the projector would be as much as possible conceived .
And the presentation itself was appropriate: she suggested looking directly at the code in terms of UX / UI. “We are used to thinking that UX is something for designers. But if you open the definitions of the words "usability", "UX" and "UI", they are generally not about design, they are much wider. " How to code the API to get a good user experience? Leah called the many components - reaching the end to the point that you need to be able to be not only professional, but also unprofessional: “We are used to portraying ourselves as more and more hardcore, but from the point of view of usability it actually hurts. When you know too much, you stop understanding usability issues. This is called the "curse of knowledge. " Leah pulled out of the timing, delaying the closing of the conference - but judging by the applause, many viewers would gladly listen to it again and again.
See you in Moscow in December! Let's see how many versions of Angular have time to get out before it.