From my A2 Host Post—September 2008 email: “A2 Hosting has removed MailScanner and ASSP spam plugins and reverted back to the SpamAssassin system used by cPanel. This update occurred from August 18th through August 21st for all of our Shared, Reseller and Semi-Dedicated servers. A2 Hosting originally had decided to use the 3rd party mail spam solutions ASSP and Mailscanner because of several problems experienced when using the default cPanel mail configuration prior to cPanel version 11. Unfortunately this caused more problems than solutions. cPanel 11 contains vastly improved spam protection features making those 3rd party solutions unnecessary. The current ASSP and MailScanner configuration icons have been removed from cPanel and replaced by the new SpamAssassin icon. If you have experienced any problems since this update, please file a ticket with the support system so that we can track and respond to your request. Thank you for your patience and understanding in this matter.”
A2 Hosting admitting they have problems with email is precisely aligned with my criticism of the service. This means that A2 Hosting and Bryan Wilhite share the same reality which is quite rare for me in the customer service world. Today I am a satisfied A2 Hosting customer (that does not use its email—I use Google Apps hooked into my domains).
arstechnica.com: “The theories behind tracing optimization were pioneered by Dr. Michael Franz and Dr. Andreas Gal, research scientists at the University of California, Irvine. The tracing mechanism records the path of execution at runtime and generates compiled code that can be used next time that a particular path is reached. This makes it possible to flatten out loops and nested method calls into a linear stream of instructions that is more conducive to conventional optimization techniques.” Much respect to Tiffany B. Brown for getting me the news.
“YUI 3: The goals are lighter, faster, consistent, power, secure”
Ajaxian.com: “Chaining: We’ve paid attention throughout the new architecture to the return values of methods and constructors, allowing for a more compressed chaining syntax in implementation code.” The next YUI has a lot of JQuery-like syntax. This could be Microsoft-style nightmare of backwards-compatibility bloat or a lean, mean, radical rewrite threatening regression-test failure. My guess is that “new architecture” means a radical rewrite.
“Firebug to get a boost”
Ajaxian.com: “Great news for all Web developers out there (that be you!). Firebug is going to get a shot in the arm. Joe Hewitt has had to slow down his work on the tool, and thus the Firebug Working Group was created, to try to make the tool continue to thrive.” Joe Hewitt has to pay his gas bill just like everyone else. But when his RSS feed dropped on me that was truly shocking.
“Captcha is broken—now what?”
Tim Anderson, The Gaurdian: “That is all very well, but the failings of Captcha impact every internet user. It is not only a matter of more spam choking inboxes. Breaking Captcha enables networks of computers to post malicious content to legitimate sites.”
“Web Development as Tag Soup”
Jeff Atwood: “The tag soup problem seems to be endemic to all modern web development stacks. … But I have to wonder: is there a better way? Is there something beyond RHTML, Views, and Templates? What examples would you point to of web development stacks that avoided degenerating into yet more hazardous, difficult to maintain tag soup? Is there anything truly better on the horizon?” In the mean time I have embraced the platform-agnostic XSLT. There is an XSLT stack for PHP, Microsoft .NET, Java and Python. That’s one flavor of tag soup for four different platforms. The numbers work for me.
“HTML 5 data- elements to store private values”
data- is a very practical solution, but people…would much prefer a more ‘pure’ solution.” This changes the “tag soup” tagline to “attribute soup”—this also violates the principle of separating data from markup. In my squalid little world, I use hidden
input elements in a conventional form to store data.