与使用 WordPress 或类似引擎相比，编写自己的博客引擎的优点和缺点
与使用现有引擎（例如但不一定是 WordPress）相比，从头开始编写自己的博客引擎有哪些优点和缺点？
What are the advantages and disadvantages of coding your own blogging engine from scratch, versus using an already existing engine (for example, but not necessarily, wordpress)?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
如今使用开发的博客应用程序的最大原因是
可能是互操作性。当今成熟的博客应用程序包括
插件和基本的开发惯性，确保您能够良好地交互
Twitter、Flickr 和社交网站等。只有一个
出色的开发人员（有很多时间）将能够自定义代码
针对所有 API 和其他附加功能的解决方案，在博客的生命周期中，他们将想要使用或至少尝试一下。构建自定义博客应用程序就是使其默认状态基本上是隔离的。而且许多博客的隔离不起作用。
无论如何，使用自定义博客应用程序的最大优点是您可以对应用程序的核心行为保持高度控制，并且由于您可能将其托管在自己的服务器上，因此可以直接访问其统计指标。如果您提前清楚地知道您不会关心除 RSS 或一两个其他渠道之外的互操作性，并且有时间投资于核心开发，那么自定义博客是保持外观和感觉的好方法。肯定会让习惯了 WordPress 或 Blogspot 不变布局的访问者感到惊讶。一个主要的陷阱似乎是，现成的博客应用程序要求您学习如何操作它们的各种演示文稿。如果您想简单地采用通常存在的数千个“主题”，这并不难，但是您的演示文稿将不再是唯一的。您博客的访问者迟早会在其他地方遇到完全相同的外观和感觉。解决方案是聘请定制开发人员，但这当然要花费$$$。即使您是那个开发人员，最终会为了核心功能而牺牲编码时间，为了表现个性而学习和编码。无论哪种方式都很昂贵。
我自己也在为这个问题而苦苦挣扎。作为网络上“一切独立”的支持者，我讨厌放弃对博客的低级控制的想法。自从消费者网络首次兴起以来，我就一直上网，并且了解只使用记事本和 FTP 客户端即可轻松创建网站。对我来说，除了这些基本工具之外的任何东西都是非常“AOLish”的，然而，许多博客应用程序现在已经发展成为完整的内容管理框架，其复杂性可以与掌握曾经仅仅弄清楚基本 HTML 所需的复杂性相媲美。我终于对一些更流行的博客解决方案（WordPress、Blogger）进行了深入的实验，并且惊讶地发现，在花了这么多时间维护我自己的解决方案之后，它的速度有多快（而且好得多）与他们一起撰写和管理条目。由于我的大多数博客都不是盈利项目，因此撰写时间对我来说并不是一个因素。然而，这可能会改变。如果归结为我需要管理和更多地关注内容而不是机制来传达我的信息，我可能会转向经验丰富的博客应用程序模式，并希望我对我的平台有足够的了解，使其成为真正独特的体验。对于像我们这样争论这个问题的人来说，这可能是最好的结果。
The biggest reason for going with developed blogging applications today is
probably interoperability. Seasoned blogging applications of today include
plug-ins and fundamental development inertia that ensures that you will interface well
with things like Twitter, Flickr, and social networking sites. Only a
spectacular developer (with a lot of time) would be able to custom code a
solution for all the APIs and other bells and whistles that, in the course of a blog's lifetime, they will want to use or at least experiment with. To build a custom blogging application is to make its default state a basically isolated one. And isolation for many blogs doesn't work.
The biggest plus for using a custom blogging application anyway is that you retain a high degree of control over the application's core behavior, and, since you will likely host it on your own server, direct access to its statistical metrics. If you know well ahead of time that you will not care about interoperability beyond, say RSS, or one or 2 other channels, and have the time to invest in core development, a custom blog is a great way to maintain a look and feel that will positively startle visitors who are used to a constant WordPress or Blogspot layout. One major pitfall, it seems, is that off the shelf blogging applications require you to learn how to manipulate each of their various presentations. It's not hard if you want to simply adopt any thousands of "themes" that typically exist for them, but then, your presentation will not be unique. Sooner or later a visitor to your blog will encounter the same look and feel elsewhere, exactly. The solution there is to hire a custom developer but that of course costs $$$. Even if YOU are that developer who will wind up trading coding-for-core-functionality time, for learning and coding for presentational individuality. Expensive either way.
I am struggling with this question myself. As a proponent of "everything independent" on the web I hate the idea of giving up low level control of my blog. I've been online since the consumer web first took off and understand the ease by which a website can be created using nothing but notepad and an FTP client. To me, anything beyond these basic tools is very "AOLish", and yet, many blogging applications have now evolved into full content management frameworks that would rival the complexity of mastering that which it once took just to figure out basic HTML. I've finally taken to in-depth experimentation with some of the more popular blogging solutions (WordPress, Blogger), and am shocked to find out that after spending so much time maintaining my own solutions, how quickly (and much better) it is to compose and manage entries with them. Since most of my blogs are not profit projects, time to compose has not been a factor for me. However, this may change. If it comes down to where I need to manage and concern myself more with content than mechanics to get my messages out, I will probably swing to seasoned blogging app mode and hope I learn enough about my platform to make it truly a unique experience anyway. That would probably be the best outcome for anyone like us debating this.
我刚刚建立了自己的博客，我必须自己回答同样的问题。以下是我选择 BlogEngine.Net 的主要原因。我
I just set up my own blog and I had to answer this same question myself. Here are the main reasons I went with BlogEngine.Net
自己编写的优点
缺点
Advantages of writing your own
Disadvantages
其实我也走过了这条路。
出于乐趣和学习的原因，我编写了自己的小型内容管理系统，用于基本的博客。它有相当静态的内容（不允许评论），但这对我来说已经足够了。一年后，我决定切换到 WordPress，并且对此感到非常满意。
今天我会改变我的方法并立即使用 WordPress。
产品角度的原因：
学习的原因观点：
如今，只有在以下情况下，我才会开始构建“从头开始”软件：
Actually I went through this path.
For fun and learning reasons I coded my own little content-management system which I used for rudimentary blogging. It had quite static content (no comments were allowed) but it was enough for me. One year later I decided to switch to wordpress and am really happy with it.
Today I would change my approach and would go for wordpress instantly.
Reasons from product perspective:
Reasons from learning perspective:
Nowadays I would start to build 'from-scatch' software only if: