<antirez>

Github reviews as a way to improve code quality?

▼
antirez 5723 days ago.
Today I tweeted quite a bit about Ruby software quality. The trigger was simply a Ruby/Sinatra application I run for personal use that crashed from time to time due to a GC bug in the Ruby interpreter I was using (the default of a recent Ubuntu install, sadly).

This is an interpreter bug, and I hope it is a rare one, but this episode made me thinking about how many bad stories I accumulated since my preferred high level programming language is Ruby: bad documented gems, not working gems, dependencies hell, hard to install things, bad performances, and so forth.

Redis Manifesto

▼
antirez 5740 days ago.
Many times I don't know what to exactly reply to feature requests, or questions about why things in Redis are done in a specific way. Most of the time the questions make a lot of sense, there is not just a way to make things in programming, a lot is about your taste, feeling, and ideas about how software should be written. So I tried to condense my feelings about Redis and software development in general in this short manifest, that I'll include in the Redis distribution. There are an infinite number of ways of doing things, this is just the one I and a good part of the Redis community like.

Redis Presharding

▼
antirez 5744 days ago.
Redis cluster is currently under development, and we hope it will be able to solve the problem of partitioning data among different Redis instances in a transparent, fast, and fault tolerant way. The cluster project is currently not ready: even if we have a pretty clear design, and many networking level code for gossip and failure detection, it will take some more month to be released, and more time to be released into a stable release.

While our work continue, people shard regardless of Redis cluster, using their own algorithms and systems. This post describes a strategy for partitioning your data among N instances that is very simple but that works great. We'll call this strategy "Redis Presharding".

there is something between append only and reusing blocks

▼
antirez 5762 days ago.
One of the most interesting properties of an append only btree is that it's impossible to corrupt. There are other interesting properties as well like concurrent accesses are trivial, since whatever is the root and all the nodes your reader is going to access, they are all valid, just they may be an old representation of the btree.

But there is a price to pay that I'm not happy with, that is, the append only btree requires a compaction process, otherwise it will get bigger and bigger. If your use case is mostly-reads this may be ok, but if you plan to use a lot of writes there is some math to do.

Pull requests are not conversations

▼
antirez 5764 days ago.
I don't remember anything that changed my work flow in a so big way as git did in the latest two years. I will not argue too much about that, as you probably experimented the effects yourself if you are reading this blog post, or perhaps you are among the guys I should say thanks for the fact I started using git.

But if git is cool, Github makes it cooler for sure. Github is like a market for git, where code gets exchanged, shared, publicly hacked. In short I love git and github. Still I think that github pull requests are posing a problem in the open source development world, and this post is all about this.

About the new INFO command, Diskstore and Cluster ETA

▼
antirez 5776 days ago.
With this blog post I'll try to keep you posted on the progresses of Redis, the recent changes to the INFO output, and the ETA for diskstore and cluster.

New INFO output
During the week end I managed to improve the INFO output that was rapidly becoming a mess ;) INFO is a very interesting command for Redis users, but there are a few issues that need to be addressed:

• Too much output., not separated by section. This has many drawbacks: complex to read for humans. Time consuming to generate as it can take more than a millisecond sometime, for some Redis uses this is not ideal.

Diskstore and a new b-tree implementation

▼
antirez 5782 days ago.
A few weeks ago I presented a new development direction for Redis, called diskstore. The original announcement is in this Redis Group post.

Diskstore is working very well in our initial tests, and we are working to improve it. Diskstore is basically a smart caching layer on top of Redis backed by an on disk plain key value store. The current implementation of the disk store is file system based: every key is represented on disk by a single file. This setup is interesting in many ways as it is pretty hard to corrupt, and very transparent (you can see the individual files, rsync them into another server, and even joining two databases just merging all the files), but hardly the fastest.

Redis 2.2.0 RC1 is out

▼
antirez 5816 days ago.
Finally we are already at the end of another development cycle: the first release candidate of Redis 2.2.0 is out! You can grab it here from github, it is tagged as 2.2.0-rc1, or if you prefer, as a tar.gz file.

