> it's silly to complain that some open source thing might stop being maintained when by default what you write yourself is also not actively maintained ;) I c

> it's silly to complain that some open source thing might stop being maintained when by default what you write yourself is also not actively maintained ;) I certainly agree to a large extent, but there's a lot that mitigates this as well: When it's code you write, you have control over feature creep, documentation, comments, etc. If you write something that only does what you need, you reduce a lot of the attack surface vs. off the shelf plugins, and you are in a position to make sure that the code commented and well documented. You don't have that sort of quality control over a third party plugin, and you may down the line be in for a rude awakening when it's no longer developer and has a breaking problem, and you open it up and find the code is a completely undocumented mess from top to bottom. Of course if you're rushing something out the door, you might not produce anything better - but if you're a software shop with solid engineers, you have a high chance of being able to get better quality code out there than a lot of WP plugins. (That being said, WP today is a lot more secure itself than it was in the past - the right option might be not writing the CMS from scratch, but writing any plugins you need from scratch)