The goal of this tutorial is a simple tasklist written with clojure and compojure
Tuesday, August 31, 2010
Posted by Steve at 2:29 PM
Sunday, August 29, 2010
Thursday, August 26, 2010
For the best Java read performance, there are four things to remember:
- Minimize I/O operations by reading an array at a time, not a byte at a time. An 8Kbyte array is a good size.
- Minimize method calls by getting data an array at a time, not a byte at a time. Use array indexing to get at bytes in the array.
- Minimize thread synchronization locks if you don't need thread safety. Either make fewer method calls to a thread-safe class, or use a non-thread-safe class like
- Minimize data copying between the JVM/OS, internal buffers, and application arrays. Use
FileChannelwith memory mapping, or a direct or wrapped array
Posted by Steve at 1:51 PM
Wednesday, August 25, 2010
Sunday, August 22, 2010
js script source: http://hakim.se/experiments/html5/trail/03/js/trail.js
Posted by Steve at 5:18 PM
Uncle Bob Martin on why he thinks Clojure is so important:http://thecleancoder.blogspot.com/2010/08/why-clojure.html
Posted by Steve at 5:06 PM
Monday, August 16, 2010
In this post, we will build the core fetcher and core workers for a single machine, and introduce a new project for workers in clojure, called work.
work uses clj-http:
clj-httpis a new Clojure HTTP client library inspired by Ring and designed for simplicity, robustness, extensibility, and testability.
Posted by Steve at 3:46 PM
This is a long article with some useful comments on the history of Java and the details of the patents in dispute.http://blog.headius.com/2010/08/my-thoughts-on-oracle-v-google.html
Now we come to the biggest question of all: how does this suit affect the Java world, regardless of outcome?Well it's obviously not great to have two Java heavyweights bickering like schoolchildren, and it would be positively devastating if Android were obliterated because of this. But I think the real damage will be in how the developer community perceives Java, rather than in any lasting impact on the platform itself.Let's return to some of our facts. First off, nothing in this suit would apply to any of the three mainstream JVMs that 99% of the world's Java runs on. Hotspot and JRockit are both owned by Oracle, and J9 is subject to the Java specification's patent grant for compliant implementations. The lesson here is that Android is the first Java-like environment since Microsoft's J++ to attempt to unilaterally subset or superset the platform (with the difference in Android's case being that it doesn't claim to be a Java environment, and it may not actually need the patent grant). Other Java implementations that "follow the Rules" are in the clear, and so 99% of the world's use of Java is in the clear. Sorry, Java haters...this isn't your moment.
Posted by Steve at 10:54 AM