As I said some time ago, 2.2 is a monument to how much Redis 2.0 sucked. I think that looking back to the previous version and having the feeling of a very bad implementation is a good thing. It means we did another step improving our code.

What's wrong with 2006 programming?

▼
antirez 5887 days ago.
Redis 2.0 introduced a new feature called Virtual Memory. The idea is that some applications using Redis may not access the whole dataset with the same frequency. In extreme cases only a little percentage of hot spot data is used often, while the rest is mostly idle and touched very rarely. For instance imagine a Redis instance holding User objects: the most active users will hit this subset of records continuously, while a large percentage of users will access the site a few times a month, and another large subset of users completely forgot about this web service at all.

A few key problems in Redis persistence

▼
antirez 5890 days ago.
Today I read this article about Redis with interest. It's a legitimate point of view on databases, you may agree or not, but the author has a solid idea about what he is looking for and about the database scene. I don't agree with everything, but there is something I especially like about this article: it actually identifies very well what I think are actually the strength and deficiencies of Redis.

In short: the strength is the data model, and the deficiency is the persistence.

An update on the Memcached/Redis benchmark

▼
antirez 5899 days ago.
A few days ago I published a blog post that included a benchmark between Redis and memcached.

My results showed Redis to be considerably faster than memcached running a single instance of redis-benchmark (or the equivalent mc-benchmark) against an instance of Redis using a single core, and an instance of Memcached using four cores.

I was missing something in the test, Dormando published a counter benchmark where more than a single mc-benchmark was used against memcached, showing that only under this conditions memcached is able to saturate all the CPU cores, leading to much higher numbers.

On Redis, Memcached, Speed, Benchmarks and The Toilet

▼
antirez 5901 days ago.
The internet is full of things: trolls, awesome programming threads, p0rn, proofs of how cool and creative the human beings can be, and of course crappy benchmarks. In this blog post I want to focus my attention to the latter, and at the same time I'll try to show how good methodology to perform a benchmark is supposed to be, at least from my point of view.

Why speed matters?
In the Web Scale era everybody is much more obsessed with scalability than speed. That is, if I've something that is able to do handle a (not better defined) load of L, I want it to handle a load of L*N if I use N instances of this thing. Automagically, Fault tolerantly, Bullet proofly.

Auto Complete with Redis

▼
antirez 5909 days ago.
Hello! This isn't just a blog post, it is actually the Redis weekly update number eight, but we can't tell this to Google: naming posts like Redis Weekly update #... will not play well with Google indexing, so I'm starting to use blog post titles more predictive of what people will actually type into a search engine, in this specific case autocomplete redis, probably.

Too bad that I'm forced to play the game of the SE0 L00z3r, but it's for a good reason. I guess this will also work well when articles are submitted in places like Hacker News, Programming Reddit and so forth. Readers will have a simpler way to tell if they want to actually click or not on the link. Ok... end of the off topic.

Redis weekly update #7 - Full of keys

▼
antirez 5928 days ago.
I'm back after two weeks of vacation: the sea was wonderful, I refused to travel at all, it was time for the real relax, that is, doing as little as you can and enjoy your friends, family, and the summertime. I hope you had a good stop too... in the Redis IRC channel one day I read that in Europe we have guaranteed vacation days because of our weak european bodies :) but whatever is your continent don't miss the opportunity to stop a bit!

And what's cool about stopping is how nice it feels to start hacking again after a few days of not writing a single line of code, so you can see a number of commits already in the master branch of Redis, including fixes for old important bugs and other little improvements. I'm processing the open issues one after the other, and when I'll done, it will be time to release 2.0.0 as stable.

Redis weekly update #6 - 2.2 and VM

▼
antirez 5975 days ago.
Hello again and welcome to the Redis weekly update #6!

The latest weeks have been very busy and interesting, I and Pieter Noordhuis visited VMware and attended the SF Redis Meetup, as you can guess quite exciting experiences for both us :)

Redis 2.0 reached RC2 in the meantime and is going to be shipped as stable in a few weeks.

Simultaneously Redis 2.2 is almost complete from the point of view of features, with the biggest thing currently in the workings being replication fo DELs on expires in slaves and append only file so that it will be possible to perform write operations against expiring keys.

