Skip to content

Comment on Never Say WordPress When Selling a Web Design Projectparent

Comments

> there is certainly a cost involved in on-going maintenance, security, expandability and flexibility.

As there would be on a commercial platform (plus some extra), so what's your point?

The point is that cost of maintenance/etc.. could be different between different solutions: let's say the customer is a Microsoft shop, with some internal .Net/SQL Server skills (or just licenses or external maintenance contract): choosing i.e. DotNetNuke could be more cost-effective than opting for a Wordpress/Drupal/other LAMP solution. The same is true comparing OSS solutions too: say you have to compare two proposed OSS web solutions, one is running on the typical LAMP, the other one is FreeBSD/Erlang/PostgreSQL. They're both free and open, right? But if the customer has already some linux and/or mysql and/or php skill inside, the choice could be driven (also) by technical aspects.

I think that was the point.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.