Aqueduct for Dart is dead: Now what?

 


The company/developers behind the server side framework Aqueduct just announced the project is now closed. What happened? Why was the project shut down? What to do now?

We are all aware of Google's Graveyard, and that's one of the main reasons major corporations are not switching to Flutter yet. Google's attention span for any new project is short, and Google either kills the project or releases a major version that breaks any backward compatibility. Aqueduct was affected by constant Dart updates, which are not bad but keeping up with so many updates will make a project very costly to maintain for an organization.

What to do now? If you are a good boss/project manager, you will rebuild your REST API services with either Symfony or Laravel. Yeah, you can call me "old fashioned" or "stuck in the 90s", but I'm not the one rushing to find a replacement of a critical backend system developed with Aqueduct. Right now, there are some developers that are trying to maintain it as a new project (ViaDuct/Conduit), but as you should already know by now, there isn't an organization behind them, no real leadership, and worst of all no real development roadmap.

What's the lesson here? Choose your framework very wisely. Read forums, users comments, and project managers please: Listen to your own developers.


No comments

Powered by Blogger.