Usage scenarios are usually applications with high performance requirements, and some operations that need to be done in the back end can be done in the front end. Such as video decoding, image processing and so on.

Do we need to be like him? 99.9% of developers don’t have to learn it. WebAssembly is more about enabling people who originally wrote C++ and Go to do things on browsers that they wouldn’t have done otherwise.

The micro front end draws lessons from the idea of back-end micro services. The core of the micro front end is to unpack the originally huge applications. These separate packages can be independently packaged and deployed for operation, which can be directly regarded as disassembling an application into small modules.

The micro front end is suitable for large, old projects with many collaborators. For example, if you have a project that is very old and the technology stack is using an older version of JQuery or React. At the moment, if you need to use React 16 to develop new features, it’s definitely not practical to rewrite the entire application. At this point, you can solve the problem with a micro front end, using a new stack to write new functionality without affecting the old functionality. Or even more extreme, with a microfront-end your team can use each of the three frameworks on this project without affecting others.

If your project is small and you don’t have a lot of collaborators, there’s no need to do a micro front end, just learn about the problems it solves.

Serverless is a Serverless architecture, but it doesn’t really need a server. The server is still needed, but now I don’t need the server, just provide the code logic, it helps developers focus on the code level rather than the engineering level.

By far the most common category in Serverless is cloud functions (FaaS). Write the code and run conditions and throw them in the cloud. Don’t worry about deployment, capacity expansion, disaster recovery, etc., just call the functions.

Does the front-end need to learn Serverless? What do you think you need to learn this for?

Git Clone XXX is the simplest implementation of git clone XXX.

Scaffolding is typically used in projects to help developers quickly generate templates based on options, and incorporates a suite of common development and deployment tools.

Well, it’s handy if you want to build your own scaffolding. The core is to come up with several sets of templates, such as those for PC, mobile, multi-page, single-page applications, JS or TS. This allows you to create multiple templates and integrate Webpack configuration, NPM Script, and so on. Finally, use the command-line development library, give the user several options, and then go to the repository of each template to pull the code, over~

Of course, the above approach is not advanced, more advanced approach can also dynamically modify the template, if you want to achieve such a scaffold, recommended to see the scaffolding of the three frames directly.

While the front-end stack may look like a lot of stuff, it really is, and many of them aren’t worth learning. It’s enough to know what problems they solve and how they do it.

The last

Readers who think the article is good can give it a thumbs up and share any questions in the comments section.

In addition, the second open class of the author will be broadcast live at station B at 8:00 PM on January 12. If you are interested, you can scan the qr code and send “Open class” to get details of the live broadcast.

Wechat scan code to follow the public account, subscribe to more exciting content Add the author wechat group chat technology