与使用wordpress或类似工具相比，编写自己的博客引擎的优缺点 [英] Advantages and disadvantages of coding your own blog engine versus using wordpress or similar

问题描述

与使用现有的引擎(例如，但不一定是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)?

推荐答案

今天使用已开发的博客应用程序的最大原因是 可能是互操作性.当今经验丰富的博客应用程序包括 插件和基本的开发惯性，确保您可以很好地交互 包括Twitter，Flickr和社交网站.只有一个 出色的开发人员(花费大量时间)将能够自定义代码 适用于所有API的解决方案，以及在博客的整个生命周期内，他们都希望使用或至少尝试一下的其他方法.构建自定义博客应用程序是使其默认状态成为基本隔离的状态.而且隔离许多博客是行不通的.

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.

无论如何，使用自定义博客应用程序的最大好处是，您可以对应用程序的核心行为保持高度控制，并且由于您很可能将其托管在自己的服务器上，因此可以直接访问其统计指标.如果您提前知道自己将不在乎诸如RSS或其他一个或2个其他渠道的互操作性，并且有时间投​​资于核心开发，那么自定义博客是一种保持外观和感觉的好方法.将会使习惯惯常使用WordPress或Blogspot布局的访问者感到非常震惊.似乎存在的一个主要陷阱是，现成的博客应用程序要求您学习如何操纵其各种演示文稿.如果您只是想采用通常存在的数千个主题"，这并不难，但是，您的演示文稿将不会是唯一的.博客的访问者迟早会在其他地方遇到相同的外观.解决方案是聘请自定义开发人员，但这当然要花钱.即使您是那个开发人员，也将为核心功能而花费大量的时间进行编码，学习和表示个性化编码.两种方式都很昂贵.

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.

我自己正在为这个问题而苦苦挣扎.作为网络上一切独立"的支持者，我讨厌放弃对博客进行低级控制的想法.自从消费者网络首次起飞以来，我就一直在线，并且了解使用记事本和FTP客户端可以轻松创建网站的过程.对我来说，这些基本工具之外的任何东西都是"AOLish"，但是，许多博客应用程序现在已经演变为完整的内容管理框架，可以与仅掌握基本HTML的掌握知识的复杂性相媲美.我终于对一些较流行的博客解决方案(WordPress，Blogger)进行了深入的实验，并震惊地发现，在花了很多时间维护自己的解决方案之后，它有多快(更好)了.与他们一起撰写和管理条目.由于我的大多数博客都不是盈利项目，因此撰写时间并不是我的考虑因素.但是，这可能会改变.如果涉及到我需要管理和关注自己的内容而不是机制，以便使我的信息发布出去，我可能会转向经验丰富的博客应用程序模式，并希望我对我的平台有所了解，以使其成为一种真正独特的体验.对于像我们这样的人来说，这可能是最好的结果.

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.

• 戴夫

这篇关于与使用wordpress或类似工具相比，编写自己的博客引擎的优缺点的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！