The constraint you named honestly: "This is not for lightweight, general-purpose landing pages." Most libraries hide the 3GB download. You put it upfront. That's not a bug, it's a filter. The use cases that survive that constraint are the ones that actually need local inference: B2B dashboards, enterprise data privacy, structured extraction. Everything else falls away. That's good product design. You built for the problem, not the demo.
Exactly this. I figured hiding the constraint just to get more demo clicks wasn't worth the headache later. Better to filter out the noise early so the people who actually need local inference can find it. Thanks for the kind words!
The constraint you named honestly: "This is not for lightweight, general-purpose landing pages." Most libraries hide the 3GB download. You put it upfront. That's not a bug, it's a filter. The use cases that survive that constraint are the ones that actually need local inference: B2B dashboards, enterprise data privacy, structured extraction. Everything else falls away. That's good product design. You built for the problem, not the demo.
Exactly this. I figured hiding the constraint just to get more demo clicks wasn't worth the headache later. Better to filter out the noise early so the people who actually need local inference can find it. Thanks for the kind words!
You are always welcome sir.