<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="0.92" xml:base="http://willy.boerland.com/myblog">
<channel>
 <title>Willy Dobbe - Comments</title>
 <link>http://willy.boerland.com/myblog</link>
 <description>Comments</description>
 <language>en</language>
<item>
 <title>dank, waterresevoir maar niet een standaard</title>
 <link>http://willy.boerland.com/myblog/raar_artifact_middenduin_maar_wat_is_het#comment-8707</link>
 <description>laatste zinnen pagina 2 van &lt;a href=&quot;http://www.ivn.nl/docs/200909232334012003.pdf&quot;&gt;pdf&lt;/a&gt;

&quot;Bijna aan het eind van de wandeling, nog op het hoge duin, zie je de  betonnen rand van het oude waterreservoir. Vanwege een gehandicapt kind op Duinlust was  er een hydraulische lift aangelegd, die werkte op waterdruk. Het water werd via een pompstationnetje uit de Zanderijvaart gepompt in het resevoir gepompt&quot;

dank aan &lt;a href=&quot;https://twitter.com/hendrikje01/status/288393952544043009&quot;&gt;hendrikje01&lt;/a&gt;.

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Mon, 07 Jan 2013 21:24:43 +0000</pubDate>
</item>
<item>
 <title>watertoren</title>
 <link>http://willy.boerland.com/myblog/raar_artifact_middenduin_maar_wat_is_het#comment-8706</link>
 <description>is het de fundering van een watertoren? &lt;a href=&quot;http://www.natuurwegwijzer.nl/routes/middenduin--kamperberg/10060000_000110&quot;&gt;natuurwegwijzer&lt;/a&gt;.

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Mon, 07 Jan 2013 19:42:49 +0000</pubDate>
</item>
<item>
 <title>update</title>
 <link>http://willy.boerland.com/myblog/extract_a_video_from_an_apple_keynote_file#comment-8705</link>
 <description>via mail the following tip, much easier:

Highlight the movie file.
Then, in the Inspector, locate the metrics tab (the one with the ruler) and you ought to see the file named.
Then, drag that movie icon with the file name to the desktop. You have the movie.

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Mon, 31 Dec 2012 14:53:11 +0000</pubDate>
</item>
<item>
 <title>see smarthings</title>
 <link>http://willy.boerland.com/myblog/drupal_as_a_home_service_bus_beyond_home_automation#comment-8704</link>
 <description>after &quot;the internet of things&quot; see this smarthings

&lt;a href=&quot;http://www.kickstarter.com/projects/smartthings/smartthings-make-your-world-smarter&quot;&gt;at kickstarter&lt;/a&gt;.

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Tue, 04 Dec 2012 10:37:56 +0000</pubDate>
</item>
<item>
 <title>every time when Drupal</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8700</link>
 <description>every time when Drupal release a new major verison, developers have to re-learn it and customer as well. Drupal should try to shorten it&#039;s development time and focus on less mission with every release. (either focus on UI / Code changes.)</description>
 <pubDate>Fri, 19 Oct 2012 14:56:27 +0000</pubDate>
</item>
<item>
 <title>Blessing/curse of bloated core</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8699</link>
 <description>With all the hoopla over Drupal core becoming bloated recently, there is an upside that figures into this equation.  As core begins to handle more and more of the heavy lifting (entities, views, mobile theming, wysiwyg etc.) modules can become lighter and faster to retool.  This streamlines and enhances the module development cycle, thereby allowing a faster transition to newer versions.  People tend to forget that the biggest delays in Drupal 7 centered around critical add-on modules, not core itself.  I&#039;m actually looking forward to a far more robust Drupal 8 that takes care of many of the modern issues that have previously been addressed by the module community.</description>
 <pubDate>Fri, 19 Oct 2012 13:32:11 +0000</pubDate>
</item>
<item>
 <title>Understand the breadth of</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8698</link>
 <description>Understand the breadth of change in the framework and you&#039;ll find that the current cycle is necessary and well measured. This might be an issue for some who will migrate away from Drupal and onto another CMS. Surprisingly, no wars will break out and no children will starve because of this. </description>
 <pubDate>Fri, 19 Oct 2012 13:25:57 +0000</pubDate>
</item>
<item>
 <title>The time is right</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8697</link>
 <description>Bert,

As you know, I&#039;ve been a longtime user and observer of Drupal. We&#039;ve heard for a very long time people complaining that there is no backward compatibility between the Drupal release, but until now there hasn&#039;t been a very compelling argument to change the Drupal culture. I think you hit it right on the head though that times have changed due to SaaS and also with what the ecosystem at large is doing.

