chatcraft.org
WASI
chatcraft.org | WASI | |
---|---|---|
65 | 45 | |
121 | 4,614 | |
- | 1.9% | |
9.5 | 6.9 | |
1 day ago | 11 days ago | |
TypeScript | Rust | |
MIT License | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
chatcraft.org
-
Show HN: I made a better Perplexity for developers
My https://chatcraft.org offers free models and is open source. They start throttling under heavier usage tho.
Gonna add some free models with search in future
-
Improve Download Speeds with Concurrency
This week, I came across an interesting problem while working on an issue in ChatCraft.
-
Concluding OSD700
This has been a true privilege working on a cool project with a great team, and under an exceptional mentor.
-
ChatCraft v2.0.0
Finally, Its the last week of semester and we had our last class of Open Source Development Project with David Humphrey. I would like to thank David for being my professor and mentor. I've taken 30 courses in Seneca and I would like to say that the three courses by David Humphrey were the one in which I learnt the most, i.e two open source courses which enhanced my github profile, gained confidence in git skills. Also before the courses ,I always wanted to contribute in Open Source but had no idea where to start from. I would also like to thank Taras Glek for giving me an opportunity to work on ChatCraft.org. Working on ChatCraft has been the biggest project I've ever worked on till date.
-
ChatCraft week 14: Releasing v2.0!
This week we met with Taras, the founder of ChatCraft online to showcase our contributions and get some professional advice from him. It was very rewarding to see what we managed to get done in the span of four months with our small team of six!
-
Contributing to Open Source Project ChatCraft
This semester has been a whirlwind of coding, collaboration, and learning as I dove headfirst into the world of open source development with ChatCraft. My journey was marked by significant contributions, including 14 pull requests (PRs), the development of 4 major features, and the squashing of numerous bugs. Here's a closer look at what I've accomplished and the invaluable lessons I've learned along the way.
-
Release v1.9.0 - ChatCraft.org
PR 580 Merged
-
ChatCraft 2.0 is almost Here!
That's right. The BIG 2.0 release for ChatCraft is scheduled by the end of next week. We have been working to build on ChatCraft's existing functionality in its v1.0 state for almost 13 weeks now, and have successfully added lots of cool features (even this post's cover photo is generated by ChatCraft).
-
ChatCraft week 13: Fixing bugs
This week on ChatCraft, I fixed a few bugs I found in production that have arisen since the new custom provider feature was implemented. I was able to find these bugs because I reviewed many PRs this week and during testing those PRs I was able to see some abnormal behaviour.
-
ChatCraft Adventures #13, UI Changes
ChatCraft Release 1.9 is available here
WASI
-
WASI 0.2.0 and Why It Matters
WASI Co-chair here. Nothing in WASI is "somehow blocked by Google", or indeed blocked by anyone at all. Graphics support in WASI hasn't been developed simply because nobody has put energy into developing graphics support in WASI.
At the end of 2023 we counted around 40 contributors who have been working on WASI specifications and implementations: https://github.com/WebAssembly/meetings/blob/main/wasi/2023/... . That is a great growth for our project from a few years ago when that issue was filed, but as you can see from what people are working on, its all much more foundational pieces than a graphics interface. Also, if you look at who is employing those contributors, its largely vendors who are interested in WASI in the context of serverless. That doesn't mean WASI is limited to only serverless, but that has been the focus from contributors so far.
By rolling out WASI on top of the WASM Component Model we have built a sound foundation for creating WASI proposals that support more problem domains, such as embedded systems (@mc_woods and his colleagues are helping with this), or graphics if someone is interested in putting in the work. Our guide to how to create proposals is found here: https://github.com/WebAssembly/WASI/blob/main/Contributing.m... .
- WASI Launching Preview 2
-
Missing the Point of WebAssembly
> As I understand it, it's not even really possible today to make WebAssembly do anything meaningful in the browser without trampolining back out to JavaScript anyway, which seems like a remarkable missed opportunity.
That's the underlying messy API it's built on. There are specs to make the API more standardized like https://github.com/WebAssembly/WASI
But overall, yeah, it feels like a shiny new toy everyone is excited about and wants to use. Some toys can be fun to play with, but it doesn't mean we have to rewrite production systems in it. Sometimes, or most of the time, toys don't become useful tools.
-
Running WASI binaries from your HTML using Web Components
Snapshot Preview 1 is the standard all tools are building to right now. The specification is available here: https://github.com/WebAssembly/WASI/blob/main/legacy/preview...
It's pretty unreadable though!
Preview 2 looks like it will be a big change, and is just being finalised at the moment. I'd expect that when preview 2 is available there will be an improvement in the quality of documentation. I'm not sure how long it will take after release for tools to start switching to it. I'd expect Preview 1 will still be the main target at least for the rest of this year.
-
WASI: WebAssembly System Interface
> Like WTF does this mean? The repo tells me nothing
Directly above the sentence you quoted:
"Interposition in the context of WASI interfaces is the ability for a Webassembly instance to implement a given WASI interface, and for a consumer WebAssembly instance to be able to use this implementation transparently. This can be used to adapt or attenuate the functionality of a WASI API without changing the code using it."
> and I've still yet to see a clear write-up about what WASI is.
In the same document: [0]
> WTF is wit?
The first link in that document ("Starting in Preview2, WASI APIs are defined using the Wit IDL.") is [1].
> I click on "legacy" and I see preview0 and preview1, which are basically unreadable proto-specs.
The README for the legacy directory [2] clearly explains what they are.
> Where's a single well-written WASI spec?
"Development of each API happens in its own repo, which you can access from the proposals list." [3]
> Whatever WASI is doing, I don't like it.
Clearly not - you've gone out of your way to ignore all of the documentation that answers your questions.
> And neither does AssemblyScript team apparently
The AssemblyScript team have a bone to pick with WASI based on their misunderstanding of what WASI is for (it is not intended for use on the web) and WASI's disinterest in supporting UTF-16 strings. You can see for yourself in [4].
[0]: https://github.com/WebAssembly/WASI/tree/main#wasi-high-leve...
-
A Gentle Introduction to WebAssembly
The Bytecode Alliance initiated a sub-project called the WebAssembly System Interface (WASI). WASI is an API that allows WebAssembly access to system features such as files, filesystems, Berkeley sockets, clocks, and random numbers. WASI acts as a system-level interface for WebAssembly, so incorporating a runtime into a host environment and building a platform is easier.
-
Spin 1.0 — The Developer Tool for Serverless WebAssembly
We are excited to contribute back to Wasmtime and the component model, as well as to new projects and proposals emerging in this space (such as new Wasm proposals, like WASI Preview 2, wasi-keyvalue, wasi-sql or wasi-cloud).
-
The Tug-of-War over Server-Side WebAssembly
I've been reading the following repositories.
https://github.com/WebAssembly/WASI/blob/main/Proposals.md
What are some alternatives?
lastmileai-python - Python SDK
.NET Runtime - .NET is a cross-platform runtime for cloud, mobile, desktop, and IoT apps.
uniteai - Your AI Stack in Your Editor
webgpu-wgsl-hello-triangle - An example of how to render a triangle with WebGPU using WebGPU Shading Language - the "Hello world!" of computer graphics.
gw2combat - A GW2 combat simulator using entity-component-system design
threads - Threads and Atomics in WebAssembly
kuru-kuru - A reimplementation of that one website in Fresh.js
wasi-libc - WASI libc implementation for WebAssembly
whisper-live-transcription - Live-Transcription (STT) with Whisper PoC
node-sqlite3 - SQLite3 bindings for Node.js
talk - Let's make sand talk
gpuweb - Where the GPU for the Web work happens!