> We're pleased to announce the release of Inko 0.19.1. This release includes support for HTTP servers and clients, pattern matching for let expressions, better code generation, many fixes and performance improvements, and more!
> If you're new to Inko: Inko is a programming language for building concurrent software, but without the usual headaches such as data race conditions and non-deterministic garbage collectors. Inko features deterministic automatic memory management, compiles to machine code using LLVM, supports different platforms (Linux, macOS and FreeBSD, and potentially any other Unix based platform), and is easy to get started with.
Argc is a powerful Bash framework that simplifies building full-featured CLIs. It lets you define your CLI through comments, focusing on your core logic without dealing with argument parsing, usage text, error messages, and other boilerplate code.
godo creates copy-on-write worktrees so you can run tests, generators or one-off tools in isolation. Each sandbox is disposable, disk-cheap and mapped to its own branch, letting you merge the results whenever you are ready.
Agency scientists found that PFNA could cause developmental, liver and reproductive harms. Their final report was ready in mid-April, according to an internal document reviewed by ProPublica, but the Trump administration has yet to release it.
1. Pricing would be $20 per person and we'd spin up an analysis for every PR you create/are assigned to review
2. We don't train or retain anything related to your codebase. We do send all the diffs to Open AI and/or Anthropic (and we have agentic grepping so it can see other parts of the codebase as well)
3. Do you mean the ability to run this on your own servers (or even on your own computer with local LLMs)? We do have plans for the former, but I don't know how big the lift on the latter will be so I'm not sure!
> We don't train or retain anything related to your codebase.
It would be good to have this mentioned on the website somewhere, as part of a privacy policy. Right now I can't find any details on the site, which is preventing me from trying this out with a production repository.
The delivery guarantees section alone doesn’t make me trust it. You can do at least once or at most once with kafka. Exactly once is mostly a lie, it depends on the downstream system: unless going back to the same system, the best you can do is at least once with idempotancy
> If you're new to Inko: Inko is a programming language for building concurrent software, but without the usual headaches such as data race conditions and non-deterministic garbage collectors. Inko features deterministic automatic memory management, compiles to machine code using LLVM, supports different platforms (Linux, macOS and FreeBSD, and potentially any other Unix based platform), and is easy to get started with.
reply