Also, by providing backward compatibility you also provide additional incentive for site owners to upgrade much more quickly to the latest version of Drupal. I still have a few D6 sites that I&#039;m reluctant to move over to D7. When D7 came around there were few contributed modules available that I needed and now that it&#039;s been so long since I&#039;ve looked at the D6:D7 variances, I&#039;ve lost some of my D6 to D7 mojo (and quite frankly don&#039;t have the time). To go with your battle cry for shorter release cyles, I would argue that D9 should focus on one change and only one change...the architecture and API system changes required to provide backward compatibility. 

</description>
 <pubDate>Fri, 19 Oct 2012 13:24:57 +0000</pubDate>
</item>
<item>
 <title>Old jQuery versions could be</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8696</link>
 <description>Old jQuery versions could be a thing of the past once 8.x is out: http://drupal.org/node/1787222</description>
 <pubDate>Fri, 19 Oct 2012 13:17:48 +0000</pubDate>
</item>
<item>
 <title>The problem is not only the</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8695</link>
 <description>The problem is not only the recycle time, but also the &#039;smoothness&#039; to upgrade from one version to another. Upgrading is a real PITA, considering the many problems. You have practically start over with a website when a new major comes (a little bit overreacting, but you get the point). </description>
 <pubDate>Fri, 19 Oct 2012 13:05:21 +0000</pubDate>
</item>
<item>
 <title>Bert, almost a year ago I</title>
 <link>http://willy.boerland.com/myblog/drupal_release_cycles_time_will_tell#comment-8694</link>
 <description>Bert, almost a year ago I wrote something very similar, http://steveburge.com/blog/general-cms-issues/no-upgrades/

That post isn&#039;t nearly as detailed as yours, but the key point is the same: times have changed.

5 years ago no-one expected software to update smoothly from version to version. Now users don&#039;t expect anything less.
</description>
 <pubDate>Fri, 19 Oct 2012 12:28:49 +0000</pubDate>
</item>
<item>
 <title>Thank you for the thought-provoking post, Bert!</title>
 <link>http://willy.boerland.com/myblog/blue_piles_of_shit_on_the_horizon#comment-8690</link>
 <description>I can see exactly where you&#039;re coming from and pretty much agree with the points you are making. My experience with the Drupal community over the years has made me feel my voice is less and less heard. It&#039;s ok, I don&#039;t have that much to say, and there are some really clever people in the community who are fighting to be heard.

So I&#039;ve retreated and become more of a listener. When I can be bothered. And there still is good stuff to be heard and discussed amongst ourselves.

My real disappointment happens when I&#039;m told how to behave. It&#039;s a personal thing. I&#039;m not far off a half century. And let me be clear, it&#039;s never been Bert telling me to do so. It&#039;s just that Bert, having brought up the subject of community and where the &#039;community&#039; is going wrong - and also that he opened up the comments on his blog - I thought I&#039;d mention this.

To summarise - my malaise with the Drupal community comes from the community telling me how I&#039;m supposed to behave.</description>
 <pubDate>Fri, 17 Aug 2012 14:00:37 +0000</pubDate>
</item>
<item>
 <title>see also</title>
 <link>http://willy.boerland.com/myblog/the_myth_of_the_drupal_leanring_curve#comment-8689</link>
 <description>wanted to use this one as well, see this mindmap
&lt;a href=&quot;http://drupal.org/node/1282788?size=_original&quot;&gt;http://drupal.org/node/1282788?size=_original&lt;/a&gt;
--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Fri, 21 Oct 2011 20:54:54 +0000</pubDate>
</item>
<item>
 <title>twitetr</title>
 <link>http://willy.boerland.com/myblog/leuk_verjaardags_kado_typo_domain_van_dop_collega_sebastiaan_meijer#comment-8688</link>
 <description>en natuurlijk &lt;a href=&quot;http://twitter.com/#!/bertboerladn&quot;&gt;http://twitter.com/#!/bertboerladn&lt;/a&gt;

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Thu, 30 Dec 2010 12:03:27 +0000</pubDate>
</item>
<item>
 <title>5star?</title>
 <link>http://willy.boerland.com/myblog/dopcast_episode_1_rate_this_module#comment-8686</link>
 <description>and yes, this site uses 5star :-)

--&lt;br /&gt;groets, bert boerland&lt;p /&gt;</description>
 <pubDate>Mon, 08 Nov 2010 13:44:45 +0000</pubDate>
</item>
</channel>
</rss>
