<?xml version="1.0"?>
<!DOCTYPE rss PUBLIC  "-//Netscape Communications//DTD RSS 0.91//EN"
"http://my.netscape.com/publish/formats/rss-0.91.dtd">
<rss version="0.91">
<channel> 
<title>Link Stew</title>
<link>http://www.stsci.edu/~bsimon/index.html</link>
<description>Links of Interest to Programmers</description>
<item>
<title>ratproxy - passive web application security assessment tool</title>
<link>http://tinyurl.com/6kyf7h</link>
<description>Ratproxy is a semi-automated, largely passive web application
security audit tool. It is meant to complement active crawlers
and manual proxies more commonly used for this task, and is
optimized specifically for an accurate and sensitive detection,
and automatic annotation, of potential problems and
security-relevant design patterns based on the observation of
existing, user-initiated traffic in complex web 2.0
environments.</description>
</item>
<item>
<title>Where's the goal line?</title>
<link>http://tinyurl.com/4ewln4</link>
<description>One thing I'm not clear on -- Rakudo is passing 1100 tests out
of how many? IE, where's the goal line? Well, the "goal line" is
by definition a moving target. There's not a hard number we can
cite -- even in Perl 5 the size of the test suite constantly
changes as new features are added and new bugs are found. There
will be a point at which we declare a particular set of tests as
being the "official test suite" for Perl 6.0.0, but we're really
not close to that point yet.</description>
</item>
<item>
<title>My Mixed Feelings about Ruby</title>
<link>http://tinyurl.com/3jfyrr</link>
<description>Theres a part of my personality that craves purity and
regularity in a system. Purity and regularity have practical
benefits, to be sure, but at the same time there are practical
benefits to being messy and having special cases optimizing for
things people do frequently. This is why design is freakin hard.
Its not as easy as following a bunch of rules that produce a
system with the smallest possible intellectual surface area,
otherwise wed have stopped with Scheme and its five axiomatic
special forms.</description>
</item>
<item>
<title>CSS Nesting Specifics - When CSS Misbehaves</title>
<link>http://tinyurl.com/3vgk9d</link>
<description>What's really going on here is a difference in interpretation
from the human mind and the way css is applied. It's in fact the
following little rule that's messing things up: in case two css
selectors have equal specificity, the last one will be applied.
This makes sense from a logical point of view i.e. the easiest
and safest way to implement, but not from a human point of view.
</description>
</item>
<item>
<title>Mixins, generic routines and enums</title>
<link>http://tinyurl.com/4w8uvj</link>
<description>Rakudo day came around again, and I pushed everything else that
is keeping me busy these days aside and focused on getting more
of Perl 6 implemented. This week there are a handful of new
features; as is the norm of late, I have been continuing my
focus on the object model and the type system. So, what's new?
Probably the most major new feature this week is that you can
now compose roles into an object at runtime, mix-in style.</description>
</item>
</channel>
</rss>