Redis weekly update #5 - RC1 is near

▼
antirez 6028 days ago.
Welcome back to the Redis Weekly update :) This one actually took one month instead of one week, but this is not bad news after all, as the reason for the delay is that I was busy working at Redis in order to speedup the release of 2.0.0 RC1.

RC1 is very near now, and we have a date: it will be released 21th May 2010. The work will continue after RC1, but will focus on testing (including providing a better test suite) and bug fixing.

This weekly update could be huge if I would report one month of work, so I'll picka few interesting stuff from the change log, trying to explain the details, instead of presenting a long list of things without any detail. I'll start from one that I think will make many users happy (for sure it made me happy), that is, loading and saving times.

fsync() on a different thread: apparently a useless trick

▼
antirez 6042 days ago.
fsync() is the kind of system call you love and hate at the same time. In many applications it's nice to know that kernel buffers are flushed to disk (even if this alone does not necessarily guarantees data is actually written to the disk, as the disk itself can have caching layers), but unfortunately fsync() tends to be monkey assess slow.

As I like numbers, slow is, for instance, 55 milliseconds against a small file with not so much writes, while the disk is idle. Slow means a few seconds when the disk is busy and there is some serious amount of data to flush.

Redis weekly update #4 - Fixes and Optimizations

▼
antirez 6062 days ago.
Welcome back to the Redis weekly update, we skipped one week as now that we are in feature freeze the news are a bit slower, even if... actually in this two weeks we managed to accumulate an interesting Changelog. While the development of new features stopped the 1th April, we are still not into a very static stage, and the following kind of changes are the new focus:
• API changes to provide a more coherent behavior. Redis 2.0 can break a few corner cases at least, being it a major release, and it's time to fix some old bug.

Redis weekly update #3 - Pub/Sub and more

▼
antirez 6076 days ago.
I was not able to write this post yesterday as I was just too busy delivering a new feature, just before the feature freeze that will start 1th April. So as you can guess, even if this violates the chronological order, this is going to be the first entry of the weekly update.

Redis is now a Publish/Subscribe server
This feature is a user-requested one. Actually it is the mix of two different requests:
• Many users wanted a notification mechanism to trap changes in the key space. Like waiting for a given key to be changed, deleted, and so forth. We already had BLPOP (blocking list-pop operation) but this is really not good enough for this task, for a number of reasons: usually you want to notify multiple clients at the same time, and usually you don't want to queue notifications, but just, who is listening will get it. Users resorted to all kind of tricks to get this effect, including the use of MONITOR as a stream of changes! But this was not the right solution as you can guess.

Redis weekly update #2 - Real world hashes, refactoring, and fixes

▼
antirez 6084 days ago.
Hello, welcome to the weekly update #2, this time it shifted to Monday as I used the whole Friday for debugging purposes as you'll read in a minute. So this is what happened in the last week, more or less in chronological order.

Real world hashes
Hashes were just a shy start the last week, now they are much better:
• More commands, now we have HSET,HGET,HDEL,HEXISTS,HKEYS,HVALS,HGETALLL,HLEN
• Tests for all the H-commands, resulting in...
• Many bugs fixed including a memory leak and other bugs in zipmap.c

VMware: the new Redis home

▼
antirez 6091 days ago.
Redis started as an internal project more or less one year ago. Initially it was not meant to become an open source project. The initial goal was just to make it simple for us to scale a few critical things in different web applications.

But it was hard to resist the open source soul there is in me :) It's been more than ten years that I have contributed to the open source world. Code sitting just inside your HD is a waste in many ways. So a few weeks later I released the first public version of Redis, and it started to grow in users, who in turn pushed me to add features and provide more stable code.

Redis weekly update #1 - Hashes and... many more!

▼
antirez 6094 days ago.
This is the first article of a serie called, with little imagination, Redis Weekly Updates. The idea is to provide some insight in the Redis development process: what's new in Redis master this week? What are the new directions? The people involved in the development process?

I'll try keeping this articles as informative as possible and, when it is possible, not too long, or at least split in paragraphs for easy scanning, so that this can become a weekly appointment for everybody following the Redis development. So... let's start!

