Being able to run docker containers on the web will immediately unlock so many usecases for my work! Right now I've been trying to get a Python sentence parser to run in the browser but it requires a lot of the ecosystem (Pytorch and such). Which is not trivial to compile to WASM.
That would fit our vision for a new generation of Web apps with traditional server-side payloads running client-side, with lots of positive impacts on user privacy and operational costs.
The main difficulties right now are two:
* Most docker containers are 64-bit, while CheerpX currently only support 32-bit x86 code
* Due to CORS limitations it is not currently possible to downloaded layers from repositories such as Docker Hub
The first limitation will be eventually fixed, the second one will require a specialized repository, a proxy, or co-operation from the existing repositories.
A similar thing has happened with Twitter. After the Musk takeover and the removal of SMS for auth something has changed they keys of the 2FA authenticator. My old keys don't work and my "ticket" has been waiting on Twitter support (which were probably all fired) for resolution.
This is absolutely wonderful, I am a HUGE fan of local first apps. Running models locally is such a powerful thing I wish more companies could leverage it to build smarter apps which can run offline.
I tried this on my M1 and ran LLama3, I think it's the quantized 7B version. It ran with around 4-5 tokens per second which was way faster than I expected on my browser.
Aider has a "token budget" for the repository map (--map-tokens, default of 1k). It analyzes the AST of all the code in the repo, the call graph, etc... and uses a graph optimization algorithm to select the most relevant parts of the repo map that will fit in the budget.
There's some more detail in the recent writeup about the new tree-sitter based repo map that was linked in my comment above.
I remember vividly when going out with my family in the year 2000. There used to be a stretch of road filled with vultures. Then a few years later they just stopped existing. I haven’t seen a real vulture since then.
I've been programming professionally close to 16 years. Here is what I can remember of my code:
# Job 1 (3 yrs)
- Worked on around three products, all shut down, code probably lives in some SVN archive.
- Learnt advanced JS, PHP, MySQL, Photoshop, jQuery etc (skills mostly relevant)
# Job 2 (1.6 years)
- Project never launched, code never saw the light of the day. Probably lives in some Git archive.
- Learnt a few in-house frameworks (irrelevant) but also leant Git (relevant)
# Job 3 (8.5 years)
- Worked on several products, the biggest one is still active and seeing millions of users weekly. Rest got shut down and live in a Git repo.
- Learnt about some inhouse frameworks (irrelevant). React, React Native (skills still relevant)
# Job 4 (2 years)
- Actively working
- Learnt Vue (skills still relevant)
So much fun! It'll be nicer to highlight the paths which are "available" given the criteria. It could be only enabled when you start dragging an entity