> Plan how to refactor the codebase to use the new JobDefinition.create function introduced in git commit . Split task into subtasks, if needed. Write the plan to todo.md.

...

> Start working on the task in @todo.md. Write code that follows the "Keep it simple, stupid!" principle.

You can get pretty good results by copying the output from Firefox's Reader View into your project, for example: about:reader?url=https://learnxinyminutes.com/ocaml/

I'm building a minimal, cross-browser, and cross-platform UI for Ollama.

Stack: HTML, CSS, JavaScript, in other words, no dependency on React, Bootstrap, etc. Deployment: web server, browser extension, desktop, mobile

You can easily experiment with smaller models, for example, Mistral 7B or Phi-2 on M1/M2/M3 processors. With more memory, you can run larger models, and better memory bandwidth (M2 Ultra vs. M2 base model) means improved performance (tokens/second).

Try to, for example, set 'num_gpu' to 99 and 'use_mlock' to true.

The biggest problem with HTML/CSS apps is that their look and feel are different from native GUIs. This is less of a problem for chat and document-based applications (Slack, Word, etc.), IMO. With Tauri, I can also customize the window and integrate native features to mitigate this. I'm not sure WebUI can do this.

Here's what I have found so far:

- JavaScript (vanilla) is a viable alternative to React.js

- HTML entities (UTF-8) are an alternative to, for example, font-awesome

- Parcel.js is great for bundling cross-browser compatible Javascript apps: simple to install and no configuration needed. By default Parcel.js supports every browser having 0.25% or more of the total amount of active web users.

- The HTML template tag and JavaScript work well as a replacement for template libraries like Pug

- ChatGPT4 is great at writing the skeleton code for a project

Future plans include experimenting with `node:test` for testing.

I would need to add external libraries to fully support the following features, but I think I will continue on the zero-dependencies path:

- Sanitizing HTML

- Code highlighting

- Markdown rendering

The code can be found here: https://github.com/christianhellsten/ollama-html-ui/

http://www.frmocorp.com/indexation.html

In principle, the theory behind indexation is very much like the theory of perfect competition. In perfect competition, the idea is that no participant is sufficiently powerful or sufficiently large to influence the price of the product. The product is assumed to be homogeneous, and shares are designed to be homogeneous. In the theory of market efficiency, no one has an information advantage over anyone else, and there is always enough liquidity. It seems reasonable to make those assumptions. Yet, it is worth making some observations about them.

Frameworks with the most features and the best (loudest?) marketing are usually the most popular (e.g. Rails and jQuery), but they might not the best tools for the job.

2. Wait for half the internet to write about it (with new links to digg.com)

3. Put back the old Digg content

4. Wait for half the internet to write about it (with new links to digg.com)

5. Nasdaq Listing/Internet domination???

This strategy should work for all social-media startups. No guarantee of profits though...