Geek asks and answers

Effective effects of client-side and fiber visualization in Meteor

Many people commented on how Fibers (which gives you synchronous code in Node.js) breaks compatibility with 99% of npm packages. I'm more interested in performance implications.

Will it cancel "Node.js is really fast, look, it's asynchronous / event based!" argument? What is the practical significance of baking the Meteor team in fibers?

In addition, after deploying a huge rewrite where pages were displayed on the client side, Twitter reversed its decision in favor of serving HTML from the server to improve page load times. What does this mean for Meteor performance limitations (especially when loading the first page)?

+5
source share
1 answer

The development team plans to implement server-side rendering to circumvent the problem of loading the first page, as well as support search engines by sending the source data that is displayed to the user as part of the HTML that he sees the initial data, while preserving everything else.

+4
source

More articles:


All Articles