כיון שעיני צרה בשל אחרים, החלתי לבדוק את המערכת של וורדפרס [u:1lrbf6l0]מכיוון המפתח[/u:1lrbf6l0].
מפתחים טענו בפני שמדובר בFramework שחוסך לך יסודות שלוקחים הרבה משאבים, ומקפיץ אותך לגמר האפליקציה במהירות שיא, זה כמובן תמורת מחירי המוגבלות של וורדפרס. טוב, אז אני דבר ראשון מתווכח (אפי' שאני לא מכיר בכלל את וורדפרס :?) ואני אומר "מה פתאום, דוט נט זה פי 10 טוב לנקודת פתיחה" וכו'.
בשלב שני, אני ניגש לבדוק בשקט את וורדפרס, רק בשביל להוכיח את טענותיי 
. מקוה שעמיתי יעשו גם כן ככה לדוט נט (MVC, אלא מה), יציצו ויפגעו.
אז התחלתי לקרוא ספר (זה באנגלית אז אני קורא בעיקר את הציורים :)), והגעתי לקטע שחשוב לי לשתף, לכל מי שמחליט אם דרכו ([u:1lrbf6l0]מבחינת מתכנת!![/u:1lrbf6l0]) בוורדפרס או שמא ב...
הקטע לפניכם באנגלית, בע"ה בימים הקרובים אתרגם הכל (עם טרנסלט של גוגל למי שחשב שאני יודע ע' לשונות).
Understanding limitations and sticking
with guidelines
As with every framework, WordPress has its limitations in developing web
applications. Developers need to understand the limitations before deciding
to choose a framework for application development.
In this section, we are going to learn the limitations while building simple guidelines
for choosing WordPress for web development. Let's get started:
• Lack of support for MVC: We talked about the architecture of WordPress
and its support for MVC in one of the earlier sections. As a developer, you
need to figure out ways to work with WordPress in order to fit with your
web applications. If you are someone who cannot work without MVC,
WordPress may not be the best solution for your application.
• Database migration: If you are well experienced in web development, you
will have a pretty good idea about the importance of choosing databases
considering the possibilities of migrating to another one in later stages.
This could be a limitation in WordPress as it's built-in to work with the
MySql database. Using it with another database will be quite difficult, if
not impossible. So if you need the database to be migrated to some other
database, WordPress will not be the best solution.
WordPress As a Web Application Framework
[ 22 ]
• Performance: Performance of your application is something we get to
experience in later stages of the project when we go into a live environment.
It's important to plan ahead on the performance considerations as it can come
through internal and external reasons. WordPress has a built-in database
structure and we are going to use it in most of the projects. It's designed
to suit CMS functionality and sticking with the same tables for different
types of projects will not provide an optimized table structure. Therefore,
performance might be a limitation for critical applications interacting with
millions of records each day, unless you optimize your caching, indexing, and
other database optimization strategies. WordPress runs on an event-driven
architecture, packed with features. Often developers misuse the hooks without
proper planning, affecting the performance of the application, so you have to
be responsible in planning the database and necessary hooks in order to avoid
performance overheads.
• Regular updates: WordPress has a very active community involving its
development for new features and fixing the issues in the existing features.
Once a new version of core is released, plugin developers will also update
their plugins to be compatible with the latest version. Hence, you need to
perform additional tasks for updating the core, themes, and plugins, which
can be a limitation when you don't have a proper maintenance team.
• Object-oriented development: Experienced web developers will always
look for object-oriented frameworks for development. WordPress started
its coding with procedural architecture and is now moving rapidly towards
object-oriented architecture, so there will be a mix of both procedural and
object-oriented codes. WordPress also uses hook-based architecture for
providing functionality for both procedural and object-oriented codes.
Developers who are familiar with other PHP frameworks might find it
difficult to come to terms with the mix of procedural and object-oriented
code, as well as hook-based architecture, so you have to decide whether you
are comfortable with its existing coding styles.
If you are a developer or designer, who thinks these limitations could cause major
concerns for your projects, WordPress may not be the right solution for you.
פורסם במקור בפורום CODE613 ב23/07/2014 18:41 (+03:00)
?