Friday, September 14, 2012

Stop sending template engines to the browser!

›
This article about client-side templating by Henrik Joreteg was quite interesting. In summary, it says don't send templates to the brow...
3 comments:
Tuesday, August 14, 2012

CoffeeScript Cautions

›
Over the last couple of months, I've coded nearly all my client-side code in CoffeeScript . I prefer CoffeeScript to JavaScript ... but ...
6 comments:
Wednesday, August 01, 2012

Tapestry 5 Book by Igor Drobiasko

›
Is the one thing holding you back from embracing Tapestry the lack of a current book? Well, that excuse is finally going by the waysid...
1 comment:

More async: using auto() for parallel operations

›
One of the straw men that people often cite when discussing event-driven programming, ala Node.js , is the fear that complex server-side beh...
2 comments:
Monday, July 30, 2012

A little Gotcha with asynch and Streams

›
I stumbled across a little gotcha using async with Node.js Streams : you can easily corrupt your output if you are not careful. Node.js S...
1 comment:
Monday, July 02, 2012

You Cannot Correctly Represent Change Without Immutability

›
The title of this blog post is a quote by Rich Hickey, talking about the Datomic database. Its a beautiful statement, at once illuminating ...
8 comments:
Friday, June 29, 2012

Gradle CoffeeScript Compilation

›
As I'm working on rebooting JavaScript support in Tapestry one of my goals is to be able to author Tapestry's JavaScript as CoffeeS...
1 comment:

Getting CrashPlan to work on Mac after JDK 1.7 upgrade

›
After upgrading my Mac to JDK 1.7, I noticed that CrashPlan stopped working. Given just how much trouble I got in a ways back when I lost...
4 comments:
Friday, June 08, 2012

Latency numbers every programmer should know

›
This is interesting stuff; Jonas Bonér organized some general some latency data by Peter Norvig as a Gist, and others expanded on it. Wha...
2 comments:
Wednesday, June 06, 2012

Synchronized Considered Harmful

›
New flash: concurrency is hard . Any time you have mutable data and multiple threads, you are just asking for abuse, and synchronized is s...
6 comments:
Tuesday, June 05, 2012

Things I Learned at Hacker Bed & Breakfast

›
You can spend any amount of money on Scotch, and it keeps getting better A Java instance field that is assigned exactly once via lazy init...
3 comments:
Friday, April 20, 2012

Yet More Spock Magic: Mocks

›
Spock's built-in mock object capabilities are just a dream to use ... unlike other systems I've used, it doesn't get in your wa...
Thursday, April 19, 2012

Yet Another Bit of Spock Love

›
I'm gradually converting a back-log of existing tests to Spock ... and some of them convert so beautifully, it hurts. Here's an exa...
6 comments:
Friday, March 09, 2012

Node and Callbacks

›
One of the fears people have with Node is the callback model. Node operates as a single thread: you must never do any work, especially any ...
1 comment:
Monday, February 27, 2012

Plastic: Advanced Example

›
Plastic is Tapestry's built-in Aspect Oriented Programming library, which primarily operates at the byte code level, but shields you f...
Thursday, February 23, 2012

Tests: Auto Launch Application, or Expect Running?

›
Does your test suite launch your application or expect it to be running already? This question came up while working on a client project; I...
5 comments:
Friday, January 27, 2012

LinkedIn Etiquette

›
I've used LinkedIn for many years now, long before I joined Facebook ... I liked the concept of never losing contact information with b...
1 comment:
Thursday, January 26, 2012

Tapestry Advantages

›
A summary of a discussion about the advantages of Tapestry over Struts : Exceptional exception reporting Significantly less code Live cla...
Tuesday, January 24, 2012

Tapestry 5.4: Focus on JavaScript

›
Tapestry 5.3.1 is out in the wild ... and if Tapestry is to stay relevant, Tapestry 5.4 is going to need to be something ...
12 comments:

Review: Gradle Class with Luke Daley

›
Last week, Luke Daly arrived in Portland to teach a three day Gradle class; the folks at Gradleware were nice enough let me audit the class...
2 comments: