You get "Grok Build" (the CLI) that uses the Cursor and/or Grok 4.5 models when you buy SuperGrok, which is like $300/year. I don't know if there is a feature-to-feature comparison by anyone on this, but you can get access to these models with unmetered tokens with SuperGrok.
It depends how much of that is services. If the device is hardware constrained, having an option to boot into a different set of services can be useful. Like a way to have more than a single lean thing, instead of a single bloated one.
Originally the word "Kanban" was used by Toyota to describe their card system that helped them achieve several important things, one of them was to NOT work on too many things at once. The other one was to visualize the work. And in general Kanban was used to manage the flow of work so that defects don't get through.
This tool on the other hand is all about "jam as much work as you can come up with into being created in parallel". Obviously there is no managing of any flow of quality outputs, and no limiting of any work because you just shove everything into the agent and burn tokens like crazy.
Calling this a "Kanban" really irks me ... its like blasphemy or something.
It is a way to switch into a different configs. Just like when you switch to a new set of packages when you update your channels (or flake) and you get activated with the new versions. Same thing with specializations, just you can choose to have a different set of packages activated and enabled in each different specialization. Like having multiple different configs in one.
It is just a Linux device. Other people will install NixOS on it anyway, and use specializations if the whole idea of swapping device roles in-and-out is viable. I don't really understand why would the team that already got a full plate decide to also invent a whole new Linux system while they're creating their hardware device.
Instead of re-inventing Linux distributions for FlipperOS on top of Debian. They should just choose to base it on NixOS which already has these "profiles" as a built-in feature called "Specializations" https://wiki.nixos.org/wiki/Specialisation
So you have some folders with markdown files ... which are insanely hard to query without a tool ... impossible to traverse via their relationships ... and you call that a graph database? WHAT?!
Clicked the link expecting to see some tool or method that actually allows graph-like queries and traversals on files in a file system, all I found was some rant about someone on the internet being wrong.
I would argue that Desktop Linux finally took off because of Steam Proton, and because of Windows 10/11 and macOS starting version fartascular or whatever their versions are named.
Diffusion models for images are already pretty much binary code generators. And we don't need to treat each bit individually, even in binary code there are whole segments that can be tokenized into a single token.
Regarding training, we have many binaries all around us, for many of them we also have the source code in whichever language. As a first step we can use the original source code and ask a third party model to explain what it does in English. Then use this English to train the binary programmer model. Eventually the binary programmer model can understand binaries directly and translate them to English for its own use, so with time, we might not even need binaries that have source code, we could narrate binaries directly.
Why would you think its more complex? There are less permutations of generating transistor on/off states than there are all the different programming languages in use that result in the exact same bits.
Who said that creating bits efficiently from English to be computed by CPUs or GPUs must be done with transformer architecture? Maybe it can be, maybe there are other ways of doing it that are better. The AI model architecture is not the focus of the discussion. It is the possibilities of how it can look like if we ask for some computation, and that computation appears without all the middle-men layers we have right now, English->Model->Computation, not English->Model->DSL->Compiler->Linker->Computation.