3 ms·

I switched to Wordpress when I realized that Drupal's Link Field Module (a plugin to add a hyperlink field to an entity) was 1100 lines of code. http://drupal.

by elchief 14y ago

I switched to Wordpress when I realized that Drupal's Link Field Module (a plugin to add a hyperlink field to an entity) was 1100 lines of code. http://drupal.org/project/link http://drupal.org/project/link

level09 14y ago
are these 1100 lines of code executed everytime you render a link field ?
- vog 14y ago
  Although this might be a performance issue as well, I think the real problem is that some unlucky people had to write those 1100 lines of code in the first place.
  - level09 14y ago
    size of code != performance problem in most cases, plus drupal give you an extremely lightweight api method "url() or l()" to render links, its up to you to choose .
ceejayoz 14y ago
If you take a look at the code, most of that's dealing with the backend UI, comments, and stuff broken into multiple lines for readability. Bashing based on LOC is as moronic as the old practice of LOC as a performance metric.
lorin_pa 14y ago
Hi, This a great example of a broader issue. The statement "I switched to Wordpress when I realized that Drupal's Link Field Module (a plugin to add a hyperlink field to an entity) was 1100 lines of code." contains no logical context. Most Drupal developers are not programmers. For example, a Drupal developer may be graphic's designer. Drupal allows end users to define ad-hock data types. That's what "Drupal's Link Field Module" is (a part of). Ad-hock data types are an option, not a requirement. If an end user wants to define an ad-hock data type with a "link", they install and configure "field modules". That's a limitation of being an "end user" (as opposed to being an application programmer). A application programmer would look at Drupal's source code and see there is succinct API method to create a link. So the broader issue is, you have folks with little to no programming experience making application programming decisions :) It's just as likely, the poster's project did not require ad-hock data types. Without any type of requirements analysis, the project fails. Drupal's popularity (at least among CMS's) is due to it's set of logical features. It's not the technical implementation of the features :) The downfall of most Drupal projects is due to poor resource choices. You hire a graphic's designer to implement an inventory system, you are going to get the same results no matter what CMS, frame work, programming language etc :) Sorry, didn't mean to pick on anyone. Without an elaboration, you speculate based on you experience :) That's my experience with Drupal development :) Lots of talented folks asked to do the wrong job :)

by elchief 14y ago

level09 14y ago

are these 1100 lines of code executed everytime you render a link field ?

vog 14y ago
Although this might be a performance issue as well, I think the real problem is that some unlucky people had to write those 1100 lines of code in the first place.
- level09 14y ago
  size of code != performance problem in most cases, plus drupal give you an extremely lightweight api method "url() or l()" to render links, its up to you to choose .

ceejayoz 14y ago

If you take a look at the code, most of that's dealing with the backend UI, comments, and stuff broken into multiple lines for readability. Bashing based on LOC is as moronic as the old practice of LOC as a performance metric.

lorin_pa 14y ago

Hi, This a great example of a broader issue. The statement "I switched to Wordpress when I realized that Drupal's Link Field Module (a plugin to add a hyperlink field to an entity) was 1100 lines of code." contains no logical context. Most Drupal developers are not programmers. For example, a Drupal developer may be graphic's designer. Drupal allows end users to define ad-hock data types. That's what "Drupal's Link Field Module" is (a part of). Ad-hock data types are an option, not a requirement. If an end user wants to define an ad-hock data type with a "link", they install and configure "field modules". That's a limitation of being an "end user" (as opposed to being an application programmer). A application programmer would look at Drupal's source code and see there is succinct API method to create a link. So the broader issue is, you have folks with little to no programming experience making application programming decisions :) It's just as likely, the poster's project did not require ad-hock data types. Without any type of requirements analysis, the project fails. Drupal's popularity (at least among CMS's) is due to it's set of logical features. It's not the technical implementation of the features :) The downfall of most Drupal projects is due to poor resource choices. You hire a graphic's designer to implement an inventory system, you are going to get the same results no matter what CMS, frame work, programming language etc :) Sorry, didn't mean to pick on anyone. Without an elaboration, you speculate based on you experience :) That's my experience with Drupal development :) Lots of talented folks asked to do the wrong job :)