Hi, Each new service we add to Whirr makes the product harder to maintain and develop. At this stage, as we've discussed in the past, it's really important to focus on evolving the core and improving the underlying abstractions. Unfortunately at the same time we should keep in mind that Whirr is more useful only if it supports more services.
How should we move forward? Refuse to add new services while we improve the core (doesn't sound like a good idea)? Create something like contrib/services for partially supported services so that we can have a clear distinction and decrease the maintenance workload (I would go for this one)? Cheers, -- Andrei Savu / andreisavu.ro
