Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

The End of the Redis Adventure

antirez.com

Post reply on HN
Print view View original

251–260 of 308 posts

Re: The End of the Redis Adventure

#251

Post by bigiain »

antirez wrote: post #78

Ok, so many thank you here, thanks! It's very nice to read the comments here. But I hope to interact more on HN, since basically the idea is to write more blog posts, write more OSS software too. Just totally random :D I'll just do whatever every morning I want to do for a long time. Then maybe I'll find a new long term interest.

Hey man, like a lot of people here, I wanna say "Thanks fort Redis, it's solved a bunch for problems for me at work", but also "Thanks for dump1090, I've had heaps of fun with that, and learned a lot from digging into your code there."

Best wishes for whatever it is you choose to do next.

Re: The End of the Redis Adventure

#253

Post by angott »

blfr wrote: post #224

My co-founder and I had successfully launched two of the major web 2.0 services of the Italian web. What are these services?

One of them was LLOOGG: https://github.com/antirez/lloogg, which used to be at lloogg.com but it seems like the domain was not renewed.

I remember using it on my personal website long before I had even heard of Redis, it was a nice analytics tool for small sites with little traffic.

Re: The End of the Redis Adventure

#254

Post by bigiain »

fidelramos wrote: post #51
m0xte wrote: post #42

Earlier quoted context omitted.

This is underground programming. Perhaps it's 1?

I'd make it -1, that way regular programmers wouldn't know about it.

"Should array indices start at 0 or 1? My compromise of 0.5 was rejected without, I thought, proper consideration." — Stan Kelly-Bootle.

Re: The End of the Redis Adventure

#255

Post by tgtweak »

ahmetkun wrote: post #96
antirez wrote: post #74

Earlier quoted context omitted.

Actually the web site uses Redis as the only store. And Redis is using 0.1% of CPU. The problem is that Ruby sucks at doing anything scalable. It's just a Ruby/Sinatra app. If you do that in PHP, it will work out of the box with many concurrent accesses. With Ruby not the case. There are ways to deploy it better, but it should be fast as default, which is not the case.

I guess it would be interesting if you re-wrote your website in PHP and wrote a blog post about it with the title 'Why I Moved From Ruby to PHP?'

Or just build a proper Ruby implementation

Re: The End of the Redis Adventure

#256

Post by tedk-42 »

justaguyhere wrote: post #5

I would rather be remembered as a bad artist than a good programmer Takes a rare person to say this, made me smile :)

When I read that line my heart broke a little.

I think he's done a great job with Redis. It goes to show sometimes that you need to let go of the thing you created for the good of the community. If I were in his position, I would have made the same move

Re: The End of the Redis Adventure

#258

Post by zebraflask »

eric_b wrote: post #50

So they're moving to a new "community based", "light governance" model. [1] There are plenty of problems with BDFL-style projects, but I think there are a lot of advantages too. Redis is unique in my experience in that it works the way you'd expect - it doesn't cause outages, it is fast, and it has a vanishingly small number of gotchas. The feature set is well curated and for the most part fits together cohesively. T…

Do you have any tips for explaining to stakeholders that things in a Redis cache expire on async schedules?

Re: The End of the Redis Adventure

#259

Post by jart »

dexen wrote: post #59
dilandau wrote: post #10

Earlier quoted context omitted.

Probably the roving mobs on Twitter who occasionally brigade project issue trackers and mailing lists. Check out the master/slave post he wrote a while back. Or just the toxic nature of some open source communities, especially on Reddīt for whatever reason.

This. The underground in underground programming refers to maintaining low visibility, as to present low target silhouette. Additional benefit is not attracting too many participants that are in it for the clout, rather than for solving problems & good engineering. Open Source is no longer sufficient for software freedom; the current 'battlefield' is maintaining security from activist pressure or gradual take-over.

I created the Occupy Wall Street website nine years ago. Believe me when I say the lengths people will go, to try and control community projects, is downright traumatizing. I never could have imagined that same kind of nastiness would impact open source.

If you don't feel comfortable engaging with the new toxic culture, you can use my underground liferaft. My liferaft isn't an operating system, but rather an attempt to help us not depend on them as much. I have no idea who's controlling GNU/Linux these days and Occupy was enough drama for one lifetime. My code has the same focus on clarity that Antirez put into his Redis codebase. My liferaft also empowers you to build and distribute tiny native portable programs (like Kilo!) using hermetically sealed tools. See https://github.com/jart/cosmopolitan

Re: The End of the Redis Adventure

#260

Post by reitzensteinm »

mrkurt wrote: post #163
calpaterson wrote: post #86

Earlier quoted context omitted.

> The most important thing Antirez did, in my opinion, was to say "No" to things. No to new features that didn't make sense. Redis has had tremendous mission creep over the years. It started of course mostly as a volatile cache but I've now seen it also used as a message bus (in three different ways: BLPOP, PUB/SUB and Streams), for service discovery and as a general purpose database - something that Redis Labs (in m…

It didn't really start as a volatile cache, it started as an in memory data structures server. It's useful for all kinds of stuff memcached isn't (and has been since day 1).

Yeah. I do think that Redis has suffered from some mission creep, including a deprecated misadventure in to a mode where values could be stored on disk and only temporarily cached in memory.

Maybe that's what Cal and his colleagues were using it for at the time, but the claim that it started as a volatile cache is just not true. Interesting datastructures and the fork based persistence model were there from the start.

Post reply on HN