I get that people here have reasons to hate on Ollama but it has two genuinely strong points:
- it makes it very easy to use open models with a lot of harnesses and assistants via `ollama launch`;
Their $20 subscription is very generous, and they claim not to log or train on your data.
I will be curious to see if their subscription ever supports the ~3T open weights models announced this week.
Nicely done! Would you consider adding an Agent SDK login for Claude for those who don't have an API budget and want to avoid potential issues with Anthropic's capricious policies around CLI use in third-party apps?
Lovely name! I implemented profanity monitoring in my Hermes setup to identify "learning opportunities" for my agents. It is quite useful. If you are budget-conscious, one challenge is determining what is the smallest number of previous rounds that Hermes needs to correctly infer what it did wrong. Curiously, Claude Code is horrible at figuring out what it did wrong. I often read its memories, and they are rarely useful.
$300 is my employer's monthly cap on Claude Enterprise. It lasts me at most a week of moderate use. I would much rather get Codex Pro and Claude Pro or Max, which would cost ≤ $200. For $300, one could also add Gemini Ultra to the mix so I could have all three review each other's code, etc.
Claude can be very good but enterprise pricing doesn't make sense to me.
Very useful website. Would you have insight into what models are best at editing existing images?
I often have to make very specific edits while keeping the rest of the image intact and haven't yet found a good model. These are typically abstract images for experiments.
I asked gpt-image-2 to recolor specific scales of your Seedream 4 snake and change the shape of others. It did very poorly.
There has been promising work on olfactory training, which you can do very inexpensively at home. If you can, I would consider seeing any ENT first to rule out polyps, etc.
Maybe at the bottom your marbles could land on surfaces with different accustic properties. Track selection would determine the surface and release time would determine the timing.
I live in a big city. DoorDash always delivers to an address 10 minutes away walking from my building. It is quite inconvenient in the winter. With human drivers, you can at least try to convince them to use Google Maps, but with an AI?
On second thought, prompt injection via delivery instructions?
What I don't quite get is why manufacturers of midi controllers (Arturia, Novation, NI, etc.), with the exception of, possibly only Korg, don't release any of their digital instruments as mobile apps. After sitting the whole day in front of my computer, the last thing I want to do is to swap VS Code for Ableton or Kontakt and spend a few more hours in the glow of my monitors.
(I do get that if you are very serious about making music you need a proper computer set up. I am just a mere amateur hobbyist.)
The m8 and the recently, heavily promoted Woovebox 2 are the Emacs/Vim of grooveboxes. They hide a vast amount of functionality behind what initially seems like an impenetrable jungle of button presses and shortcuts; a system that ultimately proves* to be highly ergonomic.
*Based on what I read. Sadly, I don't own these devices.
If you have to use, e.g., CUDA Toolkit 11.8, then you need a specific version of VS and its build tools for CUDA's VS integration to work. I don't know why exactly that is and I wish I didn't have to deal with it.
> Why is it so hard to install PyTorch, or CUDA, or libraries like FlashAttention or DeepSpeed that build against PyTorch and CUDA?
This is so true! On Windows (and WSL) it is also exacerbated by some packages requiring the use of compilers bundled with outdated Visual Studio versions, some of which are only available by manually crafting download paths. I can't wait for a better dev experience.
GitHub of the person who prepared the data. I am curious how much compute was needed for NY. I would love to do it for my metro but I suspect it is way beyond my budget.
(The commenters below are right. It is the Maps API, not compute, that I should worry about. Using the free tier, it would have taken the author years to download all tiles. I wish I had their budget!)