The author had a piece of software running and it started to slow down over time. They ignored it and marched on. It slowed down even more and they had a demo fail. (The author did not mention this explicitly, but I assume it was working fine at the demo rehearsal but slowed down and failed in front of audience).<p>So instead of trying to debug the slowdown or try to fix the system in some other way they decided to just ... switch to a completely different system. No trying to understand what's going on, not even a bug search on the tracker.<p>This seems pretty wrong to me. It's like saying "hey, I recently started to use Java, and I just hit a GC delay in my Java program -- so I am dropping Java completely and switching to Go". Yeah, sometimes switching to a new tech is the right thing, but you are supposed to at least try to tune the existing stack a bit before replacing it outright.