There's rarely a right answer to this fight. It's a question that has raged on since software was sold "off the shelf". Many pros are also cons.
Pro 3rd-party:
They cover a vast number of features
They (hopefully) look after security
Open source means other people can fix your platform.
You get improvements without having to work on your own platform
They have existed a lot longer than your newly conceived project. A lot bugs have been driven out.
Anti 3rd-party:
They don't have all the answers for every project
By extension, it may take you longer to hack in what you need than it would take to just start afresh
Unless you're using it exactly as intended, performance isn't going to be as good as it could be with a custom-built
Larger target for hackers and script kiddies
As they're older, they can be locked (via legacy support) into some bad habits (Drupal and Wordpress certainly have enough)
So if you're doing a blog, unless there are features or platform issues, I'd seriously consider WordPress. If you only needed a very simple blog attached to a much larger system that was completely non-blog, I'd probably write my own as part of that system.
Just to blur the lines, the modern frameworks (Cake, Symphony, Django, Ruby, etc) handle lots of the security, database, usability and let you develop the application without having to worry too much about anything. You get exactly what you want and you get it fast but it probably won't be as polished (eg for blogging) as WordPress.
Whatever the scenario, if there is a solution out there that meets your needs, it's open source and your team as the knowledge to make any specific change it might need to meet your purpose, it is probably a good choice to use it. It will save you time(time is money) that you could use to other tasks.
From a developer perspective, it is way more appealing to create something from scratch.
You just have to keep in mind that this is not something you are doing as hobbie, you need to have a product out there as fast as possible, with as few errors as possible, with all the features that the users would expect.
How much time/money would it require to roll your own?
Does the open source solution you're considering have the features you need (and do they work*)?
How would maintenance of the two solutions compare?
Some "common" answers:
A lot, particularly if you need (or want) a lot of features.
Most of the mature systems have some kind of plugin system and heaps of functionality. Generally if you want it they got it, perhaps some minor tweaks would be necessary.
In-house code may need some time to mature, after this they will probably be about the same. If in-house code is low on features then it may be easier to maintain.
She also says that we might even loose time and money on it since it is our responsibility to maintain it and solve bugs
How is that worse than an in-house solution exactly?
If you are selling services using an existing open source product can make a lot of sense. (And by the way, you probably can get the wordpress people to work for you - you'll have to pay of course, but you also have to pay your in-house team)
If this blogging system is only for your own usage it makes even more sense to use an existing solution, and the open source solutions stand out in that area because there are a lot of people available that could code some custom solutions for you.
Only if you are actually selling the software the situation with open source becomes a bit harder to get a grip on money-wise.
Yes, there are a lot of reasons. Being open-source doesn't mean it'll automatically be well written.
However, sometimes it really fits your business model because you need to ship something fast, usable, not too specific in requirements and already tested by millions of people. In this case, doesn't make sense to produce something in house.
If you want to convince her of using Wordpress instead of building one, show the arguments on time and money that would be spent in trying to write from scratch instead of using an open source solution. Don't forget to show some live examples from big companies that are using Wordpress (check the official website).
For most companies, developing your own blogging solution is the equivalent of developing your own version of the machine that mixes the tarmac to make the road that leads to your office.
The only exception is if you want to get into the road-building business. But that's a hard and competitive business, an established stable market with a lot of capital requirements, not something to wander into.
发布评论
评论（7）
这场斗争很少有正确的答案。自从软件“现成”出售以来，这个问题就一直存在。许多优点也有缺点。
专业第 3 方：
反第 3 方：
因此，如果您正在写博客，除非存在功能或平台问题，否则我会认真考虑 WordPress。如果您只需要一个非常简单的博客附加到一个完全非博客的更大系统，我可能会编写自己的博客作为该系统的一部分。
只是为了模糊界限，现代框架（Cake、Symphony、Django、Ruby 等）处理大量的安全性、数据库、可用性，让您开发应用程序而不必过多担心任何事情。你得到了你想要的东西，而且速度很快，但它可能不会像 WordPress 那样精致（例如博客）。
There's rarely a right answer to this fight. It's a question that has raged on since software was sold "off the shelf". Many pros are also cons.
Pro 3rd-party:
Anti 3rd-party:
So if you're doing a blog, unless there are features or platform issues, I'd seriously consider WordPress. If you only needed a very simple blog attached to a much larger system that was completely non-blog, I'd probably write my own as part of that system.
Just to blur the lines, the modern frameworks (Cake, Symphony, Django, Ruby, etc) handle lots of the security, database, usability and let you develop the application without having to worry too much about anything. You get exactly what you want and you get it fast but it probably won't be as polished (eg for blogging) as WordPress.
好问题，+1 :)
我的意见：
无论什么情况，如果有一个解决方案可以满足您的需求，它是开源的，并且您的团队拥有进行任何特定更改的知识来满足您的目的，那么它就是使用它可能是一个不错的选择。它会节省您的时间（时间就是金钱），您可以将其用于其他任务。
从开发人员的角度来看，从头开始创建一些东西更具吸引力。
您只需记住，这不是您出于爱好而做的事情，您需要尽快推出一款产品，尽可能减少错误，并具有用户期望的所有功能。
Good question, +1 :)
My Opinion:
Whatever the scenario, if there is a solution out there that meets your needs, it's open source and your team as the knowledge to make any specific change it might need to meet your purpose, it is probably a good choice to use it. It will save you time(time is money) that you could use to other tasks.
From a developer perspective, it is way more appealing to create something from scratch.
You just have to keep in mind that this is not something you are doing as hobbie, you need to have a product out there as fast as possible, with as few errors as possible, with all the features that the users would expect.
实际上，这可以归结为：
一些“常见”答案：
这比内部解决方案到底差多少？
Really it comes down to this:
Some "common" answers:
How is that worse than an in-house solution exactly?
这实际上取决于您的商业模式。
如果您使用现有的开源产品销售服务可能会很有意义。 （顺便说一句，您可能可以让 wordpress 人员为您工作 - 当然您必须付费，但您还必须向您的内部团队付费）
如果这个博客系统仅供您自己使用，使用现有解决方案更有意义，并且开源解决方案在该领域脱颖而出，因为有很多人可以为您编写一些自定义解决方案。
只有当你真正销售软件时，开源的情况才会变得更难控制金钱。
This really depends on your business model.
If you are selling services using an existing open source product can make a lot of sense. (And by the way, you probably can get the wordpress people to work for you - you'll have to pay of course, but you also have to pay your in-house team)
If this blogging system is only for your own usage it makes even more sense to use an existing solution, and the open source solutions stand out in that area because there are a lot of people available that could code some custom solutions for you.
Only if you are actually selling the software the situation with open source becomes a bit harder to get a grip on money-wise.
我们的主持人 Joel Spolsky 就此主题撰写了一篇有趣的文章。
Our host Joel Spolsky has written an interesting article on this subject.
是的，原因有很多。开源并不意味着它会自动写得很好。
然而，有时它确实适合您的业务模式，因为您需要快速交付、可用、要求不太具体并且已经经过数百万人测试的东西。在这种情况下，内部生产是没有意义的。
如果您想说服她使用 Wordpress 而不是构建 WordPress，请展示关于尝试从头开始编写而不是使用开源解决方案所花费的时间和金钱的论点。不要忘记展示一些来自使用 Wordpress 的大公司的实例（查看官方网站）。
Yes, there are a lot of reasons. Being open-source doesn't mean it'll automatically be well written.
However, sometimes it really fits your business model because you need to ship something fast, usable, not too specific in requirements and already tested by millions of people. In this case, doesn't make sense to produce something in house.
If you want to convince her of using Wordpress instead of building one, show the arguments on time and money that would be spent in trying to write from scratch instead of using an open source solution. Don't forget to show some live examples from big companies that are using Wordpress (check the official website).
对于大多数公司来说，开发自己的博客解决方案相当于开发自己的机器版本，该机器将柏油路面混合起来，开辟通向办公室的道路。
唯一的例外是如果您想进入道路建设业务。但这是一项艰苦且竞争激烈的业务，是一个既定的稳定市场，有大量的资本要求，不适合闲逛。
For most companies, developing your own blogging solution is the equivalent of developing your own version of the machine that mixes the tarmac to make the road that leads to your office.
The only exception is if you want to get into the road-building business. But that's a hard and competitive business, an established stable market with a lot of capital requirements, not something to wander into.