one main marketing leverage of 23andMe, AncestryDNA, etc are fulfilling the curiosity of people who want to know which part of the world their genes are from. I guess that dataset should be preparatory.
for vibe coding stuff, especially when you're outside touching grass, I believe MacBook Neo is perfect. it fills the gap between the phone remote control (which is too painful for chatting with ai cli) and, well, not having any dev device.
i've been a zed user for almost 6 months. i've encountered maaany bugs which i reported, or that were already reported. they're still there. meanwhile, every single update shipped a feature or bugfix for "ai agents".
not sure how 1.0 ships with that massive pile of bugs. but ai agents are the first-class citizen in this editor, and developer experience is not a priority.
funny thing is i uninstalled zed right before the 1.0 release. kinda relieved i didn't miss anything.
I have a few lightweight apps using deepseek api, and funny how the initial credit I topped up for using r1 is still left.
Nothing makes the user happier than getting more for less.
cc: anthropics with its fancy token-wasting claude code "features"
in my results, accuracy-wise Ternary-Bonsai-8B is on par with Qwen3.5-4B. But in accuracy-per-byte, bonsai is the clear winner:
=> Ternary-Bonsai-1.7B achieved 65.1% from 462 MiB, beating Qwen3.5-0.8B by 12 points while being ~5% smaller on disk.
=> Ternary-Bonsai-4B is the accuracy-per-byte winner above 1 GiB. 83.0% from only 1.1 GiB, within 2 points of Qwen3.5-4B at 40% of the weight size.
they show strong promise on edge devices and where disk space is limited. I think this lab is worth watching.
I recall a Qwen exec posted a public poll on Twitter, asking which model from Qwen3.6 you want to see open-sourced; and the 27b variant was by far the most popular choice. Not sure why they ignored it lol.
> This project is early and experimental. Core concepts are settled, but expect rough edges. Local mode: relatively stable - Hub-based workflows: ~80% verified - Kubernetes runtime: early with known rough edges
i guess gastown is a better choice for now? idk i don't feel good about "relatively stable"
People in the comments are, in my opinion, overcomplicating this and making it more philosophical than it needs to be. The reason for their decision is dead simple: there aren’t enough GPUs, so they have to cut access somewhere, and they’re starting with claw.
It’s really that straightforward. If tomorrow they decide GPUs are better allocated to enterprise use, they could start removing the $20 plan just as quickly overnight, the same way they did tonight.