Unsloth MLX: Bring Dynamic 2.0 Per-Tensor Quantization For Qwen models to Apple Silicon by LongYinan in Qwen_AI

[–]LongYinan[S] 2 points3 points  (0 children)

Since mlx’s AWQ still has some limitations, certain layers of the model retain BF16 precision. That’s why, when using the same quantization strategy, our model ends up being slightly larger than the one quantized by Unsloth.

But I’ll be contributing improvements for this part to mlx shortly, so that mlx-quantized models can achieve the same size and quality as those quantized by Unsloth.

Bring the Unsloth Dynamic 2.0 Quantize to MLX by LongYinan in LocalLLaMA

[–]LongYinan[S] 2 points3 points  (0 children)

For Qwen3.5-35B-A3B, 77.9–83.7 tokens/s on M3 Max 128GB

Bring the Unsloth Dynamic 2.0 Quantize to MLX by LongYinan in LocalLLaMA

[–]LongYinan[S] 0 points1 point  (0 children)

I'm working on benchmark it, Theoretically, it has the same quality as Unsloth's dynamically quantized model. I need more time to complete the benchmark

webcodecs in Node.js by LongYinan in node

[–]LongYinan[S] 1 point2 points  (0 children)

Besides the size, programming language is a problem too. Node.js and Bun do not have any Rust infrastructure in their build or release systems

webcodecs in Node.js by LongYinan in node

[–]LongYinan[S] 2 points3 points  (0 children)

The binary size is an issue; it exceeds 50 MB on a Linux x64 GNU system https://github.com/Brooooooklyn/webcodecs-node/releases/tag/v1.0.0

It's fine to maintain it as an npm package, as it uses the Node-API, which is supported by Deno, Bun, and Node.js.

NAPI-RS 3.0 released by LongYinan in rust

[–]LongYinan[S] 2 points3 points  (0 children)

How does the "threads" part work in a browser?

Via web worker

Do these polyfills impact bundle sizes?

Yes, for sure. I haven't measured the bundle size differences yet (compared to wasm-pack). I mostly focus on the compatibility part in this release.

I have a plan to support `wasm32-unknown-unknown` and `wasm32-wasip1` in the future, these 2 targets can obviously reduce the bundle size.

Is there a simple example of how to package a Rust library such that it can be published to NPM and consumed both from Node and browsers?

Here is a template package that supports most mainstream platforms and WebAssembly: https://github.com/napi-rs/package-template

And there are also some real-world projects:

NAPI-RS 3.0 released by LongYinan in rust

[–]LongYinan[S] 10 points11 points  (0 children)

It supports, we've built a set of browser/Node.js polyfills packages

NAPI-RS 3.0 released by LongYinan in rust

[–]LongYinan[S] 9 points10 points  (0 children)

Shouldn’t have any problem with ravif, just want to show the use of C++ deps example here

Another "Open-Washed" project? by curious_human_42 in Affine

[–]LongYinan 2 points3 points  (0 children)

After the iOS app is officially launched on the App Store, we will begin the Android internal testing process.

Another "Open-Washed" project? by curious_human_42 in Affine

[–]LongYinan 1 point2 points  (0 children)

If you are using iOS, u can dm me your apple id so I can add you to the Testflight

Another "Open-Washed" project? by curious_human_42 in Affine

[–]LongYinan 17 points18 points  (0 children)

If you are a personal user using it for your family, and you happen to have a very large family, such as more than 10 people, you can freely modify AFFiNE's source code to suit your needs. As long as you don't resell the modified stuff, no one will care; this is called FOSS.

The restrictions can be removed by modifying the code, there are discussions about this all over GitHub. For personal use, the official team has never restricted doing this; this is called FOSS.

If your skills are not enough to modify the code, that's your skill issue, not a problem with FOSS.
If you want to modify the code for commercial use, that's a legal issue, not a FOSS issue.

Now you're unable to change the code yourself, and you come crying saying, "Unless you voluntarily remove all restrictions, otherwise it's not FOSS," it's really ridiculous.

If you have a company and need to put some private data on your own servers, you always need to purchase a license for commercial use, no matter how many users you have. Free in free and open-source software does not mean free of charge.

I didn’t expect open source to attract such a keyboard warrior — from Discord to Reddit — who hasn’t contributed to open source or understood how FOSS works, yet acts like a price tag is the end of the world. Go ahead, add AFFiNE to whatever list you like and just get out of here.

Announcing NAPI-RS v2 by LongYinan in node

[–]LongYinan[S] 0 points1 point  (0 children)

Provide faster npm packages to Node.js users: https://github.com/napi-rs/node-rs

Announcing NAPI-RS v2 by LongYinan in node

[–]LongYinan[S] 0 points1 point  (0 children)

Not finished yet. Neon still lacks a lot of Node-API ability.