For the forges, what the sibling said.

However, what I see cooking at Cursor is way more promising than the others. Things like full system understanding, their own forge, multi-repo support. I'd put them as way more visionary in the Gartner magic Quadrant ;)

We currently use rocksdb with storage on the same node, and hit rocksdb 1000s of times per second during our analysis. About 20% writes, 80% reads. The issue is that we need to start scaling horizontally, for burstable workers and zero-downtime deployment. So we're thinking to offload to an external kv service instead of a local rocksdb.

TiKV seems a good replacement, about 3-4x slower, but very scalable. Reading this article, I think a separate postgres cluster with unlogged tables might be a good idea. If anyone has some experience to share, let me know!

Comments URL: https://news.ycombinator.com/item?id=49318634

Points: 1

# Comments: 0

When reasoning about a bit of code, types and effects are two things that help me grok it. However, there are a lot more. Like: how much memory can this use, does it process any PII, how quickly should it respond, which users are allowed to run it. Our "type" system could then alert us when we call a function that takes 20 seconds straight from a button without a loading spinner.

I'm very curious to see whether a language with many annotations this could work. Probably a language stored in a database approach like Unison is needed.

Other than that, I'm also curious to know if Jacquard works well with LLMs in practice. How well does providing the language docs into the prompt actually work? The models are trained on mainstream languages so I've been doubtful whether new languages will be able to compete.

We're running a fork that supports a "sidecar" server for running multiple integration tests against. So if any tests that need the server are included, it spawns the server, runs the integration tests, and then shuts it down. By re-using the same server we speed up our runs tremendously.

Discussion thread on gh: https://github.com/nextest-rs/nextest/discussions/3330

Good luck coming up with a new language and getting enough content out there that LLMs will be fluent with it.

If true, I think that's a shame. There's plenty of innovation still to be done.

At first the delay was 30 minutes. Then 2 hours. After 1h30 with zero updates we decided to bail. Just checked and nothing is moving yet, so we made the right call.