/usr/share/php/tests/Horde_Feed/Horde/Feed/fixtures/lexicon/http-phplens.com-phpeverywhere-%2Fq=node-feed-1 is in php-horde-feed 2.0.1-4.
This file is owned by root:root, with mode 0o644.
The actual contents of the file can be viewed below.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 | <?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://phplens.com/phpeverywhere">
<channel>
<title>PHP Everywhere - By John Lim</title>
<link>http://phplens.com/phpeverywhere</link>
<description></description>
<language>en</language>
<item>
<title>Perception is 99% of reality</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/251</link>
<description><p>Jeff Atwood <a href=http://www.codinghorror.com/blog/archives/001058.html>writes</a>:
<blockquote>
If you've used Windows Vista, you've probably noticed that Vista's file copy performance is noticeably worse than Windows XP. I know it's one of the first things I noticed. Here's the irony-- Vista's file copy is based on an improved algorithm and actually performs better in most cases than XP. So how come it seems so darn slow?
</blockquote>
<p>PS: Jeff adds that Vista SP1 has switched back to XP's algorithm. Duhh!</description>
<pubDate>Fri, 07 Mar 2008 19:53:44 -0500</pubDate></item>
<item>
<title>Octalpussy</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/250</link>
<description><p>In my previous post I asked what would be the output of of the following numbers:
<pre>
echo 09," => (09) &lt;br>";
echo 9," => (9) &lt;br>";
</pre>
<p>The answer is:
<pre>
0 => (09)
9 => (9)
</pre>
<p>
That's because any number preceded by 0 is treated as an octal number, and 9 is an invalid octal number. Octal numbers are base 8, e.g.:
<table border=1>
<tr><td>Octal Value<td>Decimal Value
<tr><td>1<td>1
<tr><td>2<td>2
<tr><td>3<td>3
<tr><td>4<td>4
<tr><td>5<td>5
<tr><td>6<td>6
<tr><td>7<td>7
<tr><td>10<td>8
<tr><td>11<td>9
</table>
<p>&nbsp;
<p>The silly thing is that hardly anyone uses octal nowadays, but it continues to be part of the C, C++, Java and PHP standards. The mistake is also <a href=http://mindprod.com/jgloss/octal.html>very common</a>. C-style languages pride themselves in their terse and minimalist syntax, but this is one scenario where a language design error was probably made. Perhaps 0c should have been used to represent octal in analogy to 0x for hexadecimal, but this suggestion is sadly 35 years too late. 0 for octal is too deeply imprinted in modern compiler DNA.
<p>PS: Here's the <a href=http://phplens.com/lens/lensforum/msgs.php?id=17245>mistaken ADOdb bug report</a> that started it.</description>
<pubDate>Sun, 03 Feb 2008 11:24:06 -0500</pubDate></item>
<item>
<title>Octopussy numbers in PHP</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/249</link>
<description><p>Someone reported a bug in ADOdb, the open source db library i maintain. I went crazy for half an hour until i realised the problem. Here's a little gotcha you can try:
<pre>
echo 09," => (09) &lt;br>";
echo 9," => (9) &lt;br>";
</pre>
<p>If you expect the above code to produce the same values, you are sadly mistaken. Try it. Also see the <a href=http://phplens.com/phpeverywhere/?q=node/view/250>followup</a>.</description>
<pubDate>Sun, 03 Feb 2008 10:59:24 -0500</pubDate></item>
<item>
<title>Code's Worse Enemy</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/247</link>
<description><p>
Steve Yegge talks about choosing the right programming language in the face of <a href=http://steve-yegge.blogspot.com/2007/12/codes-worst-enemy.html>Code's Worse Enemy</a>:
<p>
<blockquote>
I'll give you the capsule synopsis, the one-sentence summary of the learnings I had from the Bad Thing that happened to me while writing my game in Java: if you begin with the assumption that you need to shrink your code base, you will eventually be forced to conclude that you cannot continue to use Java. Conversely, if you begin with the assumption that you must use Java, then you will eventually be forced to conclude that you will have millions of lines of code.
</blockquote>
<p>
There's a lot of truth in what he says. You can't fault his taste: He prefers Mozilla Rhino, a Javascript/Ecmascript implementation.
<p>
When we coded in ASP, we were a JScript shop. When we were looking for something that ran cross-platform, the closest thing that fit the bill was PHP. Javascript with perl-style $variables. Neither language is perfect. But good enough - or as some prefer to put it: <a href=http://en.wikipedia.org/wiki/Worse_is_better>worse is better</a>.</description>
<pubDate>Sun, 06 Jan 2008 04:45:57 -0500</pubDate></item>
<item>
<title>Why Should PHP ever be taught in school?</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/244</link>
<description><p>Happy New Year Folks! Let's keep on blogging.
<p>This posting by Ka-Ping Yee on <a href=http://zestyping.livejournal.com/124503.html>why PHP should never be taught</a> is precisely why PHP should be taught. If something is popular but hard to understand then we need an education process. To just shake our heads and give up is simply immature (or trolling). Otherwise we might as well say that English (or any other spoken language for that matter) should not be taught, because spoken languages are illogical, imprecise and therefore ... useless :)
<p>Most programming languages have similar gotchas. Oracle's PL/SQL has "" being equivalent to null. Javascript believes that 0 and "" are equivalent. C has non-zero being equivalent to boolean true. Lisp's gotcha begins with ( and ends with ) -- (just a joke). Java's gotcha begins with J2EE and the obsolete baggage that comes with it.
<p>PS: The confusion is because === is the real equality operator and should be used here. In PHP, == is equality after typecasting, where 0 == "0" and "" == "0" evaluating to true are accepted conventions. They are useful constructs in many situations in a similar vein to C's convention of 0 being boolean true and non-zero being boolean false, which the critics cleverly ignore. See the <a href=http://www.php.net/manual/en/types.comparisons.php>PHP Manual on type comparisons</a></description>
<pubDate>Tue, 01 Jan 2008 09:04:43 -0500</pubDate></item>
<item>
<title>Web cluster redundancy with mod_backhand revisited</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/243</link>
<description><p>In my <a href=http://phplens.com/phpeverywhere/?q=node/view/241>last blog entry on mod_backhand</a>, I mentioned that you could implement redundancy in a web cluster by having multiple load balancers and using <a href=http://en.wikipedia.org/wiki/Round_robin_DNS>round robin DNS</a> pointing to the load balancers. This technique is mentioned in the mod_backhand presentation notes by Theo Schlossnagle, one of the author's of mod_backhand.
<p>But if you think about it carefully, in my opinion, this solution doesn't really work well:
<ul>
<li>Round robin DNS systems simply return a list of IP addresses (sorted randomly) that resolve that domain name. Most DNS servers do not perform checks to detect if any of the IP addresses are down. So clients will get the IP addresses of load balancers that are down too. The DNS client normally just picks the first IP address in the list to use - and it could be the IP address of a load balancer that is down.
<li>Secondly, when a client resolves the domain name, this IP address is cached on the client. So a failure in one of the load balancers would still mean that all web browsers that previously connected to that load balancer successfully because of DNS caching would be unable to access the system for quite a long time (e,g. 10-15 minutes).
</ul>
<p>I can think of several solutions, but the best one as far as I can see (if you still want to use mod_backhand of course) is to run mod_backhand on a high availability hardware solution (or if a few minutes downtime is acceptable, keep a spare box configured with mod_backhand around to swap with any balancer that goes down), and not push the hard problem of high availability and redundancy to DNS.
<p>Ahmad Amran Kapi from Melaka, Malaysia, points out that you can use <a href=http://www.backhand.org/wackamole/>Wackamole</a>:
<blockquote>
Wackamole is an application that helps with making a cluster highly available. It manages a bunch of virtual IPs, that should be available to the outside world at all times. Wackamole ensures that a single machine within a cluster is listening on each virtual IP address that Wackamole manages. If it discovers that particular machines within the cluster are not alive, it will almost immediately ensure that other machines acquire these public IPs. At no time will more than one machine listen on any virtual IP. Wackamole also works toward achieving a balanced distribution of number IPs on the machine within the cluster it manages.
</blockquote></description>
<pubDate>Wed, 26 Dec 2007 05:57:40 -0500</pubDate></item>
<item>
<title>Back and Backing Backhand on top of that!</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/241</link>
<description><p>Since I got married last year, I haven't had much motivation to blog. The good news is that since the previous year, I've accumulated a list of accomplishments and experiences that i feel are worthwhile sharing.
<p>
Recently, my company implemented our first <a href=http://backhand.org/>mod_backhand</a> implementation. Mod_backhand is a load-balancing and clustering solution that runs on Apache. Let's say you have 3 web servers that you need to load balance in a cluster. When a server goes down, it will auto-detect that server is down and route subsequent http requests to other servers. You can buy a load-balancing box such as Cisco Redirector, or roll your own package using Linux, Apache 1.3 and mod_backhand.
<p>
The mod_backhand load balancer is basically a Linux system with Apache 1.3 (httpds) with the mod_backhand patches installed. The load-balancer also supports redirects and https. Load balancing uses the Apache virtual directory mechanism, so you can configure different load balancing behaviour for different applications on a directory basis.
<p>
The nice thing about mod_backhand is that it autodetects servers going up and down in the cluster, with no additional configuration required. All web servers in the cluster need to broadcast that they are alive and available on the cluster at regular intervals. So if you want to add another web server to the cluster, you just need to install the backhand broadcasting service and start it on the server, and the load balancer will pick it up. CPU and load information is also broadcast to the load balancer, so the load balancer can make an intelligent guess as to which web server to pass the http request to.
<p>
There are some issues that you need to be aware of:
<ul>
<li>No support of https on the internal network. Communications between the web browser and load-balancer can use https but not between load-balancer and web server. So if you have confidential information and you don't trust your internal network, you need to setup another layer of encryption on top of that (e.g. SSH tunnel). That's what we did for our login system.
<li>The load balancer, like any other system in the network, becomes another point of failure. If you want total redundancy, one method is to have multiple mod_backhand load balancers, and round-robin DNS the load balancers.
<li>AFAIK, automatic failover to another server of a http request if the 1st web server goes down is not supported.
<li>There is Windows support (for the web servers in the cluster, not as a load-balancer) thanks to Rob Butler, but you currently need Visual C++ expertise as the binary "NT Backhand Broadcaster" doesn't work out of the box anymore with mod_backhand. There are patches in CVS but no existing binary download. As a service to the community, I have compiled my own: <a href=http://phplens.com/lens/dl/ntbhb-john-21-Dec-07.zip>NT Backhand Broadcaster</a>.
<li>Keep-Alives reduce the availability of the load balancer, as web clients can lock a mod_backhand process for unreasonable amounts of time. You need to change your Keep-Alives on to a low value (eg. 1 second), and if possible, move your static HTML and images to the load balancer (which is just Apache after all).
<li>Your web page URLs need to be relative URLs of course. The one exception is https, which needs to use the address of the load-balancer.
</ul>
<p><b>Additional Windows Notes</b>
The Windows Registry settings for Backhand Broadcaster are a bit obscure. Here is a sample config:
<p>
<pre>
HKEY_LOCAL_MACHINE\SOFTWARE\CerebraSoft]
[HKEY_LOCAL_MACHINE\SOFTWARE\CerebraSoft\Backhand_Broadcast]
"Arriba"=dword:28213950
"numCPU"=dword:00000002
[HKEY_LOCAL_MACHINE\SOFTWARE\CerebraSoft\Backhand_Broadcast\BroadcastParams]
"HostName"="Windows Server 1 BHB"
"ContactIP"="192.168.0.121"
"SendIP"="192.168.0.255"
"SendPort"=dword:0000115d
"ContactPort"=dword:00000050
"SendTTL"=dword:00000001
</pre>
<p>The ContactIP is the IP address of my Windows server running BHB: 192.168.0.121
The SendIP is the broadcast IP for the subnet (not the IP address of the load-balancer).
<p>Sometimes the first time you run NT Backhand Broadcaster, it will fail to calculate Arriba (a benchmark measuring the power of your server) and just die. You need to manually enter the Arriba value yourself in the registry. Just use the above example value if you aren't sure what to do.
<p>The load-balancer provides a page to check out the status of all servers in the cluster, typically http://load-balancing-server/backhand/
<p>Lastly, if you still cannot get it working, check out the Windows Event Log (Applications), as errors and status messages are logged there.</description>
<pubDate>Fri, 21 Dec 2007 04:22:11 -0500</pubDate></item>
<item>
<title>Bye Bye PHP4</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/240</link>
<description><p>Matt of WordPress fame gives his <a href=http://photomatt.net/2007/07/13/on-php/>opinion on PHP4 and the transition to PHP5</a>. As he says:
<p>
<blockquote>
None of the most requested features for WordPress would be any easier (or harder) if they were written for PHP 4 or 5 or Python. They’d just be different. The hard part usually has little to do with the underlying server-side language.
</blockquote>
<p>
Very true. Most of our code continues to run fine on both PHP 4 and 5, with hardly any checking of PHP_VERSION. Migrating from PHP4 to PHP5 has been relatively painless (each time we port an application, we spend at most half a day fixing warnings that didn't appear in PHP4).
<p>
Matt asks why the takeup of PHP5 been so low, and is quite disparaging to the PHP internals devs. I don't see it in such black and white terms. PHP5 never had a feature that was must-have or to-die-for. In fact, if you look at PHP's recent changes, most of them are performance improvements, or fixing past mistakes (adding proper date support for example in 5.2.1), or feature tweaks (iterators, etc). Given that most PHP4 developers have found workarounds to things fixed in PHP5, migrating to PHP5 is probably a low priority.
<p>
Also some fixes in PHP5 can cause serious problems. For example, In PHP 5.2.0, time-zone calculations started to support epochs, which are time-changing events. Now my timezone was +7.30 GMT until 1980, when we got a new Prime Minister who decreed that the country would combine its 2 time-zones to 1, so Malaysia standardised on +8.00 GMT. A timestamp such as "12.10am Nov 12, 1979 MYT" in PHP 5.1 would be displayed as "11.40pm Nov 11, 1979 MYT" in PHP 5.2.
<p>
On a more optimistic note, as long as the market share of PHP remains strong, I think the take-up rate of PHP6 will probably be higher than PHP5 in the non-English world, simply because managing multi-lingual and sites that don't use ASCII for their native script is much easier in Unicode. Now that's a compelling reason!</description>
<pubDate>Mon, 23 Jul 2007 08:22:52 -0400</pubDate></item>
<item>
<title>A big Pfutt to Windows Vista</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/239</link>
<description><p>Peter Gutmans, a noted security expert talks about <a href=http://www.cs.auckland.ac.nz/~pgut001/pubs/vista_cost.html>Windows Vista Content Protection</a>. Quite disturbing and saddening. I'm about to buy a notebook for my mum, and all the one's I'm looking at have Vista preinstalled. Pfutt.
<blockquote>
<p>Beyond the obvious playback-quality implications of deliberately degraded output, this measure can have serious repercussions in applications where high-quality reproduction of content is vital. Vista's content-protection means that video images of premium content can be subtly altered, and there's no safe way around this — Vista will silently modify displayed content under certain (almost impossible-to-predict in advance) situations discernable only to Vista's built-in content-protection subsystem.
</blockquote></description>
<pubDate>Thu, 22 Feb 2007 00:18:43 -0500</pubDate></item>
<item>
<title>Stefan Esser ruminates on PHP Security</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/238</link>
<description><p>Stefan Esser, one of the foremost PHP security gurus in the world is <a href=http://www.securityfocus.com/columnists/432>interviewed in Security Focus</a>. He's also well known for disagreeing with the PHP Group (that oversees PHP Core development) about the way PHP security issues are treated. Disturbing in more ways than one.</description>
<pubDate>Wed, 07 Feb 2007 21:31:09 -0500</pubDate></item>
<item>
<title>The Shape of Future Processors?</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/237</link>
<description><p>I read this article on CPU trends <a href=http://www.hpcwire.com/hpc/1209133.html>Converging Design Features in CPUs and GPUs</a>. Matthew Papakipos writes:
<blockquote>
<p>Where are both CPU and GPU designs converging?
<li>
<li> Both processors will be massively multi-core –- think hundreds of cores -- within a five-year period.
<li> Both processors will have complex memory hierarchies, with programmer managed core-local memories and core-local hardware-managed cache. (My own belief is that hardware-managed cache will decrease substantially in importance.)
<li> Memories will be strongly non-uniform with significant latency and throughput differences between local and non-local memory.
<li> Accelerators that can offer substantial speedups for specific tasks, either integrated on-chip or available via a HyperTransport-type interconnect, will be ubiquitous.
</ol>
</blockquote>
<p>I'm more interested in modern CPUs trends and their relation to PHP, and not GPUs. Here are some of my thoughts:
<p>Well PHP running in pre-fork mode on Apache or FastCGI on IIS/Apache should have no problems handling massively multi-core architectures, assuming the cores are uniform in design.
<p>As to complex memory hierarchies, we already have to handle the different latencies in <i>harddisk -> harddisk cache -> cpu data/instruction caches</i>. We always had the option of caching data on a hard disk or RAM disk, and some PHP Accelerators already give you the option of caching data in shared memory -- I just see it as more of the same for PHP developers. Things get more interesting for PHP compiler and opcode cache designers as they will have more options for caching PHP opcodes and data.
<p>What is interesting is the possibility of hardware acceleration of PHP. To me, it's not likely that any CPU vendor will come up with a hardware accelerator for PHP, but a CPU accelerator for .NET or java opcodes is a strong possibility. Thus in the long run, .NET or java compilers for PHP (and Python and Perl) could become mainstream.
<p></description>
<pubDate>Mon, 22 Jan 2007 01:50:25 -0500</pubDate></item>
<item>
<title>My experience moving to PHP5</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/235</link>
<description><p>
In August of this year, we decided to move from PHP4 to PHP5 for all our future PHP development. The transition was relatively painless, as the core libraries we use (<a href=http://adodb.sourceforge.net/>ADOdb</a>, <a href=http://phplens.com/>PHPLens</a>, some <a href=http://pear.php.net/>PEAR</a> modules) are already PHP5 compliant and have been for some time. What's nice about PHP5 is that it caught some errors that have been lingering in our code: PHP5 no longer allows a function to be defined twice, and some basic variable referencing errors that we missed previously.
<p>
We have ported our key web applications over to run on PHP5, but for some key customers with extremely large PHP4 code bases, we felt it was safer to keep them running on PHP4 for the time being as the cost of migration would be high; and we weren't sure whether it was worth it as the customers seem to be happy with PHP4's current performance.
<p>
Other things that we have changed is that we have transitioned to using XMLHttpRequest for all our Ajax calls. Formerly we were using the excellent <a href=http://www.ashleyit.com/rs>JSRS library</a>, but I can already see most programmers we hire in the future will be more familiar with XMLHttpRequest than JSRS. The nice thing about using XMLHttpRequest is that all XMLHttpRequests can be debugged using the excellent <a href=http://addons.mozilla.org/firefox/1843/>Firebug</a>, a Firefox/Mozilla extension that is extremely useful for Javascript debugging.
<p>
I admit we are still retrograde when it comes to exploiting PHP5's new functionality. Last month, we had to do a presentation so we moved our PHP5 web application to a notebook. Later I found out that notebook only had PHP4 installed. The web application worked flawlessly.
<p>
<img src=http://phplens.com/phpeverywhere/icons/bet9mil.gif></description>
<pubDate>Sun, 03 Dec 2006 00:50:47 -0500</pubDate></item>
<item>
<title>In praise of Zend Core</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/234</link>
<description><p>
Hi I'm back. Been busy. I will try to relate some of my experiences in the last few months in later blogs.
<p>
I'd like to point out that one of the greatest services to the PHP community that Zend is providing is the free <a href=http://www.zend.com/products/zend_core/zend_core_for_oracle>Zend Core for Oracle</a> and <a href=http://www.zend.com/products/zend_core/zend_core_for_ibm>Zend Core for DB2</a>. The latest versions install PHP 5.1.6. The little known secret is that these 2 installers are perfect for MySQL as the mysql and mysqli extensions are included in the release.
<p>
Zend Core is the installer I would recommend to setup PHP in a Windows IIS environment because it has support for FastCGI with IIS. FastCGI is the only scalable and safe way of running PHP on IIS, because not all PHP extensions are thread-safe and there are global locks in multi-threaded mode that hurt PHP performance if don't use FastCGI.
<p>
The only minuses is that Zend Core currently doesn't include the postgresql extension, and you have to compile in extensions which are not included in the release.
<p>
<img src=http://phplens.com/phpeverywhere/icons/jayne.gif></description>
<pubDate>Tue, 28 Nov 2006 12:53:17 -0500</pubDate></item>
<item>
<title>New Improved Yummy ADOdb Session Handler</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/233</link>
<description><p><a href=http://adodb.sourceforge.net/>ADOdb</a>, the database library i maintain, has had support for storing session data in a database for a long time. However there was one limitation that always continued to bug me: the fact that all the PHP servers using database-backed sessions needed to synchronize their times to ensure that the session timers worked properly.
<p>Well in the latest version of ADOdb (4.91), released a few days ago, we have the new Session2 implementation. This time, we always use the database server clock to keep track of times. We no longer rely on the PHP app servers to set the session timers, so even if the clocks of these app servers are out of synch, sessions are not affected. This change required us to change the database table format used, but that is a small price to pay for the added flexibility. You can read more in the <a href=http://phplens.com/lens/adodb/docs-session.htm>ADOdb session docs</a>.
<p>
Usage is really simple:
<pre>
include_once("adodb/session/adodb-session2.php");
ADOdb_Session::config($driver='mysql', $host, $user, $password, $database,$options=false);
session_start();
</pre>
<p>
<img src=http://phplens.com/phpeverywhere/icons/57.gif></description>
<pubDate>Fri, 04 Aug 2006 00:00:11 -0400</pubDate></item>
<item>
<title>Partitioned Iteration in Enterprise Frameworks</title>
<link>http://phplens.com/phpeverywhere/?q=node/view/232</link>
<description><p>Just heard that Bill Gates is retiring from Microsoft. I guess he's achieved every possible goal he had, and it's downhill from here ;-)
<p>
I always enjoy reading Roger Sessions work on designing scalable software infrastructure. He's a Java framework expert who has become a .NET advocate. Roger has written a very interesting white paper on <a href=http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnbda/html/sessfin00.asp>A Better Path to Enterprise Architectures</a>. It's a rehash of the <a href=http://en.wikipedia.org/wiki/KISS_Principle>KISS principle</a> and small is beautiful, taken from a software designer's perspective.
<p>
If that sounds pretty dull to you, read the fighter pilot analogy Roger brings up, where he talks about Mig-15 and F-86 dogfights. Stirring stuff.</description>
<pubDate>Fri, 16 Jun 2006 07:25:20 -0400</pubDate></item>
</channel>
</rss>
|