https://antirez.com/rss

Amodei in his latest blog post wrote a mix of agreeable things and things that I believe misrepresent where the real risk of AI is located.

(This blog post was adapted from the transcription obtained from my YouTube video at https://www.youtube.com/watch?

Even if you are as averse to semver as I used to be in the course of my programming activity, you can still think of open source software distribution as something that used to follow a fixed number of steps.

Look at the past history of this blog.

Automatic programming dramatically speeds up writing software in certain use cases and in the right hands.

High end NVIDIA cards, and the server and power needed to run them, cost a lot of money, especially if you plan to reach enough VRAM to run massive models.

EDIT: of course this was already done in the past!

I didn’t expect DwarfStar 4 (https://github.com/antirez/ds4) to become so popular so fast.

I started working on the new Array data type for Redis in the first days of January.

The proof of work is the wrong analogy: finding hash collisions, while exponentially harder with N, is guaranteed to find, with enough work, some S so that H(S) satisfies N, so an asymmetry of resources used will see the side with more "work ability" even…

Those who cannot remember the past are condemned to repeat it.

Here LLM and coding agents can find: 1.

Anthropic recently released a blog post with the description of an experiment in which the last version of Opus, the 4.6, was instructed to write a C compiler in Rust, in a “clean room” setup.

In my YouTube channel, for some time now I started to refer to the process of writing software using AI assistance (soon to become just "the process of writing software", I believe) with the term "Automatic Programming".

I love writing software, line by line.

* For years, despite functional evidence and scientific hints accumulating, certain AI researchers continued to claim LLMs were stochastic parrots: probabilistic machines that would: 1.

I’m taking a few weeks of pause on my HNSWs developments (now working on some other data structure, news soon).

Regardless of their flaws, AI systems continue to impress with their ability to replicate certain human skills.

Frontier LLMs such as Gemini 2.5 PRO, with their vast understanding of many topics and their ability to grasp thousands of lines of code in a few seconds, are able to extend and amplify the programmer capabilities.

This is a short story of how humans are still so much more capable of LLMs.

Yesterday, it was a very intense day.

Five months ago, I rejoined Redis and quickly started to talk with my colleagues about a possible switch to the AGPL license, only to discover that there was already an ongoing discussion, a very old one, too.

About three years ago I saw a quite curious and interesting post on Hacker News.

Yesterday we finally merged vector sets into Redis, here you can find the README that explains in detail what you get: https://github.com/redis/redis/blob/unstable/modules/vector-sets/README.md The goal of the new data structure is, in short, to create a…

I used AI with success 5 minutes ago.

By multiple accounts, the web is losing pieces: every year a fraction of old web pages disappear, lost forever.

It’s not new, but it’s accelerating.

We are destroying software by no longer taking complexity into account when adding features or optimizing some dimension.

I’m not the kind of person that develops a strong attachment to their own work.

The Raspberry Pico is suddenly becoming my preferred chip for embedded development.

From a theoretical standpoint, the best reply provided by an LLM is obtained by always picking the token associated with the highest probability.

My usual process for writing blog posts is more or less in two steps: 1.

I'll start by saying that this article is not meant to be a retrospective on LLMs.

The Idle scan was conceived at the end of 1998, evidenced by emails.

A few days ago, on Twitter (oh, dear Twitter: whatever happens I’ll be there as long as possible – if you care about people that put a lot of energy in creating it, think twice before leaving the platform).

(English translation of this post: http://antirez.com/news/136) Dopo due anni di lavoro, finalmente, Wohpe, il mio primo libro di fantascienza, ma anche il mio primo scritto di prosa di questa lunghezza, è uscito nelle librerie fisiche italiane, su Amazon,

(Traduzione italiana di questo post: http://antirez.com/news/137) [Sorry for the form of this post.

One year ago I paused my programming life and started writing a novel, with the illusion that my new activity was deeply different than the previous one.

A new idea is insinuating in social networks and programming communities.

When I started the Redis project more than ten years ago I was in one of the most exciting moments of my career.

Finally Redis 6.0.0 stable is out.

So it happened again, a new Redis version reached the release candidate status, and in a few months it will hit the shelves of most supermarkets.

[Note: this post no longer describes the client side implementation in the final implementation of Redis 6, that changed significantly, see https://redis.io/topics/client-side-caching] The New York Redis day was over, I get up at the hotel at 5:30, still…

Months ago the maintainer of an OSS project in the sphere of system software, with quite a big and active community, wrote me an email saying that he struggles to continue maintaining his project after so many years, because of how much psychologically ta…

The new Redis data structure introduced in Redis 5 under the name of “Streams” generated quite some interest in the community.

Ten years ago Redis was announced on Hacker News, and I use this as virtual birthdate for the project, simply because it is more important when it was announced to the public than the actual date of the project first line of code (think at it conception VS

Yesterday a concerned Redis user wrote the following on Hacker News: — https://news.ycombinator.com/item?

[EDIT!

For quite some time I’ve wanted to record a new video talking about code comments for my "writing system software" series on YouTube.

The last few days have been quite intense.