Banging my head against the wall about the type of abstract
data type to use for controling Xd builds and then it's
like, just use the DOM, retard. (yes, I often call myself
retard when I'm thinking) Why the heck should I build all
of these complex structures when it's right there in the
DOM. It's like I'm kicking and screaming my way into 1999.
I'm going to stick to the DOM over my natural attraction to
Jdom just becuase it's a cross language interface so I know
that if some day when things are ported (yeah, in your
dreams, einstein) that the APIs can match as much as
possible.
Built my first PEAR class based on HTML/Table for lists.
I'm working with the guy who did that class so I'm gonna
run it by him and see what he thinks. I just wanted to get
my hands dirty with the library matching style.
A strange thing that they're doing at work is coding there
PHP in a strict Java style. Each page builds calling main
(). The how is that by doing this the transition over to
Java will be a lot easier. I'm not sure if I'm convinced.
Type in error_reporting (E_ALL); at the top of
a page and watch the fur fly. Weak typing is a real
handicap for that kind of roll out. Still, it is very
elegant looking code.
After working with JSP, I have grown rather fond of server
side scripting with strong types. Everything that comes
along seems to be drawn to the flexibility. Not sure why.
E, Ruby... I'm kinda glad that some of the Perl 6 dev talk
hints that you might be able to force types. That would be
sweet. Getting real sick of all this if (!is_array
($foo)) {} shit.