sbt VS bloop

NOTE: I won’t mention SBT and Leiningen here because, with all due respect, they are niche build tools. I also won’t discuss Kobalt for the same reason (besides, it’s no longer actively maintained). Additionally, I won’t touch upon Bazel and Buck in this context, mainly because I’m not very familiar with them. If you have insights or comments about these tools, please feel free to share them in the comments 👇

Sbt has the primitives that would allow that, but this would change the semantics of the test task. See also testQuick and https://github.com/sbt/sbt/issues/6292

If I use IntelliJ then apparently sbtn is not supported and they don't bother with Scala-CLI or Coursier.

Version 1.3.13 has a size of 1.17 MB in zip

See scala-xml 2.x mega tracker on plugin ecosystem conflicts.

This is under discussion at https://github.com/sbt/sbt/issues/6997

See https://github.com/playframework/playframework/issues/10572 and https://github.com/sbt/sbt/issues/6235 for more details and context.

BTW, if you're curious, it appears OP is using this: https://github.com/sbt/sbt/releases/tag/v1.6.2 Pretty sure one of the executables is doing ANSI colours.

If you see the progression of documentation changes over the years pushing people towards multi-project style, and issues like https://github.com/sbt/sbt/issues/6217, hopefully you'd see that I've really tried to encourage people to use multi-project style from the get go.

Fyi in case anyone is curious, sbt is fully removing log4j going forward: https://github.com/sbt/sbt/pull/6726

https://github.com/BloopAI/bloop Is fully open source and has full text + regex search built on tantivy fyi

Thanks! Bloop really helped with the documentation! they index your code base and uses RAG locally to talk against it. It works shockingly well.

In this blog post, I’ll be comparing 3 distinct AI-first code search tools I recently came across: Cody (developed by late-stage startup, Sourcegraph), SeaGOAT (an open-source project that was trending on HN last week), and Bloop (an early-stage YC startup). I’ll be evaluating them along the dimensions of user-friendliness as well as their accuracy.

If you're confused about any of the code snippets above, you can check out bloop.ai and phind.com (along with its VSCode extension) to answer any of your questions about the repository, noting that both have free plans.

COMPANY: bloop (https://bloop.ai)

bloop (YC S21) | Rust AI Engineer | Onsite | London, UK

We're a YC + tier-1 VC backed startup, working on a AI chat assistant for software developers that can answer questions about any large codebase.

About you: you hack around with GPT on the weekend, maybe you even fine-tune some of these new open source models. But you're also a solid programmer, capable of not just prototyping a nice demo but also shipping performant code that can scale. You're probably quite good at what you do, maybe you were top of your class, or maybe you rose the ranks to your comfortable management role, but yearn for the days of writing code, redbull and deploying on a Friday.

We're a small team, looking for one individual to join us in London, in-person at least 3 days per week.

Please reach out to me at join [at] bloop [dot] ai with "HN AI Engineer" in the subject line and a note about why this is exciting and a link to your portfolio or linkedin/resume.

P.S. Our stack is Rust, so it's likely the role will go to a candidate with Rust experience but if you think you have something to offer that compensates for lack of Rust we should chat anyway!

https://github.com/BloopAI/bloop

Bro let me turn your life inside out: https://bloop.ai

Another example is Bloop, it is a code search engine built on top of tantivy and qdrant.

Bloop is a developer assistant that uses GPT-4 to answer questions about your codebase (https://github.com/BloopAI/bloop)