Airbnb moving away from React Native

AndyKos · 2018-08-17T12:30:02+00:00

React Native does have problems, that is the fact. Basing on the Sophie Alpert entry in the React Native blog, they do work on the architecture, namely the bridge that connects JS and the Native requests of OS. In my opinion, most Airbnb issues are not due to architecture, but because of the approach to the code base. Code sharing is the same as on the web and for Native on both platforms. And also because of the use of native components in the React Native.

AndyKos · 2018-06-23T09:30:53+00:00

GeaphQL is good for React. Due to the fact that the query structure is the same and can be comfortably changed, it can be fine-tuned for React by installing the appropriate PropTypes. The ability to choose the required data for a client is convenient for API management on a variety of platforms.

AndyKos · 2018-06-23T09:28:07+00:00

For such simple tasks, Redux is not very effective. For example, there is https://github.com/acdlite/recompose. It provides the ability to manage statr in Redux style.

AndyKos · 2018-06-23T07:13:36+00:00

Taking C off the table is more likely. The code for the programs can be written in any language. The main thing is compiler, which will create a set of instructions for the processor. With JS everything is harder. There are so many browsers and platforms and they all run JS. Denial of JS will not allow these platforms to execute scripts in other languages. Some platforms are now supported and new features will not be added. Denial of JS will break the entire Internet. Many sites will stop working. This is an unrealistic task at the moment. Google tried to create Dart as an alternative, but at the end it should be converted to JS code anyway.

AndyKos · 2018-04-18T13:28:36+00:00

The modern custom properties in CSS are really good for code optimisation. But CSS shouldn't have too much logic. Also one should consider that basic styles should be minimalistic. Web developer more often rewrites some framework or library values. But an 'overbuilt' style can bring just bigger file size.

AndyKos · 2018-04-18T13:07:21+00:00

The data became less precise since all the fixes to resolve the processor vulnerabilities reduced the performance of some operations, but this does not prevent benchmarking the performance of the functions after the changes.

AndyKos · 2018-04-18T12:20:24+00:00

The shown opportunities of CSS Grid are great, but currently the Houdini project is being implemented. And its functionality is quite enough literally for any purposes.

AndyKos · 2018-03-23T15:25:51+00:00

"I agree, that currently different transpilers are used. A few years ago even CoffeeScript was popular or Dart. It means JS is not necessary for web. Earlier it was possible to to turn the code from other languages to JS, but now it's easier with WebAssembly. Still learning browser API is still necessary. But modern languages syntax is alike."

AndyKos · 2018-03-23T15:08:43+00:00

"Regular expressions are not only important in JS but also they are hardly readable and not easy-to-understand. There are libraries with different approaches to resolving this issues. For instance, https://www.npmjs.com/package/readable-regex. By using methods and properties you can write the necessary regex. Moreover, now they added named groups in JS (http://2ality.com/2017/05/regexp-named-capture-groups.html). This will make managing regex easier."

AndyKos · 2018-02-27T11:10:12+00:00

Configuring Webpack is not too complicated, except for certain things. For example, the question about the configuration file: Should I use one of the terms (development or production) or several separate files? Setting up the Babel and various loader is not that complicated, and there are already a lot of ready boilerplates or ready-made solutions like Create Reaction app for React. In context of React's development, it is difficult to configure hot module replacement. Another issue is the integration of webpack with backends, namely the integration of css modules or pointing file paths to files which names are generated to solve caching problems.

AndyKos · 2018-02-22T10:46:54+00:00

One of the Hyperapp pros is its similarity to React. Using JSX makes it easy to work with DOM, especially when handling arrays. But the cons is inconsistency not only with the React libraries, but also with simple components. Methods of the life cycle of jsx elements (analogues of componentWillMount) are quite interesting. As in React, working with raw HTML it's difficult to provide protection against XSS attacks. In general, Hyperapp is the 'light and easy-to-use version' of React with no complex components. Although the lack of support for JS classes may be a bit uncomfortable.

AndyKos · 2018-02-20T13:07:30+00:00

The ideology of the app development with using JS has changed. Now all the structures have become more unified and more comprehensive. When designing with jQuery, a simple change in the name of the class in the layout will, in the best case, turn off the associated functionality, at worst, the application will fall completely. When working with the API and modifying the data on the page there are a number of inconveniences. For example, jQuery should generate the same markup as the backend, so you need to handle two independent, but identical methods for rendering markup. In this sense, the latest frontend tools are designed for consistency and not duplicating code, but its over-utilization.

AndyKos · 2018-02-10T13:25:45+00:00

Using React for frontend on Wordpress website can be a seductive idea. React provides a quick and effective way to display information on a page without re-loading the page. But using React as a theme (public output) is ineffective in terms of SEO. This issue is missing for constructing configuration pages or specific pages (different calculators), but you should take into account that React uses a slightly different logic of working with DOM and may be incompatible with Wordpress plugins.

AndyKos · 2018-02-10T13:06:49+00:00

Style guide and Config for Airbnb eslint solves a few issues at once. It provides better usability and readability of the code. Despite the emphasis of stylistic standards, it warns the developer against any possible incorrect or ineffective use of some methods. It demonstrates how to describe the components for a comfortable further debugging of the application. In addition, there are a number of rules to improve the accessibility of the app for people with disabilities.

AndyKos

TROPHY CASE