VueConf2021 official video

  • Yu Yuxi: Talk about the ecological progress of Vue3
  • Vite, the next generation Web tool
  • Vue3’s compilation and optimization efforts
  • Optimize code for a new generation of build tools
  • Explore JSX in Vue 3
  • Composable Vue
  • Build a high-performance Flutter application with vue.js
  • Develop multi-terminal applications based on Vue3.0
  • Lightning Share: Element3, a hyperrealistic UI component library with Webgl customization

This paper mainly focuses on the topic of Vue building high-performance Flutter application

At present, cross-end has been a topic that the front end cannot get around. With the popularity of IoT devices, more and more “ends” emerge in our daily development. Since The introduction of Hybrid and React Native (Weex), Flutter has emerged as a new favorite in recent years thanks to its streamlined rendering pipeline and its ability to draw its own rendering. However, its development model with Dart + Widgets and its separate ecosystem from the front end resulted in high development costs. Based on this background, we explore a W3C standard-based application of Flutter, which connects to the front-end ecology up and ensures multi-end consistency down through self-drawing.

The above is the share of The VueConf2021 brought by Alibaba Tao Technology Department. But the first half of his share is almost all about the history of the cross and why Flutter came into being and became popular. Like an internal report for Ali: P, but after his sharing, more VueConf2021 best Green brother soul torture:

Weex has been turned yellow, how long can you maintain this one?

Just kidding, for those of you who don’t know about Flutter, LET me share my understanding of Flutter

What is good about Flutter?

  1. Cross-end consistency
  2. Cross-end consistency
  3. Cross-end consistency

No kidding here, Flutter certainly has some other advantages, but in my opinion, they are not as good as cross-end consistency. In other words, cross-end consistency is one of the core reasons why a Flutter can stand on a cross-end frame. Because of this very sexy property, developers are willing to adapt and accept the “stubbornness” of the Flutter framework…

The obstinacy of Flutter?

I don’t know why Flutter is stubbornly designed the way it is today. It is not difficult to learn, but for a developer who is used to the habits and ecology of Web front-end development, adapting to a different set of styles and habits comes at a considerable cost.

Plus, it’s getting tough for Web front-end engineers! Internal volume disaster: p

Even if you master Flutter, you can’t always write Flutter. You have to hop back and forth between Dart/JS, Flutter/Vue, which can be quite uncomfortable.

For instance the author is such, often cerebrum is anoxic so, memory is deranged…

Let me give you a couple of examples

  • An asynchronous function
//javascript
async function func(){}//dart
func() async{}Copy the code
  • Random value
//javascript
Math.random();
Math.floor(Math.random()*5);

//dart
Random().nextDouble();
Random().nextInt(5);
Copy the code
  • Log print
//javascript
console.log();

//dart
print();
Copy the code
  • An array of
//javascript
var arr = [];
arr.push(1);
arr.push(1.2.3.4.5);

//dart
var arr = [];
arr.add(1);
arr.addAll([1.2.3.4.5]);
Copy the code

I’m just scratching the surface of these differences. Would you go crazy if you bounced between these two habits over and over again?

So how good would it be to take advantage of the cross-endpoint consistency of Flutter while still writing the code that Web front-end developers are used to? Kraken was born in this context

Kraken is a what

Open the Kraken (Openkraken.com/)

Beihai (English name: Kraken), a Web rendering engine developed by Alibaba for 3 years, is officially open source. It is committed to creating a scalable, cross-platform, high-performance rendering engine, and has been used in youku, Damai, Tmall and other business scenes.

So what kraken can do, you can go to the website, my understanding is

Weex = JS+Vue+ native rendering

Kraken = JS+Vue/React/Rax+Flutter self-render

Flutter was born out of web standards, after the Chrome team got rid of some of the messy web specifications…

So can I take it that Kraken has brought all those web specifications back together

That is to say, Kraken = implemented a Webkit with Flutter. For this understanding, I asked my friends in Flutter China…

A review of hydrology, nothing dry…

Feel free to comment in the comments section. What do you think?