Login

Recent searches

No recent searches

Search options

Not available on writing.exchange.
writing.exchange is one of the many independent Mastodon servers you can use to participate in the fediverse.
A small, intentional community for poets, authors, and every kind of writer.

Administered by:

Server stats:

323
active users

writing.exchange: AboutProfiles directoryPrivacy policy

Mastodon: AboutGet the appKeyboard shortcutsView source codev4.3.7

#Redis

2 posts2 participants0 posts today
Public *
Fabio Manganiello

#Arch is replacing #Redis with #Valkey.

The transition period will be of 14 days, at the end of which the Redis package will be moved to the AUR.

I said it already one year ago after Redis switched its license to a very restrictive SSPLv1: I don’t get it. And I said that little, if anything, would have changed, and that the Redis community would have just been splintered into a bunch of forks, while the great offenders (AWS and Azure in the first line) would have just switched their cloud offerings to the more permissive forks, still without feeling any duty to contribute back.

Fast forward one year, that’s exactly what happened.

AWS is already offering Valkey as a drop-in replacement for Redis in ElastiCache. Most of the distros have already switched to Valkey, or are considering to do so. The only loser so far has been Redis itself, which has lost community support, users, developers and funding.

Lesson learned: if you build a FOSS project, and you’re pissed by Amazon and Microsoft monetizing it without contributing back, opting for a strict open-source (but NOT free) license that forces any users of your product to also release the full source code of what they’ve built with your product (not only any modifications they’ve made to your product itself) is a bad idea.

I mean, I would love to live in a world where such a strategy actually helps, where the “free-as-in-beer” folks can be sensibilized about the cost of their freeloading and where you can nudge them to be less evil with a license that forces them to build more in the open. But the truth is that this world is quite far from that vision. If the cost of forking is perceived as lower than the cost of contributing back, then you can assume that folks will just fork whatever was there at the time of the license change.

https://archlinux.org/news/valkey-to-replace-redis-in-the-extra-repository/

archlinux.orgArch Linux - News: Valkey to replace Redis in the [extra] Repository
Public
Wolf

I think any large interesting program you might write could well have an embedded language within it, in which the user can write stuff that is just as good, and just as deep as built-in functionality. You want this. It’s a thing that makes programs compelling.

In #Vim, that embedded language is #VimScript. In #emacs, that’s #elisp (which in fact, I think the whole thing is written in). In a #smalltalk environment, you control the entire environment with Smalltalk, just as elisp applies to Emacs. For many, many things, that language is #lua ( #NeoVim, many games, #pandoc, #redis, this list goes on).

I used to think there were really two reasonable mainstream languages you could use here: #Python or #javascript. Between those two, for a long time I felt that JavaScript was the winner. I think that has changed as Python has gotten faster, more powerful, and better known. But also, I think the answer might actually not be either of these two. It might be Lua. Lua is simpler and faster than either JavaScript or Python. It’s more embeddable. It’s designed specifically for this purpose. It’s in much wider use as an embedded scripting language. I don’t want Lua to be the answer. I like Python better. But I think Lua actually is the right answer.

Public
Benjamin Carr, Ph.D. 👨🏻‍💻🧬

What Happens to Relicensed #OpenSource Projects and Their Forks?
Contributor impact varies after projects adopt more restrictive licenses, finds Community Health Analytics in Open Source Software (CHAOSS) research on #Elasticsearch, #Redis, #Terraform and their forks.
So "Looking at all of these projects together, we see that the forks from relicensed projects tend to have more organizational diversity than the original projects," they conclude.
thenewstack.io/what-happens-to

The New Stack · What Happens to Relicensed Open Source Projects and Their Forks?Contributor impact varies after projects adopt more restrictive licenses, finds CHAOSS research on Elasticsearch, Redis, Terraform and their forks.
Continued thread
Public
Codeberg.org

We were still struggling with email delivery from Forgejo. It looks like some queues are corrupted and restoring them is very hard. Most queued messages are spam or registration emails with already expired tokens. Finally, we made the decision to reset the queue and will do that in a few minutes.

We are using the opportunity to switch the queues to #redict / #redis, which was a planned project anyway (a requirement for clustering our Forgejo to multiple instances).

ExploreLive feeds
About