18/03/2012 Leave a comment
18/03/2012 1 Comment
From now on, I won’t be posting here anymore* and wil instead be using my shiny new blog over jawher.me.
It has been 2 years since I started using wordpress(.com) (after having used blogger and b2evo before), and while it’s a nice and quick-to-bootstrap solution, I’ve started to grow annoyed with it for the following reasons:
- I have spent years waiting for wordpress.com to include a clean, a really clean, theme, wide enough so it doesn’t butcher code snippets (this is a technical blog after all), but nope, no luck. I also found the paying themes were a bit too expensive.
- Ads. I only noticed them recently when I had to check something quick in my blog using IE. Yup, it only took me 2 years to figure that out, thank you adblock ! I have no problem with “classy” and contextual ads, but the one I’ve seen the other day was plain awful. Again, it was a free service, so …
- They had many performance issues, especially on the backend-side
Again, I’m not complaining: I’m more than grateful for the wordpress.com for what they offered me and millions of other blogger, a nice free hosting package, but it’s time for me to move to greener (I hop) pastures.
Enter my new blog: jawher.me, built on Jekyll and served with nginx from an EC2 micro-instance. I’m rather happy with my new setup, especially the markdown format (instead of html), and the freedom it gives me. Also, it’s backed by a Github repo: a push and a couple seconds later (which will eventually become minutes, Jekyll is not a speed beast) the changes are reflected on the site. I’ll eventually blog in more detail on my setup.
* Actually, I’ll continue, for some time at least, to post links in here to the new posts.
03/03/2011 Leave a comment
In a previous blog post, I’ve talked about templating in general and showed a quick example of how Moulder does templating.
Unlike many other templating libraries, Moulder keeps the template data and the templating rules in separate files. The template data can (only) be any XML-like format, including HTML.
The templating rules are written in Scala or in Java (depending on the version you choose) and mimics jQuery’s usage patterns, i.e. a rule is expressed as a CSS selector and a list of operations to perform on the elements returned by that selector.
28/02/2011 Leave a comment
Processing XML files is a PITA. There. I said it. Processing XML files using the Java standard XML API, i.e. JAXP is even worse. There are some nicer APIs out there that alleviate this pain, like XPATH, XStream, JAXB, Castor, etc.
But still, they all fail in some point or another, ranging from being verbose and tedious to write to not being able to handle large XML streams.
The latter is a killer for many of the higher level approaches out there. Try using XPATH or any mapping library on a file weighing more than a couple of megabytes.
To handle such cases, we are usually left with StAX. Don’t get me wrong: StAX is not that bad an API, and I’d take it any day instead of JAXP even for small files. It still is a very low level API and parsing the simplest of files requires an impressive amount of code. Also, handling state with StAX is a painful exercice. You usually end up building a full-fledged state machine to do it.
23/02/2011 Leave a comment
Extrait du synopsis :
Cet article va présenter le framework Apache Wicket et ce en s’appuyant sur la création d’une application de suivi de bugs (Bug tracker) qu’on nommera “Min.Bug.Tra”. Une telle application est un cas particulier de ce qu’on appèle CRUD (Create, Read, Update et Delete) mais qui a l’avantage de traiter une problématique réelle.
L’article complet est par ici : Création d’une application de type CRUD avec Wicket
19/01/2011 Leave a comment
Insert an element at a given position into a list.
user> (insert-at(\c, 3, (list \a, \b, \d))
(\a, \b, \c, \d)