IT Security e Computer Forensics a Catania

▼
antirez 6127 days ago.
Il mio amico Gianni Amato organizza un interessante corso di Sicurezza Informatica e Computer Forensics a Catania. Mi ha chiesto di spargere la voce e lo faccio con piacere, visto che sono certo che sarà una occasione interessante per chi è interessato all'argomento.

Potete avere maggiori informazioni sul corso visitando il  sito del corso.

Comunque sono 4 giornate con 4 diversi docenti al costo di 650 euro. Mi sembra un buon affare.

Redis Virtual Memory: the story and the code

▼
antirez 6131 days ago.
If you are reading this article probably you already know it: Redis is an in-memory DB. It's persistent, as it's disk backed, but disk is only used to persist, all the data is taken in the computer RAM.

I think the last few months showed that this was not a bad design decision. Redis proved to be very fast in real-world scenarios where there is to scale an unhealthy amount of writes, and it is supporting advanced features like Sorted Sets, and many other complex atomic operations, just because it is in memory, and single threaded. In other words, some of the features supported by Redis tend to be very complex to implement if there is to organize data on disk for fast access, and there are many concurrent threads accessing this data. The Redis design made this two problems a non issue, with the drawback of holding data in memory.

Pseudo Random Number Generator with power law (long tail-alike) distribution

▼
antirez 6145 days ago.
Today I needed a PRNG with a bised distribution, specifically following the Power Law distribution in order to simulate the "long tail" often seen in things like social networks data, search, and so forth.

