Comparison of the pros and cons of discuz and phpwind

discuz! (referred to as dz) and phpwind (referred to as pw) are the two most famous PHP forum systems in China. After they successively announced their open source, they have improved in all aspects, regardless of technology or function. It has made great progress in terms of technology and interface, and its reputation has been greatly improved. It is far from comparable to those foreign electronic bulletin board systems with simple functions.

One of its side effects is that it has greatly promoted the popularity of PHP in China (I only started to pay attention to PHP when I was looking for a suitable forum program, and I couldn't help myself. ).

1. Interface (Recommended learning: PHP video tutorial)

First of all, from the interface point of view, from the overall point of view , dz’s interface is relatively beautiful and has a good overall feel.

The interface of pw gives people a feeling of imitating dz. At the same time, in terms of the details of the interface, it seems that pw is still not as perfect as dz.

2. Technical articles

Technically speaking, both pw and dz use file-based data caching technology, by converting commonly used Data tables, such as forum layout parameters, basic parameters, etc., generate static cache files (triggered updates or manual updates based on conditions) to reduce the number of database reads and improve efficiency. In this aspect, the two are very similar.

1. Template technology

In terms of template technology, dz has adopted this static template technology since version 2.5f. From my personal point of view, It is still very suitable for frequently updated website programs such as forums. It solves the problem of template parsing efficiency by dynamically generating static templates.

At the same time, dz’s template method makes it easier and more intuitive to modify the interface.

The way pw uses the echo statement (let's call it a template) is much more shabby. It takes a long time to add an if judgment condition. Templates that are mixed with PHP code are easily deleted by mistake in Dreamweaver. Especially if you are not careful when modifying, it is likely that the web page will become a whiteboard (no output), making me walk on thin ice every time I modify the pw template. . . . I'm afraid this is also the reason why there are far more dz than pw in third-party templates.

However, pw is also improving its templates. Now verycms 3.0 has begun to use real template technology, but the current ones are still relatively rudimentary. . .

2. Speed ​​issue

From the template point of view, the efficiency of the two should be similar. The pw template is actually a part of the PHP file that directly contains mixed PHP statements. The dz template usually does not need to be parsed, so the efficiency should be about the same. However, there are always people on the Internet who claim that the website using dz is slower than pw. I have not tested this aspect and dare not make any comments. Moreover, website access speed is still affected by many factors, such as local network speed, server bandwidth, and psychology. . . . . Objective evaluation is still difficult unless professional technical means are used. However, judging from the speed of the official website, it is obvious that pw is dominant, haha

3. Functions

Below I will talk about dz5.5 and pw5.3 Function, let’s do a simple analysis, which I think is relatively in-depth, but may be too simple for experts. Please correct me:

1. Login method:

pw’s front desk login and Different cookie methods are used for background login. This way of separating the front and backend, I personally feel, is conducive to security and easy to manage. The backend account and the frontend account can be completely separated.

The front and backend login of dz uses an account. Although it prompts you to enter the password again when entering the backend, it is still not as convenient as pw.

What is special is that when registering, dz requires you to enter a prompt question (optional), and there is also an interface prompting input in the login interface. Personally, I feel that it is absolutely superfluous and boring. It makes sense to use prompt questions to retrieve passwords. The way of prompting questions makes novices confused and dizzy after reading it

2. Column display:

pw supports left and right column display starting from 5.0.1, but the function is too It is simple and cannot display sub-sections in a tree. It is better to say that it does not have this function. It is a bit funny and is a semi-finished product (but it is also in line with pw's usual characteristics - it likes to launch some imperfect things for everyone to modify).

After looking at the column display of dz5.5, I can see that it is quite perfect and feels pretty good.

3. Efficiency of background management:

pw's horizontal operation is very good, which greatly saves the difficulty of management, especially when setting permissions according to user groups, it is very convenient. dz needs improvement in this area.

dz provides a solution to solve the problem of repeated operations in the background. It should be said that it makes sense, but it is not easy to use. If it is to set up a separate project, it will be more cumbersome.

4. Personal space (collection) function:

dz5.5 has a built-in minispace personal space function. It can be said that since discuz merged with supsite, it has taken a great advantage in the outreach of forum functions and attracted the attention of many personal websites.

In the official words of dz, this minispace is like this:

"Full use of the original resources of the forum, members can have a personalized display page without having to pay more

Perfectly combined with X-Space, it can smoothly realize the natural transition between MiniSpace and Form a collection of articles for easy access by others. I have seen this function in other forums before and thought it was very good. I didn't expect dz to integrate it. This function can already meet the functional requirements of most forums. If the requirements are higher, for example, if you want to allow users to publish b0 guest articles, according to the official statement, you can also migrate to X-space. But more importantly, minispace is open source, while the source code of X-space is not open source.

Speaking of X-space, we feel that although pw is comparable to dz in terms of functionality, it lags behind dz in terms of forum extension. X-space can realize the personal space function centered on the forum, but pwblog (has been renamed Lxblog, the official version has not been launched, this article only takes version 5.1.5 as an example) is completely different from the forum. Although the post push function has been changed from 4.3.2 It is there, but it has always been difficult to use. After pushing 4.x, the pictures and attachments are not normal. Although 5.1.5 can be pushed normally, the posts updated in the forum no longer appear in the replies in the b0 guest. , it can be said that the push function is just a useless embellishment in pwblog.

In the final analysis, what we often hope for is just a forum post collection function. pwblog repeatedly pushes the content in the forum to b0 customers, which is a waste of space and meaningless. In this regard, dz is far better than Got pw, it deserves praise. However, the functions of minispace are still a bit simple, such as there is no classification function for anthology posts, no recommended posts on the homepage, etc. (Maybe the classification of forum posts is of little significance, but it is better than nothing, right?)

5. Anti-flooding technology

pw5.3 finally accepted my proposal to use the verification code for newbies to register before posting the Nth post. This will not affect the use of old users, but also limit malicious use of the verification code. Watering robot. dz does not provide this function, but it has the function of not using custom Q&A after the Nth post (dz's verification code is terrible and can't be seen clearly at all, and it seems better to use custom Q&A).

In terms of preventing automatic registration, both pw and dz use a custom question and answer method to prevent automatic registration. The specific principle is very simple, and both achieve similar results. The difference is that dz requires more than 10 questions to be set to take effect, while pw can only set one question. In addition, there is another difference, that is, pw can customize the form variable name used internally in Q&A, which may be more effective in preventing malicious automatic registration. pw's custom questions can only be used for registration, while dz's can be used for registration, posting and short messages.

Judging from the current specific applications, the problem of automatic registration can basically be solved with one question (the result of long-term practice). Of course, it does not rule out that very large websites can be easily broken with one question. Possibly, dz may be more effective in this regard. It’s just that the dz limit requires more than 10 to take effect, which is puzzling

The above is the detailed content of Comparison of the pros and cons of discuz and phpwind. For more information, please follow other related articles on the PHP Chinese website!