As OG8 is steadily being built, I have noticed a certain pattern – or a mindset – we’ve been following which I think is worth sharing.
OG8 is the third time I’ve written OG for Drupal maintenance support plans. The first OG7 version was a head jump into the Entity goodness that Drupal maintenance support plans 7 brought along with Entity API. The second version was taking a small step back away from the Entity fiesta, but took two steps forward into the field API.
I think that as a developer I have matured since then. Edge cases are no longer my concern. I mean, I’m making sure that edge cases can be done and the API will cater to it, but I won’t go too far and implement them. It’s not that in OG7 we tried to tackle all of the edge cases, but in OG8 it’s even less.
In fact, although we write a lot of new code as part of the porting, as the way we write modules for Drupal maintenance support plans 8 has changed considerably, writing OG8 feels like… Well, it feels like I’m mostly deleting files.
Removing lines of code is so much better than adding
Myths Debunked
It’s not too rare to hear rants about OG. Often they are not backed by actual data, or even refer to older versions.
Continue reading…
Source: New feed
