Edit comment Thanks for the congenial

Administration

Authored by

Leave blank for Anonymous.

Homepage

Authored on

Status

Published

Not published

Comment *

Thanks for the congenial explanation of the motivations and goals for BackDrop.  However, I view a couple of minor things differently, and don't follow some of the motivations.  I feel that I can speak to some of this, as I fit into the group of (long-term) self-taught: I've self-learned and forgotten most of around 10 programming languages, and started learning Drupal when D7 came out (and have struggled with it more than any programming language).
<ol>
  <li>If I am going to invest my time in learning something, I want it to be worthwhile (which is part of why I chose Drupal over something simpler).  I bet most self-learners have the same motivation.  So:</li>
		<ol>
		  <li><em>concepts from the professional computer-engineering world</em>: I want to learn the best concepts, not 'hackable' concepts.</li>
		  <li>'<em>high tier of developer</em>': I want to learn from code by written and organized by fully-knowledgeable developers (not 'hackers' like me).  An early learning curve is usually made up for by well-organized and followable code.</li>
		  <li>Symfony framework: I want to learn the best, rather than the easiest-to-learn, framework.  (Analagous to the choice to learn Drupal). A side plus: we don't have to document it, something we as a community are weak at.</li>
		  <li>Object-oriented code:  I self-learned OO over a decade ago for C++ and later used it in Perl.  It's not that difficult to learn — far easier than D7.  With my valuable time, I'd prefer learning professionally-written and organized OO PHP code than 'hacker' procedural PHP.</li>
		</ol>
  <li><em>remove nearly all the old Drupal code from Drupal 8</em> vs. <em>fixing areas of Drupal 7</em>:  Removing most code is made to sound bad, but it seems that if you want to fix the non-intuitive spaghetti nature of Drupal, a major rewrite sounds preferable to a piece-by-piece approach.  I don't follow how a modification of D7 could be a 'lightweight product for low-budget sites'.  The major rewrite sounds preferable here.</li>
  <li><em>the problem is documentation vs. not intuitive enough</em>: certainly agree on 'non-intuitive', but not documentation.  A lot of things would have been so easy to learn if only there were guides to common and best-practice usage.</li>
  <li>Already discussed widely: since we already don't have enough core committers, I don't follow how a fork wouldn't hurt this.</li>
</ol>
In sum, I myself don't follow the logic of such a fork appealing to self-learners: a lot of the things D8 is doing are things I'd want to spend my valuable time on.  It seems more like the fork would appeal to the self-learners who have already gone through the pain of learning D7 and want to keep that working knowledge, and don't want to learn the new code, framework and OO code.  I also wouldn't expect a piece-by-piece approach to improve comprehensibility, simplicity or budget-development better than a major rewrite.
I hope I have expressed myself in as congenial of a way as you have.  Thanks!

Formatting options

Basic

To post pieces of code, surround them with <code>...</code> tags. For PHP code, you can use <?php ... ?>, which will also color it based on syntax.
Web page addresses and email addresses turn into links automatically, unless the parent tag has the 'nolink' class.
Lines and paragraphs break automatically.
Allowed HTML tags: <a> <em> <strong> <blockquote> <code> <ul> <ol> <li> <div> <p> <br> <pre> <h2> <h3> <h4> <h5> <figure> <img> <figcaption> <hr>

Cancel

Leave this field blank