boltzmann64

AI is a software just like operating systems and executables where open source absolutely dominates the industry. Remember when the compiler engineers optimized the shit out of llama.cpp.

Right now the bottleneck for AI software is compute and data. Moore's law is give us compute, StackOverflow, arXiv (and it's children like bioRxiv), gutenberg and others (3lib, anna, internet.org) will give us data.

It's a waiting game. Open source always wins.

reminds me of

It doesn't. It's model. All models are wrong (including quantum mechanics and attention) but some are useful. You understand the domain of the model, the problems it can solve, the math behind the models and use the model to make predictions. If you are competent at linear algebra and functional analysis, you can do quantum mechanics.

If you make the error of believing that quantum mechanics is ontological god's honest truth of nature, you will end up with blunders like using it to explain consciousness like Prof Penrose. His math was impeccable, but he was making a category error.

https://docs.moondream.ai/

Also, try fx.wtf as a replacement for jq. it comes with a in-built tui viewer that supports vi-keybindings. Ecmascript is built into fx.wtf so you can query the JSON with JS notation (where JSON was born). You can use any JS functions including map/reduce/filter or perform any kind of transformation instead of learning jq dsl that you will forget tomorrow.

Policy that is hard to pass: SIM binding for all messenger apps and automatic log out every 6 hours for desktop apps.

Even more egregious policy: Pre-install spyware that cannot be disabled.

Withdraw the egregious policy on outrage, and people think they have won the battle.

So, it doesn't matter if a AI can or cannot do clean room implementation. Unless it is a patent or trade secret violation, cleam room implementation doesn't matter.

In git, your repo is the canonical repo and that is where you work. You work on a new feature and when you are ready, you "git format-patch" and "git send-email" to the community via the mailing list or other developers. A discussion may happen and people may or may not decide to apply the patch to their own repositories, with "git am." This doesn't break every other developers' working copy because they decide how to apply the patches they got in their email. No central repo, no trunk, guaranteed by the d in git dvcs.