Sukka

@curbengh We could even release 5.0.0 first, then add multi core support from 5.1.0.

@curbengh We could start with `backtick_code` filter. Take a look at the flamegraph: https://29e28e2d8f6f8fdb247ad2c47788857d003fd894-12-hexo.surge.sh/flamegraph.html It seems to be a long task.

@tuananh LGTM! It seems definitely better than my WorkerPool: https://github.com/hexojs/hexo-util/pull/212/

> haven't gotten around fixing it yet. Not sure if it has anything to do with the way hexo calls all the filter @tuananh The entire `hexo` context just can...

Here's what we can learn #4368 According to the [documents of the worker_threads](https://nodejs.org/dist/latest-v12.x/docs/api/worker_threads.html#worker_threads_port_postmessage_value_transferlist): > `value` will be transferred in a way which is compatible with the [HTML structured clone algorithm](https://developer.mozilla.org/en-US/docs/Web/API/Web_Workers_API/Structured_clone_algorithm)....

Instead of `worker_threads`, I am considering using `cluster` API instead. `cluster` API is much simpler, and is stable since Node.js 4.0. It has no "structured clone algorithm" things as well....

@tommy351 has some exprience on [migrating to monorepo](https://zespia.tw/blog/2020/05/10/yarn-2-and-monorepo/). Hopefully he could give us some suggestions.

[Next.js](https://github.com/vercel/next.js) uses lerna. [React](https://github.com/facebook/react) uses yarn workspace. [Babel](https://github.com/babel/babel/) used to use lerna, and it is now using yarn workspace, too. Microsoft has [Rush](https://github.com/microsoft/rushstack). So which one should we use? @tomap...

> Isn't the sandbox supposed to help us test that? What are the things that you want to validate? Well here is a thing. We just have *so many repos*...

> Sure, so now, plan and then do! > > 1. Do some tests. > 2. Once ready, convert hexo into a monorepo but with only hexo in it, ready...