+ <div class="entry">
+ <div class="title"><a href="No_patch_is_not_better_than_a_useless_patch.html">No patch is not better than a useless patch</a></div>
+ <div class="date">2009-04-28 09:30</div>
+ <div class="body">
+<p>Julien Blache
+<a href="http://blog.technologeek.org/2009/04/12/214">claim that no
+patch is better than a useless patch</a>. I completely disagree, as a
+patch allow one to discuss a concrete and proposed solution, and also
+prove that the issue at hand is important enough for someone to spent
+time on fixing it. No patch do not provide any of these positive
+properties.</p>
+</div>
+ <div class="tags">
+
+
+
+ Tags: <a href="tags/debian">debian</a>, <a href="tags/english">english</a>, <a href="tags/nuug">nuug</a>.
+
+ </div>
+ </div>
+ <div class="padding"></div>
+
<div class="entry">
<div class="title"><a href="EU_parlamentet_raner_fellesskapet_for_musikk.html">EU-parlamentet raner fellesskapet for musikk</a></div>
<div class="date">2009-04-26 08:30</div>
</div>
<div class="padding"></div>
- <div class="entry">
- <div class="title"><a href="Standardize_on_protocols_and_formats__not_vendors_and_applications.html">Standardize on protocols and formats, not vendors and applications</a></div>
- <div class="date">2009-03-30 11:50</div>
- <div class="body">
-<p>Where I work at the University of Oslo, one decision stand out as a
-very good one to form a long lived computer infrastructure. It is the
-simple one, lost by many in todays computer industry: Standardize on
-open network protocols and open exchange/storage formats, not applications.
-Applications come and go, while protocols and files tend to stay, and
-thus one want to make it easy to change application and vendor, while
-avoiding conversion costs and locking users to a specific platform or
-application.</p>
-
-<p>This approach make it possible to replace the client applications
-independently of the server applications. One can even allow users to
-use several different applications as long as they handle the selected
-protocol and format. In the normal case, only one client application
-is recommended and users only get help if they choose to use this
-application, but those that want to deviate from the easy path are not
-blocked from doing so.</p>
-
-<p>It also allow us to replace the server side without forcing the
-users to replace their applications, and thus allow us to select the
-best server implementation at any moment, when scale and resouce
-requirements change.</p>
-
-<p>I strongly recommend standardizing - on open network protocols and
-open formats, but I would never recommend standardizing on a single
-application that do not use open network protocol or open formats.</p>
-</div>
- <div class="tags">
-
-
-
- Tags: <a href="tags/debian">debian</a>, <a href="tags/english">english</a>, <a href="tags/nuug">nuug</a>, <a href="tags/standard">standard</a>.
-
- </div>
- </div>
- <div class="padding"></div>
-
<p style="text-align: right;"><a href="index.rss"><img src="xml.gif" alt="RSS feed" width="36" height="14"></a></p>
<div id="sidebar">
<li><a href="archive/2009/03/">March (12)</a></li>
-<li><a href="archive/2009/04/">April (9)</a></li>
+<li><a href="archive/2009/04/">April (10)</a></li>
</ul></li>
<li><a href="tags/aros">aros (1)</a></li>
- <li><a href="tags/debian">debian (6)</a></li>
+ <li><a href="tags/debian">debian (7)</a></li>
<li><a href="tags/debian edu">debian edu (6)</a></li>
- <li><a href="tags/english">english (10)</a></li>
+ <li><a href="tags/english">english (11)</a></li>
<li><a href="tags/fiksgatami">fiksgatami (1)</a></li>
<li><a href="tags/norsk">norsk (39)</a></li>
- <li><a href="tags/nuug">nuug (38)</a></li>
+ <li><a href="tags/nuug">nuug (39)</a></li>
<li><a href="tags/opphavsrett">opphavsrett (3)</a></li>
projects / homepage.git / blobdiff