从数据传输链路、输入端(麦克风、搜索框)、投放广告业务商(是否有必要选择这种方式)、“偷听平台”(被怀疑的对象搭建一个收集信息分析广告平台是否划算是否有客户)等角度来分析,监听属被动成本大收益小,更多可能在于被我们忽视掉的 输入法 工具,或者是一些用户好友的行为依赖。
哈哈哈,好像跑了技术的标题,但做需求的确实可以通过窥探整个环节来辩证一件事情的真伪,全局思维需要不断培养。
UI框架之上的框架,指Next.js这样的东西;满足基本要求,可拓展下一级的框架;
就像元规则,所有规则都遵守的规则;
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR!
npm ERR! While resolving: tolstoy-v3-web@2.0.0
npm ERR! Found: @hot-loader/react-dom@17.0.1
npm ERR! node_modules/@hot-loader/react-dom
npm ERR! @hot-loader/react-dom@"^17.0.2" from the root project
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! @hot-loader/react-dom@"^17.0.2" from the root project
npm ERR!
npm ERR! Conflicting peer dependency: react@17.0.2
npm ERR! node_modules/react
npm ERR! peer react@"17.0.2" from @hot-loader/react-dom@17.0.2
npm ERR! node_modules/@hot-loader/react-dom
npm ERR! @hot-loader/react-dom@"^17.0.2" from the root project
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
./node_modules/@ant-design/react-slick/node_modules/lodash/debounce.js Module build failed: Error: ENOENT: no such file or directory, open ‘D:\tencent_huyu\tolstoy\tolstoy_web_v3\node_modules@ant-design\react-slick\node_modules\lodash\debounce.js’
删除node_modules文件,根据提示–force
下拉加载优化思路:(自认不能成)
全量加载元数据(只读取关键字段:id、code、name) ---- 设计优先级机制进行评分(最长公共序列、编辑距离) ---- 根据分数进行排序 (node的 worker_threads (node v10 就开始提供)来处理。
worker_threads 跟node的 cluster 模块不一样,cluser 模块是for node进程安全稳定用,可以按照cpu核数分为主进程和子进程,不同子进程之间内存不共享。但是worker_threads是为for cpu 密集计算, 内存可以共享 ;; 浏览器使用 webworker)— 分页机制返回