I was not able to find ready to use code, but just a few formulas, so I wrote one in Ruby (I'm going to port this to C for Redis).

Maybe this will be useful to somebody else:

    # Power law (log tail) distribution
    # Copyright(C) 2010 Salvatore Sanfilippo

One year of Redis

▼
antirez 6170 days ago.
The first version of Redis was released to the public almost one year ago (10 months ago actually). This seems like a good time to look back at the development process.

Redis can't be considered a successful project yet, it's just too early, however the followings are a few concepts I learned in the last months that I feel like to share with you in the hope that I'll be able to apply this ideas in the future, and in the hope that programmers interested in creating a new open source project will find something interesting here and possibly avoid some mistake.

Linux: still better for coding

▼
antirez 6221 days ago.
Something like one year ago I switched from Linux to Mac OS X. It was not an easy switch if you think that my desktop on Linux used to be this one, that is, just fvmw2 with a minimal configuration, super fast virtual desktop, border-less windows.

Why I switched after more than 12 years of Linux? Actually I didn't decided to switch, just I got a macbook because I wanted to hack a bit with the iPhone SDK and with Mac OS X itself. I installed Linux and Mac OS X in multi boot, and for a few weeks the user interface of Mac OS X was impossible to use for me. But after a few more weeks I was using only Mac OS X for everything.

Why you should boycott Nokia

▼
antirez 6235 days ago.
Nokia just annunced an action against Apple:
Nokia announced that it has today filed a complaint against Apple with the Federal District Court in Delaware, alleging that Apple's iPhone infringes Nokia patents for GSM, UMTS and wireless LAN (WLAN) standards.
To me this sounds like: if you can't compete with the quality of the products you can try to sue to beat your competitor. This is not acceptable. Even more sad is that Nokia patents are more or less unavoidable, this is what I understand from the Nokia press release itself:

Questa antenna è pericolosa per la salute?

▼
antirez 6256 days ago.
English
Sorry if I ask here this strange question.

I could like to rent a little room in this building, in order to use it as office. It's cheap but it's not too bad inside. The problem is, this monster-antenna very near the building.

I'm not able at all to guess if this is going to hurt the health or not. What I think is a good sign is that the actual transmitters appear to be placed a lot higher than the building itself...

Somebody has a clue? The following is the picture. Thanks for any hint.

Hping wiki back online

▼
antirez 6257 days ago.
After a huge downtime, the Hping Wiki is back online, thanks to the emails of users pinging me about this issue. Finally I found two hours to restore its content, running under a very legacy code, a Tcl Wiki implementation I wrote myself many many years ago.

Sorry for the delay...

Originally published on oldblog.antirez.com on 30 September 2009.

Biancomangiare al pistacchio

▼
antirez 6257 days ago.
Il biancomangiare è un dolce Siciliano (e forse più in generale del sud Italia) fatto con ingredienti molto semplici. L'ingrediente di base è il latte. Si presenta come un budino denso di colore bianco, da cui il nome. La versione che vi propongo è particolarmente buona per via dell'uso del pistacchio fresco.

Ingredienti
La riuscita di ogni ricetta ha come condizione prima la qualità degli ingredienti, che devono essere ottimi e freschi.

• Un litro di latte fresco, intero, di alta qualità.

Libertà di interpretazione

▼
antirez 6260 days ago.
La recente discussione sulla libertà di stampa in Italia cela in realtà una libertà diversa, reclamata con forza dai potenti che possono permettersi di filtrare seriamente la già culturalmente poverissima TV italiana applicando un filtro che fa passare le voci che non disturbano il governo, e blocca tutto il resto.

Deve essere per forza così d'altra parte, altrimenti si delinea il quadro ancora più inquietante di un Berlusconi e suoi seguaci che non riescono, intellettivamente, a fare uno sforzo sufficiente per capire il significato universalmente riconosciuto di Libertà di Stampa.

Mailbox multiple, una perla di gmail labs

▼
antirez 6270 days ago.
Se siete utenti di gmail e il vostro rapporto con l'email è un combattimento all'ultimo sangue, giorno per giorno, come il mio, sto per dirvi qualcosa che potrebbe interessarvi moltissimo. Aprite le orecchie dunque, e ricordate che forse se usate gmail con l'interfaccia utente settata in italiano la cosa non funziona.

Infatti come molti di voi sanno già, cliccando sull'icona verde a forma di "pozione", sita in alto a destra, è possibile accedere a delle funzionalità più o meno avanzate (ci sono anche delle cazzate inutili mica da poco eh...).

Fenomenologia di Mike Bongiorno di Umberto Eco

▼
antirez 6278 days ago.
(scritta da Umberto Eco nel 1961)

L'uomo circuito dai mass media è in fondo, fra tutti i suoi simili, il più rispettato: non gli si chiede mai di diventare che ciò che egli è già. In altre parole gli vengono provocati desideri studiati sulla falsariga delle sue tendenze. Tuttavia, poiché uno dei compensi narcotici a cui ha diritto è l'evasione nel sogno, gli vengono presentati di solito degli ideali tra lui e i quali si possa stabilire una tensione. Per togliergli ogni responsabilità si provvede però a far sì che questi ideali siano di fatto irraggiungibili, in modo che la tensione si risolva in una proiezione e non in una serie di operazioni effettive volte a modificare lo stato delle cose. Insomma, gli si chiede di diventare un uomo con il frigo­rifero e un televisore da 21 pollici, e cioè gli si chiede di rimanere com'è aggiungendo agli oggetti che possiede un frigorifero e un televisore; in compenso gli si propone come ideale Kirk Douglas o Superman. L'ideale del consumatore di mass media è un superuomo che egli non pretenderà mai di diventare, ma che si diletta a impersonare fantasti­camente, come si indossa per alcuni minuti davanti a uno specchio un abito altrui, senza neppur pensare di posseder-lo un giorno.

There is not just a single Apple

▼
antirez 6318 days ago.
Obviously thanks to the recent moves of Apple a lot of guys are Qutting the iPhone. This may appear sensationalism, but I think that every time an hardware vendor is trying to say what software can run and can not on his hardware, there is just one thing to do: to protest loudly. The issue is so important for our future that there should be a law explicitly prohibiting all the possible forms of software censorship, at least about hardware that is sold to end users.

Some math about the Engineyard contest

▼
antirez 6332 days ago.
I did some math, and I think this is the probability of two random SHA1 strings having the hamming dinstance of 'D':

    (1/2^160)*(160!/((160-d)!*d!))

This is why. For example imagine we want to compute the probability of an hamming distance of 2. I want the first bit to be not equal, that occurs with a probability of .5, the second bit to be not equal too, again .5, the others to be equal, that is .5 each. This are independent events, so we need to multiply them together, basically for any given pattern of equal/not equal we want there is a probability of .5^160 for a specific arrangement of equal/not-equal of the bits.

Gli italiani sono spammer

▼
antirez 6345 days ago.
E oggi sono arrivati al punto di tentare di colonizzare anche programming.reddit.com:

Programming Reddit colonizzato da tristi spammer italiani

Programming Reddit è una community composta da persone interessante alla programmazione e all'hacking. Al contrario di quello che avviene in Italia dove la maggior parte delle persone tenta di abusare dei servizio di social news e social bookmarking negli altri posti è possibile creare bellissime community di grande qualità che ti fanno crescere e sono di stimolo.

Condividere le statistiche di LLOOGG tra diversi account

▼
antirez 6353 days ago.
Dopo aver sistemato il problema della scalabilità (almeno tecnologicamente, a livello hardware non mi illudo che ce la faremo per sempre con soli due server ;) abbiamo ricominciato a lavorare a nuove funzionalità: la prima in ordine di mia personale wishlist era sicuramente la possibilità di condividere i dati con gli amici, o se si hanno più siti, di aprire più account, uno per sito, e poterli consultare tutti comodamente dall'account principale.

Per usare la funzione basta andare su "Settings" e inserire lo username dell'utente a cui si vuole dare la possibilità di accedere alle nostre statistiche. Gli account free possono specificare un solo utente mentre per gli account PRO non c'è alcun limite.

Grafico del carico sul DB di LLOOGG dopo lo switch a Redis

▼
antirez 6359 days ago.
Penso che l'immagine si commenta da sola, guardate come crolla dopo Venerdì:

Crollo del carico dopo lo switch a Redis

Da notare che il traffico che rimane dopo lo switch, quelle piccole ondine non sono neppure quelle frutto di Redis... se ci fate caso nella onda del load di MySQL erano già presenti su una scala più piccola. Infatti sono dovute allo script di generazione dei grafici di carico e altri cose minori nel cron.

LLOOGG: ora completamente su Redis

▼
antirez 6360 days ago.
Qualche mese fa LLOOGG schiattava clamorosamente, complice una macchina DB troppo piccola e una tecnologia di database errata per il servizio...

Da quella esperienza è nato Redis, dunque non la maledico :) Redis si avvicina alla maturità, e tra poco uscirà la release stabile 1.0, ma da questa mattina è già l'unico quore di LLOOGG (MySQL è stato fisicamente spento...). Il carico sulla macchina si è abbassato a livelli ridicoli (posterò grafici a breve), e io sono molto contento di avere una soluzione completamente distribuita per il futuro di questo servizio.

