With this release, I’ve updated the Packer compressor from 3.1 alpha 3 to 3.1 final. The Packer compressor with spidermonkey continues to be some 20x times faster than the rhino based version, making the compressorrater all that more easy to use as a your go to javascript compressor.
Should have done this a long time ago… Instead of running the Packer compressor in the CompressorRater with Java SE 6 Scripting (aka Rhino), I’m now using SpiderMonkey… the result is a 20X speed boost for Packer! Try it yourself!
There’s a great blog post from John Resig about TraceMonkey which boosts the potential performance of JavaScript to near-native speeds in SpiderMonkey. I’m excited about the potential of JavaScript as a really high performance language!
For today’s 1.0.7 release, I also put back online the YUI (now updated to 3.0.0beta1) & ExtJS libs, and re-generated all the test results for common JS libs with Packer running native Spidermonkey.
It’s been over a year since the last update and this update is way past due!
This is just a minor release– I’ve updated the YUI compressor to the latest version (version 2.4.2 at the time of this writing) and updated the popular library examples:
and took the popular library examples offline for now:
I’ve got lots of great ideas for CompressorRater if I can find the time to work on it…
I heard a really fascinating story on NPR today. New research in the journal of neuroscience found that basically, the faster the nerve impulses can travel down the pathways in your brain, the higher your IQ is.
The article really piqued my interest as I’ve often wished I could get more things done and be more productive and pondered how I could work smarter or even be smarter on a more permanent basis… what are the limiting factors of my productivity and what are the limiting factors of my brain… ?
I find this fascinating…
My questions are:
How can we use this knowledge to increase our intelligence?
What other significant factors are there that contribute to intelligence?
Are faster processing and intelligence, in fact the same thing?
If we make the analogy with computers, a faster computer is obviously more desirable than a slow one because with faster hardware, we can run more complex rich software programs that do more things for us, and we can multitask more programs at once as well.
Indeed, faster chip speeds at a lower unit of cost (along with higher storage capacity) have been the single most important goals in chip manufacturing and computer advancement for as long as I can remember…
Logically it seems like faster processing is not equivalent to more intelligence, because a really dumb person wouldn’t come up with the same solutions as a really intelligent person, no matter how much time you gave them; or would they? Would a room full of 10 really slow people come up with an equally brilliant solution to a problem as one really smart person with 10x the intelligence?
Notice I said slow people above instead of dumb people… It seems that at some level this notion of slowness and low intelligence is actually obvious common knowledge, as the terms, “slow” and “dumb” are more or less interchangeable.
If we could somehow increase the speed of transmission of the brain signals of slow individuals, could we make them into more intelligent people?
A lot to think about for sure…
UPDATE: another article about it!
It’s been a little while since the last release of jabsorb…
This one is a fairly minor release, yet nevertheless important.
Changes:
You can download the release here:
And for general user discussion on the jabsorb library, go here:
http://groups.google.com/group/jabsorb-user
Enjoy!
The next alpha release for log4jdbc is out! Get it while it’s hot….
1. Fixed a bug with batched SQL in this release (thanks to Daniel Doubleday for reporting this)
2. Added simple getter methods for all the underlying wrapped objects.
For example, you can get the real Connection from the ConnectionSpy like this:
Connection realConnection = ((ConnectionSpy) conn).getRealConnection();
or you can get the real Statement from the StatementSpy like this:
Statement realStmt = ((StatementSpy) stmt).getRealStatement();
The simple getter methods added to log4jdbc were also added to the JDBC 4 version for consistency but please keep in mind that if you are lucky enough to be using JDBC 4, it’s best to use the more powerful Wrapper interface (which has always been fully supported in the JDBC 4 version of log4jdbc.)
I’ve been meaning to add this feature for awhile, but was prompted again by this issue raised by jrobertray.
3. Finally, I’ve added a new option for turning off SQL Statement warnings. log4jdbc has always included warnings in the logs when simple Statements were used to execute SQL. This is because a database can usually pre-compile and cache PreparedStatements much more efficiently (especially when running many many similar SQL statements with only differing bind variables.) Also, using Statements can sometimes have security implications if used improperly (binding variables is much cleaner than concatenating strings together to form your SQL!) I’ve realized that this warning might annoy some people (aka me!), so I’ve turned it off by default. You can turn it back on by setting the log4jdbc.statement.warn system property to true.
I hope you enjoy this release, and as always, please send me feedback!
I’m getting email about log4jdbc on a daily basis now. I’ve created a new google group for questions, feedback and general support. From now on, please send your general questions, feedback, feature request etc. to this new group.
Here are the essentials:
* Group name: log4jdbc
* Group home page: http://groups.google.com/group/log4jdbc
* Group email address log4jdbc@googlegroups.com
I’m also in the process of moving the project hosting to google code (It’s just so much easier than SourceForge!) There isn’t much there yet, but it will be expanding soon:
In this release, I’ve cleaned up the generated SQL a bit and added a bunch more options for controlling the SQL output. You can now turn on and off the type of SQL you want to log. For example, you might want to log only INSERT SQL statements and generate a SQL script from the logger output.
I also added an extra logger that shows whenever a new connection is opened, or a connection is closed. It also dumps all open connection numbers at each open and close event, so you can see how many connections your program uses as it progresses (great for detecting connections leaks!)
I reorganized the documentation to hopefully make things a little more clear, especially with the growing list of options.
The two most ofen requested features for log4jdbc are Maven support and DataSource support. I plan on getting these in before the 1.2 final is out. Please be patient!
For documentation and download, go to http://log4jdbc.sourceforge.net
log4jdbc is a little Java JDBC spy driver that I first open sourced about a year ago.
It can snoop on other JDBC drivers and log all the goodies going on with your database under the hood– SQL, timing info and more!
I just released the 1.1 final release today. It has some significant improvements over the 1.0 release which came out last year around this time. Most notably, it uses the SLF4J logging system (instead of log4j) so it’s much more portable as to which logging system you can use.
Hope you enjoy using it and please send me feedback if you like it (or hate it).
I’ve finally managed to find some time to work on the CompressorRater. Updates on line today:
Hope you enjoy! Feedback will be welcomed and appreciated.
