Caffeinated Simpleton - Latest Comments

Re: Java, please stop ruining my fun.

Linus Ericsson — Tue, 28 Feb 2012 14:02:44 -0000

Today it's Leiningen that takes care of all this. Maybe Phils Corkscrew project mentioned here evolved into Leiningen?

I repeat: Don't try this at home, use Leiningen instead.

Thank you!

Re: An Introduction to JavaScript’s “this”

John — Thu, 23 Feb 2012 21:41:04 -0000

I've read many explanations of this, most are very long, none have come close to this one. I now actually feel like I understand it. Many thanks

Re: An Introduction to JavaScript’s “this”

Andrea Padovani — Mon, 23 Jan 2012 04:18:33 -0000

Very nice tutorial, thank you :-) Do you know if any of these methods is suitable to actionscript too?

Re: Java, please stop ruining my fun.

photo studio los angeles — Sat, 17 Dec 2011 08:04:56 -0000

CUI android everywhere

Re: My Radical-Right Agenda

photo studio los angeles — Sat, 17 Dec 2011 08:04:19 -0000

situation will be more worse in the coming days

Re: Java, please stop ruining my fun.

Wedding Videography San Diego — Thu, 03 Nov 2011 07:48:30 -0000

Great stuff! Thanks for the share. Very simple yet effective tips

Re: Java, please stop ruining my fun.

Santa Cruz Medical Clinic — Tue, 27 Sep 2011 02:53:23 -0000

Keep up the fantastic piece of work,Keep doing what you are doing
thanks

Re: Exploring memcmp

Dan McGee — Mon, 29 Aug 2011 18:51:46 -0000

I know this is a really old post, but thought I'd bring memmem() to your attention.

Re: Java, please stop ruining my fun.

los angeles wedding packages — Thu, 25 Aug 2011 08:17:44 -0000

I’d constantly want to be update on new content on this internet site , bookmarked ! .

Re: Java, please stop ruining my fun.

Moziko Wind — Tue, 09 Aug 2011 03:41:25 -0000

Market is driven by character user interface.......Java is really helpful in it.........

Re: My Radical-Right Agenda

chug2k — Mon, 20 Jun 2011 02:14:22 -0000

Re: immigration reform - I think one of the worst things is how difficult it is for educated folks to get a visa. Turning away low cost immigrant workers is one thing; turning away a proven professional is just brain drain.

Re: An Introduction to JavaScript’s “this”

Dylan Thomas — Tue, 17 May 2011 12:27:05 -0000

Excellent summary. Reading 'The Good Parts' and lots of online examples - none clearer that this one :-)

Re: An Introduction to JavaScript’s “this”

justin — Sat, 18 Dec 2010 21:11:29 -0000

Good catch!

I recently updated the post to use "self" instead of "my", since more and
more people are using that style these days. It's also the style I prefer
now. I guess I missed one!

Re: An Introduction to JavaScript’s “this”

Simon — Sat, 18 Dec 2010 21:05:09 -0000

I look at the code above and am confused on one line of code - see below, last line I paste. Where do you get 'return my.condiments' from? should it not be 'return self.condiments' as you note in the comment at the end of that line?

function HotDog() {
var self = this; // self references the current this, which is correct.
self.condiments = "mustard, ketchup";
self.getCondiments = function() {
return my.condiments; // self is guaranteed to be a reference to the original "this"

Re: Bujagali: Incredibly Fast JavaScript Templating

JSNoob — Mon, 15 Nov 2010 11:44:49 -0000

Any pros and cons compared to the increasingly popular Google Closure templates ????http://code.google.com/closure...

A definite pro for Closure Templates would be Google brand name, I guess.

Re: Bujagali: Incredibly Fast JavaScript Templating

aefxx — Wed, 10 Nov 2010 02:44:04 -0000

@justin

Hi there, I'm the author of jQote2 and I'd like to reply on jQote2 not being able to cache "well". Well, that statement is just plain wrong. jQote2 does have the ability to cache, both client-side and server-side.

If one feels that the compilation hit is too costly (note that every template is compiled only once, though), one might as well just precompile the templates and save those (lambdas as I call them) on the server. It's mere JavaScript in the end - less developer friendly but feasible.

You also mentioned that the actual template transformation is irrelevant and rather boring. Well, not quite as the resulting lambdas do differ a lot when it comes to performance. I've benchmarked templating solutions that ran 30x (and more) slower than jQote2 which would have a noticable impact on the end user's perception.

I will take the time and give bujagali a try and benchmark it against the top performers. Once done I'll let you know. Let's see how "incredibly fast" it realy is.

Re: Bujagali: Incredibly Fast JavaScript Templating

retro — Tue, 19 Oct 2010 15:52:59 -0000

I'm considering to use it as a server side template language for our CMSaaS so people that will use it should know _some_ Javascript and HTML. I really like how you combined power of Jinja / Django templates with Javascript syntax. Also, I really like macro functionality :)

Re: Bujagali: Incredibly Fast JavaScript Templating

justin — Tue, 19 Oct 2010 15:46:03 -0000

Thanks! That's good to hear.

There are some subtle things that a good understanding of JS helps with (like the difference between 'self' and 'this' in templates) and some crazy ways of designating functions to be called after rendering is complete, but you can definitely get going without using any of that craziness.

On the other hand, a lot of designers are becoming quite fluent in JavaScript, which is awesome. Those guys should (hopefully) have no problem.

Re: Bujagali: Incredibly Fast JavaScript Templating

retro — Tue, 19 Oct 2010 15:38:41 -0000

I really like Bujagali, and I think that you're wrong when you say it is not designer friendly. Every template engine has learning curve and I don't think Bujagali's is any worse than any other's. After all, you can choose how hard and complicated should it be.

Re: Bujagali: Incredibly Fast JavaScript Templating

justin — Tue, 19 Oct 2010 15:05:41 -0000

What it comes down to is that all JavaScript templates, when it comes to actually transforming templates into markup, basically do the same thing. So speed tests against moustache or jQote2 are boring, because while they might all be slightly different, the whole ecosystem around those systems hasn't improved, where it has for Bujagali.

Re: Bujagali: Incredibly Fast JavaScript Templating

justin — Tue, 19 Oct 2010 14:55:26 -0000

Moustache and jQote2 don't provide a built-in way of separating templates from the rest of your markup, meaning they don't cache well. Also, since the templates aren't pre-compiled, there will always be a compilation hit. Bujagali templates can be pre-compiled server side and sent down as regular old JS files. This is what we do at rdio.

It's kind of an entirely different approach, but I'll come up with some numbers and make a new post soon to illustrate the differences.

Re: Bujagali: Incredibly Fast JavaScript Templating

Matthew — Tue, 19 Oct 2010 08:23:10 -0000

How does it compare to jQote2 or moustache? How fast is it?

Re: Cobra is Ready to Release

justin — Sun, 17 Oct 2010 14:52:02 -0000

It's on github: http://github.com/JustinTullos...

Re: Cobra is Ready to Release

Robert Massa — Sun, 17 Oct 2010 10:31:06 -0000

Hi Justin, I'd love to try Cobra. A small and simple library like this is exacly what I need. It would be nice if you'd host the source somewhere. (github page doesn't exist anymore)

Re: A Threading Model Overview

Miami Web Design — Thu, 05 Aug 2010 21:10:53 -0000

Very good explanation. I personally prefer working with a framework like ruby