[Grok-dev] a nice research project
sebastian at urbantalk.se
Sat Feb 7 22:25:21 EST 2009
"If it does a lot of work [...] you might need to understand a lot if
it breaks [...]"
That was the worst crap I have seen in years. Seriously, it's like
listening to someone advocating intelligent design over darwinism.
I've been involved in scalability testing on the .net platform and in
my opinion this is just amateurish at best, ignorant at worst. That
said, all angels of profiling are interesting and beneficial to follow
up, but the blog post insinuates that (with some feable reservations)
a user can draw interesting conclusions from the comparison. I think
not. It is only useful for the framework developers and the post
should be targeted at that audience.
I think the knew catch phrase should be "Lies, damn lies and blog
7 feb 2009 kl. 18.02 skrev Martijn Faassen:
> Hi there,
> I just read this:
> And I certainly don't understand that Grok is doing here.
> The sample code for instance shouldn't be using the ZPT engine at all,
> but for some reason we *do* see a lot of TAL used in the profiler
> output. I don't understand why an XML parser should be invoked either,
> except if that's ZPT again. Configuration needs XML but that should
> be invoked during startup time (I see calls to minidom) in there.
> If people would like to dig into this and see where some of these
> artifacts are coming from, perhaps we can get the list of calls for
> a simple application down.
> Grok-dev mailing list
> Grok-dev at zope.org
More information about the Grok-dev