Alright, I'll write a rebuttal on behalf of the authors. First, they tested their update methodology by applying it to a long history of released versions for

Alright, I'll write a rebuttal on behalf of the authors. First, they tested their update methodology by applying it to a long history of released versions for each piece of software. Second, although any code involving concurrency is tricky, I thought the line counts were actually quite low: C LoC C delta xfgen LoC vsftpd 12,202 113 101 redis 13,387 57 37 Tor 76,090 159 189 memcached 4,181 112 27 icecast 15,759 134 200 where C LoC is the original program length, C delta is the changes to the program, and xfgen LoC is extra specification stuff they had to write. Third, how is a broken online update any worse than a broken offline update? Is there a greater argument for data loss?