脆文:https://www.threads.com/@thecat88tw/post/DS__HXfkROF
謝謝 @cab_late 花時間仔細閱讀並如此詳細的回應我的貼文,這兩天跨年比較忙,今天終於有時間坐下來針對他的疑慮提出幾點說明,大家參考看看,希望有幫助。
首先要先對 functionl call 的本質與目地有清楚的認知。
它是讓 LLM 操作外部資料(side effects)的主要途徑,也是最底層的基礎手法。
脆文:https://www.threads.com/@thecat88tw/post/DS__HXfkROF
謝謝 @cab_late 花時間仔細閱讀並如此詳細的回應我的貼文,這兩天跨年比較忙,今天終於有時間坐下來針對他的疑慮提出幾點說明,大家參考看看,希望有幫助。
首先要先對 functionl call 的本質與目地有清楚的認知。
它是讓 LLM 操作外部資料(side effects)的主要途徑,也是最底層的基礎手法。
| // Install npm i pg-mem --save-dev | |
| import { DataSource, Repository } from 'typeorm'; | |
| import { newDb, DataType } from 'pg-mem'; | |
| import { v4 } from 'uuid'; | |
| const setupDataSource = async () => { | |
| const db = newDb({ | |
| autoCreateForeignKeyIndices: true, | |
| }); |
| ruby '2.7.1' | |
| gem 'rails', github: 'rails/rails' | |
| gem 'tzinfo-data', '>= 1.2016.7' # Don't rely on OSX/Linux timezone data | |
| # Action Text | |
| gem 'actiontext', github: 'basecamp/actiontext', ref: 'okra' | |
| gem 'okra', github: 'basecamp/okra' | |
| # Drivers |
I heard some points of criticism to how React deals with reactivity and it's focus on "purity". It's interesting because there are really two approaches evolving. There's a mutable + change tracking approach and there's an immutability + referential equality testing approach. It's difficult to mix and match them when you build new features on top. So that's why React has been pushing a bit harder on immutability lately to be able to build on top of it. Both have various tradeoffs but others are doing good research in other areas, so we've decided to focus on this direction and see where it leads us.
I did want to address a few points that I didn't see get enough consideration around the tradeoffs. So here's a small brain dump.
"Compiled output results in smaller apps" - E.g. Svelte apps start smaller but the compiler output is 3-4x larger per component than the equivalent VDOM approach. This is mostly due to the code that is usually shared in the VDOM "VM" needs to be inlined into each component. The tr
Basecamp's new book Shape Up is now available online (https://basecamp.com/shapeup) to read page-by-page.
There is a .pdf version, but that's not the best format for Kindle / other eReaders. Instead, we can convert the page-by-page into an eReader friendly format.
NOTE: This has only been tested on Chrome
This is how you can conver the react docs to a .ePub / Kindle (.mobi) file to read in an eReader (or eReader app):
brew install pandoc via Homebrew)content/docsecho '' > ALL.md
for i in $(cat nav.yml | grep 'id:' | awk -F: '{print$2}')
do
5 Ways to Make HTTP Requests in Node.js
我们主要用 axios,因为它基于promise
上个项目只有一处用了 request, 因为它提供流处理
I've been deceiving you all. I had you believe that Svelte was a UI framework — unlike React and Vue etc, because it shifts work out of the client and into the compiler, but a framework nonetheless.
But that's not exactly accurate. In my defense, I didn't realise it myself until very recently. But with Svelte 3 around the corner, it's time to come clean about what Svelte really is.
Svelte is a language.
Specifically, Svelte is an attempt to answer a question that many people have asked, and a few have answered: what would it look like if we had a language for describing reactive user interfaces?
A few projects that have answered this question:
介绍不同分词器的文章不少,较经典的有BosonNLP 11款开放中文分词引擎大比拼
可惜这11款分词器只有IK和结巴一直在更新elastic的分词器插件,Boson的插件已经很久没更新
所以加上elastic自带的smartcn 也就只有三种分词器可选。
注1:smartcn基于中科院的ictclas 但用的是1.0, 似乎没再更新
| { | |
| "explorer.openEditors.visible": 0, | |
| "workbench.colorTheme": "Default Light+", | |
| "workbench.iconTheme": "vscode-simpler-icons", | |
| "workbench.sideBar.location": "right", | |
| // 需下載安裝 Fira Code 字型 (安裝 OTF 格式) | |
| // https://github.com/tonsky/FiraCode/releases | |
| // 需下載客製化過的 Microsoft YaHei Mono 字型 |