I recently discovered Dropwizard, which I found to be incredibly easy to use and eminently readable. The example code I saw for Vert.x, on the other hand, reminded me of the "callback spaghetti" I've heard lamented as a problem in NodeJS. Do I have a poor first impression? Can someone sell me on Vert.x for web-facing applications? Am I the wrong audience because I'm using other technologies like RabbitMQ to handle distributed polyglot work? [Apologies if I come across like a hater, because I'm not; I'm genuinely confused about whether Vert.x represents an improvement or an alternative to my situation.]
We're using Vert.x internally to do basically all of our IO (network client and server, disk) in an asynchronous manner, because its API is super simple and elegant. Because much of our other code is already asynchronous and event-driven, Vert.x fits in nicely.
The callback hell is certainly something that you can run into , but we've created a sane Java construct to avoid it:
Were they ever doing the wrong thing? The idea that the IP and full control of the project could just walk over to Redhat with the developer when he took a new job to work on it there after VMware initially funded it all seems incredibly naive at best.
When VMware said that Tim Fox couldn't be in control any more but they didn't name anyone else to lead the project, one possible interpretation was that the project would have no official leader at all. VMware could have avoided that confusion.
