pashields

That doesn't mean that idiomatic practices are always virtuous, but non-idiomatic code is only virtuous because it overcomes an inherent mismatch between what the user wants and what the language provides. With many languages (certainly js, java, c++) we see non-idiomatic practices guide changes to the language and then be replaced. Java gained functions to avoid the abuse of anonymous inner classes. ES6 is stealing from transpiled javascript languages left and right.

Making idiomatic code virtuous is the goal of creators and maintainers. Writing idiomatic code means that you have chosen languages, frameworks, and libraries that are closely aligned with the code you need to write and the style you want to write it in.

Comment · 13 years ago

see Aphyr's comments here: https://groups.google.com/d/msg/redis-db/Oazt2k7Lzz4/q9YDD7D...

Comment · 13 years ago

Just to be clear, the criticism is of Redis Cluster, which has been redesigned because the first design was so lax it was effectively unusable. The real issue, is that as of right now I have no idea what the exact semantics and failure conditions of Redis cluster are. I'm not clear that anyone really knows. Salvatore thinks he knows, but we can't be sure that he does.

With all this talk of practicality, what really makes distributed systems practical is when someone can do a formal analysis of them and conclude what possible states can occur in the system. This is not work that database users should do, it is work that database implementors should do. The failure to use a known consensus system is a failure to deliver a database I can understand.

I find this all a bit disappointing since I've been a huge fan of Redis since the early days. It's an amazing tool that I still have in production, but I get the feeling that it's utility will never expand to suit some of my larger needs. Bummer.

Comment · 13 years ago

They handle automatic failover, which redis does not currently do out of the box. That part is pretty cool. Maybe not worth the price, but definitely useful.

Comment · 13 years ago

Adzerk - Durham, NC 12 person (and growing fast) ad platform. Real customers (Reddit, Stack Overflow, and more), real revenue.

We have open positions in sales, devops, and developer roles. More info on the positions here: http://www.adzerk.com/job-openings/

Comment · 13 years ago

Adzerk - Durham, NC - Full-time, permanent - (http://www.adzerk.com)

We're looking for a devops engineer and both junior and senior developers. More info on our jobs page (http://www.adzerk.com/job-openings/)

Adzerk is focused on helping publishers make more money from their ad inventory by building a revolutionary ad serving platform. We believe that making advertising a viable business model for publishers ensures the future of a free and healthy internet. We love nothing more than helping a great publisher be rewarded for their hard work and help them continue to create awesome content.

Comment · 13 years ago

Adzerk - http://www.adzerk.com/job-openings/ - Durham, NC

We're looking for software engineers, both senior and junior. Our needs are all over the place, from UI to data warehousing, so there is a lot of skills you can bring to the table and many areas to play around in. We've got 10 people on the team right now and we are planning to grow!

Adzerk is a Durham, NC startup that’s helping content publishers make more money from their ad inventory by building a revolutionary ad serving platform. We serve ads for reddit, stackoverflow, and other sites you've probably heard of.