jina VS Gource

Jina mainly because of their use of neural networks and AI.

Jina - It’s an open-source project where you can build search engines. Well maybe not no code but it claims that you only need a few lines of code for creating projects. The project supports semantic, text, image, audio, and video search. What I’m also interested in is with their neural search and generative AI. I’m also interested in the amount of github repo that they have. I have this on my radar since this is also something I was interested in.

Do you guys have any ideas how we can match images on our database? We’re working on a project that about matching images on our database. We were trying to use SIFT and some other similar methods, but for some reason, nothing doesn’t seem to be working that well. Does anyone have any suggestions for the most effective way to do this? Maybe some open-source solutions like HuggingFace or Jina AI? We just want to make sure our image matching is correct and that part’s been a bit of a struggle on our part.

The tech lets you find 3D models without sifting through tons of text - An information retrieval framework does the heavy lifting and compares models to each other, no descriptions or keywords needed.

Jina AI -They offer a neural search solution that can help build smarter, more efficient search engines. They also have a list of cool github repos that you can check out. Similar to Vertex AI, they have image classification tools, NLPs, fine tuners etc.

Well, it's not exactly a new feature, but we've been working on early support for DocArray v2 in Jina.

Jina let’s you serve all of your models through the same Gateway while deploying them as individual microservices. You can also tie your models together in a pipeline if needed. Also some nice ML focussed features such as dynamic batching.

The underlying technology, https://gource.io/, has probably been mentioned here before, but it's a superb tool which produces beautiful animations, so deserves another airing.

This is really cool. And as OP pointed out, I really like the pipeline integration. Like when linting catches function-level complexity, but in a cross functional way. I prefer to think of programs in layers where the top layers can import lower layers, but never the other way (and also very cautious on horizontal imports). Something like this would help track that.

From the visualization perspective, it reminds me a lot of Gource. Gource is a cool visualization showing contributions to a repo. You see individual contributors buzzing around updating files on per-commit and per-merge.

https://github.com/acaudwell/Gource

Nešto kao gource?

Yeah, I was completely distracted trying to figure out what `import { Button, icons } from "ui"` was derived from. Looks like `

That being said, I do like the overall idea of animating code changes. Calls back to that old Facebook sketching app[0] that would let us share replays, and I am a fan of the stories that Gource[1] can tell.

Ultimately, though, the sequential text file is a bad metaphor for code. Best thing for it is to split your modules across files.

0. Can't remember the name of it, but something similar is https://sketchtoy.com/

1. https://gource.io/

If the goal is to create a fun animation, then have a look at https://gource.io/ for inspiration.

From https://github.com/acaudwell/Gource

I wonder what your history would look like in Gource: https://gource.io/