HackerTrans
トップ新着トレンドコメント過去質問紹介求人

brian_love

12 カルマ登録 4 年前

投稿

[untitled]

1 ポイント·投稿者 brian_love·8 日前·0 コメント

[untitled]

1 ポイント·投稿者 brian_love·9 日前·0 コメント

Threadplane: Angular agent UI framework graded A for supply-chain trust

threadplane.ai
3 ポイント·投稿者 brian_love·10 日前·0 コメント

Eve validates the shape. Now pick your runtime

dawnai.org
2 ポイント·投稿者 brian_love·26 日前·0 コメント

[untitled]

1 ポイント·投稿者 brian_love·4 年前·0 コメント

コメント

brian_love
·9 日前·議論
[flagged]
brian_love
·9 日前·議論
[flagged]
brian_love
·10 日前·議論
[flagged]
brian_love
·10 日前·議論
I'm building a meta-framework for LangGraph similar to eve and flue that uses file-based routing, tools, etc. Building developer tooling using agents in the past with codex and opus has been limited, especially with regards to strong typing and DX. Fable 5 is changing this for me.
brian_love
·26 日前·議論
[flagged]
brian_love
·3 年前·議論
If Apple can leverage their silicon to run models on your physical device at speeds that are acceptable, this could be a game changer for generative AI.
brian_love
·4 年前·議論
My colleague posted an interesting article that addresses the disparity between an end-user of a typescript library and being a library author.

As the user of a library, not only do I hope for excellent documentation, but I also hope that the library authors have designed an ergonomic API that provides clear and consistent typings when using TypeScript. What I acknowledge I lack is a clear understanding of the level of effort that is required. Designing and building a library is challenging, creating documentation takes time, and support TypeScript types is another burden that I place on library authors.

Check out the article: https://liveloveapp.com/blog/2022-08-23-overcoming-typescrip...
brian_love
·4 年前·議論
My colleague posted an interested article that addresses the disparity between an end-user of a typescript library and being a library author.

As the user of a library, not only do I hope for excellent documentation, but I also hope that the library author have designed an ergonomic API that provides clear and consistent typings when using TypeScript. What I acknowledge I lack is a clear understanding of the level of effort that is required. Designing and building a library is challenging, creating documentation takes time, and support TypeScript types is another burden that I place on library authors.

My goal of sharing this article is to add to the discussion of a recent article titled "TypeScript is terrible for library authors" (https://erock.prose.sh/typescript-terrible-for-library-devel...).