MongoDB and Redis: a different interpretation of what's wrong with Relational DBs

▼
antirez 6375 days ago.
Working to Redis is a good feeling for me: it's not something about money, or deadlines, or customers not agreeing with me, but about trying to do my 2 cents in order to help the field to go forward. It's a joy to work to things you love, especially if you have the feeling that you don't want to win: even if a few ideas of your work will be useful for another experiment or implementation it is already worth it. It's like science, what matters is to know more, to find better solutions to problems, and so on.

Milano

▼
antirez 6399 days ago.
A Milano ci sono stato un sacco di volte, ma non la conosco di persona.

E' come arrivare a Linate perchè Malpensa è distante, e poi a San Babila, che non ti ricordi mai il verso giusto per riprenderlo quell'autobus, e non è segnato da nessuna parte anche se troppe persone hanno bisogno di prenderlo.

Organizzazione, puntualità, silenzio, decoro, produci.

O meglio, fai finta di produrre, l'importante è questo. Poi magari sbatti la testa su quel problema dal verso sbagliato 1000 volte, non capisci un cazzo, lo sai, ritenta, cambia angolazione. Sovrastrutture, lo si fa lo ha detto il capo non ha senso non ci fa niente pazienza, anche se cambia idea tra poco.

Ci sono due tipi di conoscenza

