1,014 karma · joined August 27, 2018
None of these restrictive arguments would stop me from doing the next 2-3 steps even, after buying those many discs.
Nobody needs to have every functionality of HTTP offloaded to MCP at all, at this point.
I'll stick to the bare minimum that works.
Today, most people can vibe code their own OSes and emulators within a day or two. You're telling me an entire country can't do it? That is so defeatist.
Plus, there are some young people who are seemingly bored and have an economy not plagued by the same lobby issues as the US. They might be able to get cracking on it.
Given the current US debt situation, Japan is in a position to dictate its local manufacturing terms and actually do what it wants to do.
Meanwhile, in the US, the products being sold are highly lobbied and relies on the government moat to be protected in order for things to work. The side effect of that also means that some of the companies really don't lead to innovative outcomes in the long run, and are in positions of lucky power. This leads to poorer customer experiences, poorer technical outcomes and non competitiveness in the long run, like manufacturing. This trend needs to be reversed and the US leaders should be held responsible for doing the right thing here.
I'm well aware of TRON and its capabilities. I really think Japan can develop this and market it locally, without requiring all the bloat the current OS world comes with; It might actually turn into a speed and security advantage if they did this right.
It's like 80% of the work after raising a PR is just socializing ideas and getting people to agree on stuff
See https://github.com/guilt/TinyToT which already builds a powerful reasoning model where you drop your traces as Markdown, it picks it up and runs. Ditto for data, so you have both separately and can refresh one and not mess up the other. Zero training, Zero RL. Code is there, try it yourself.
Someone's doing a company out of this? Great, let more people discover the truth.
In case other people have done a better job of explaining what else they have done or have used back in the day, add it in this thread.
I've run two NAS appliances for 15+ years now, and never had to worry about any of this, because I just run good old Community Linux or BSD on it.
I can plug whatever PCIe card I want, as much storage as I want and from whom I want.
I am adding multi-modality to https://github.com/guilt/TinyToT, and I see that dis-aggregating capabilities, very similar to how our own sensory organs work, seems to be paying off quite well.
This project was built on structural sparsity, do away with any requirements to train models on largely outdated corpus of data, and only train it on reasoning logic. Because if models can use tools well and retrieve everything else, it greatly would reduce the need for large language models.
Further, when generating traces, I ran a benchmark that showed that on grounded data, n-grams and simple retrieval outperformed transformers on efficiency (See https://github.com/guilt/Transformers) and wanted to try scaling this up to much larger traces.
It worked quite well. Next improvement would be to run this with a BERT model and add more do-not-know traces and the Claude style neurotic self-doubt/self-verify traces and test it out a bit more.
If the entropy required to route people to the relevant answers is very low, full dense attention is a waste of compute. That's the theory being pressure tested here. The more I do this exercise, the more I am getting convinced that smaller models are good enough.
Why don't you go and actually build something novel? People need to understand better how current models work, and if retrieval indeed solves 99% of the problems people care about, then those other models aren't doing anything super novel either.
I'm not arguing here: The code is out there, data is out there. Do better if you know something actually better. Thanks!
So there's going to be more and more research coming out telling you what size of models are really needed to solve a specific task. When you combine that with RSI, the next frontier would be to get this model as close to the real world with instant data and instant reasoning, no fine tuning at all. And see how this one could iterate itself.
I'll also be trying out more tiny models and seeing if they can call each other, and be as effective; You will also be seeing me trying this, in addition to what I'd already mentioned in the other reply.
P.S. Building something that proves that you don't need those many params even.
- Instances they ghosted
- Interviewer behavior
- Scope of work and funding red flags
- Generic red flags found on Glassdoor, Team Blind etc.
Now I just remember it without needing that list