by Jared
on Jul 29, 2010
This is the last in a four-part series, in which I demonstrate how to build a CSS parser using CodeTalker:
To get the code for this:
git clone git://github.com/jabapyth/css.git
by Jared
on Jul 29, 2010
This is the third in a four-part series, in which I demonstrate how to build a CSS parser using CodeTalker:
To get the code for this:
git clone git://github.com/jabapyth/css.git
by Jared
on Jul 28, 2010
This is the second in a four-part series, in which I demonstrate how to build a CSS parser using CodeTalker:
To get the code for this:
git clone git://github.com/jabapyth/css.git
by Jared
on Jul 27, 2010
This is the first in a four-part series, in which I demonstrate how to build a CSS parser using CodeTalker:
To get the code for this:
git clone git://github.com/jabapyth/css.git
by Jared
on Jul 27, 2010
In last couple of weeks a few of my projects (most notably vim-debug and CodeTalker) have really begun to take off and generate some public interest.
Unfortunately (for the projects), I will be leaving next week to serve an LDS Mission in Germany for the next two years, during which time I will have exactly no time to pursue various hobbies, least of all Coding.
by Jared
on Jul 26, 2010
Or at least that's the idea. I tried to design CodeTalker such that you don't need to pore over pages of API docs... This document + the example contrib parsers provided should be enough (let me know if they aren't).
by Jared
on Jul 26, 2010
As per request, I've decided to write down what I've learned from my optimization adventures with CodeTalker.
by Jared
on Jul 22, 2010
diff is one of those programs that's just been around forever, and that hasn't changed much b/c it's the best it can possibly be. ...right?
Sort of. For finding out which lines have changed between two files, there's none better (maybe). 40 (!) years of use has shown us this. But for finding the difference between two files? I argue that those two problems, which have been so long conflated, are actually not the same.
by Jared
on Jul 21, 2010
One thing that has bothered me about distutils is its lack of a "test" command -- it seems strange to me that setuptools has it but distutils does not...
Anyway I looked around to make sure it really wasn't there (I couldn't believe it at first), but finally, convinced, I wrote my own.
by Jared
on Jul 21, 2010
One problem that I needed to solve while making CodeTalker was fast tokenization -- so I benchmarked several implementations of matching the WHITE and ID tokens.
by Jared
on Jul 21, 2010
Just when you though codetalker couldn't get any faster, I managed to double its speed.
in case anyone's wondering, the binary around the logo corresponds to the ascii string "codetalker"
I've put together some updated graphs, for JSON and CSS parsing...
by Jared
on Jul 17, 2010
And I put together another graph, profiling the different libraries for parsing CSS with python.
by Jared
on Jul 17, 2010
In the course of rewriting CleverCSS, I wanted to write a backwards converter from css to ccss. I thought it would make the tool much easier to adopt.
In the end, I wrote my own CSS parser with codetalker.
by Jared
on Jul 17, 2010
One of the comments on reddit when I announced codetalker was "what's wrong with pyparsing?"
So I thought I'd run some comparisons, detailing why I felt the need to reinvent this particular wheel.
by Jared
on Jul 16, 2010
I was looking around for ways to get a look at a python dependency graph, and found this site which actually does a pretty good job. The only gripe I have regards the command you must use:
python py2depgraph.py path/to/my/script.py | python depgraph2dot.py | dot -T png -o depgraph.png
Couldn't be easier, right? ...