▼
antirez 6401 days ago.
Da un commento che ho scritto su programming.reddit.com, una cosa che ho sempre pensato. La discussione era scaturita dalla domanda di un utente che chiedeva se fosse il caso o no di imparare a sviluppare con gli strumenti Microsoft.

There are two kind of programming knowledge:

a) the kind of knowledge that never goes away. To know how a linked list works or the time complexity of randomized qsort is really valuable. The more you can know about this stuff, the better.

b) non-general knowledge, that is, knowledge that aliens from beta-orionis can't know about: they probably know about qsort, and prime numbers, and linked lists, and parallelization. This are concepts not invented, but... mostly discovered. Instead non-general knowledge is how to configure Apache, how a particular programming language works (and not the general abstraction it implements), and how Microsoft technologies work.

You are required to learn a lot of b-type stuff, but the lesser the better, so you have to learn environments, languages, that are powerful, cheap, affordable, available, reliable, ...

Presentazione su Redis di Michelangelo Altamore

▼
antirez 6410 days ago.
Oggi Michelangelo Altamore ha fatto una presentazione su Redis al Barcamp Catanese. Ha espresso le idee fondamentali di Redis meglio di come avrei saputo fare io stesso, giudicate voi scaricando la presentazione. Io non sono andato (!) pur essendo a pochi chilometri perchè oggi avevo un impegno che mi relegava a casa, ma è bell'impegno almeno :) Il mio simpatico figlioletto.

Dinamiche Rosa - migliorato e iniziamo ad avere utenti!

▼
antirez 6412 days ago.
Abbiamo messo online Dinamiche Rosa con la nuova veste grafica e alcune nuove funzionalità], sono molto contento perchè è venuto bene ed Ester Cavalcanti, la nostra nuova grafica, ha fatto un buon lavoro e ha migliorato il prodotto assieme agli sviluppatori da molti punti di vista.

Incredibilmente non appena abbiamo messo la nuova grafica online abbiamo iniziato a ricevere utenti... sarà un caso? Credo di no. Diverse persone si sono iscritte e usano il sito e noi abbiamo sempre più voglia di migliorarlo.

Ma se l'universo è finito cosa c'è oltre i suoi confini?

▼
antirez 6421 days ago.
Qualche giorno fa stavo parlando con alcuni miei amici di cosmologia. Come accade spesso durante queste discussioni si finisce per parlare di universo chiuso o aperto, e alla fine, inevitabilmente, delle dimensioni dell'universo. E allora scatta la domanda: ma se l'universo è finito, cosa c'è oltre i suoi confini?

Questa non è esattamente una domanda da niente, ed è del tutto fuori dalla mia portata, però l'ultima volta che mi è stata fatta questa domanda ho risposto in un modo che ha convinto anche me stesso, utilizzando un parallelo informatico (stavo parlando con persone che capiscono come funziona un programma). Ecco la mia risposta.

Merlionox si lamenta di oknotizie. La rivincita degli spammer?

▼
antirez 6425 days ago.
Incredibilmente, Merlinox, uno degli utenti che ha per primo utilizzato il sistema in maniera impropria costringendoci a creare i primi sistemi piu' evoluti di anti fronde, si lamenta del fatto che oknotizie ha un sacco di problemi.

Ecco la mia risposta sul suo blog, che spero pubblichera':

Oknotizie ha evidentemente dei pregi e dei difetti. Alcuni sono propri del sistema, altri, essendo un servizio largamente creato dagli utenti, scaturiscono da questi.

Smuvi e' ora Virgilio Film

▼
antirez 6429 days ago.
Da ieri notte alle tre, Smuvi, un sistema di raccomandazioni e una community sul cinema che Kiurma (la mia nuova azienda per chi non lo sapesse) ha sviluppato circa un anno addietro, fa ora parte di Virgilio sotto il nuovo nome di Virgilio Film.

Al contrario di quanto accaduto con Oknotizie/Segnalo Smuvi sta per essere venduto a Matrix, non e' una partnership, ma siamo ancora noi a sviluppare il sito per conto loro e in questo caso anche ad erogarlo (erogare siti ad alto traffico puo' essere una bella esperienza quando si sviluppa sia il software che l'architettura hardware).
: