I don't buy the argument that textual code is a remnant of our mathematical past and visual programming is the future. Surely our writing systems are just as text-based and yet, I don't see anyone proposing we supplant them with pictograms.
Aside from that, many problems are simply not suited to an event-based model, just as many problems are not suited to functional models and others are not suited to imperative models. There is not, and will never be, a one size fits all approach to development.
The reason software is so susceptible to errors is nothing to do with the model of its development, but rather that bugs can be "hidden" until the program is running, and commonly much longer after that. This is why you rarely get bugs in CSS, HTML or PNGs - the full results of modifications can be seen in near real time. When you do get bugs in HTML or CSS, they are browser issues or issues with resizing - things that are not immediately apparent.
Importantly, any programming environment sufficiently well equipped to be useful, will always have places to hide bugs. Event-based programming does nothing to address this, in fact I think it provide more bugs.