Comments for Feeding the Bit Bucket

Comment on The Pain of Premiere Pro by extenze reviews

extenze reviews — Thu, 24 Jun 2010 19:45:45 +0000

It is obvious that you enjoy doing what you do as your excitement can be notice in all your work. Don’t ever let the passion pass on as we are here always looking forward to what you have in store for us. Thanks for your readiness to share your astonishing masterpieces.

Comment on Clojure Resources by Tweets that mention Feeding the Bit Bucket» Blog Archive » Clojure Resources -- Topsy.com

Wed, 19 May 2010 08:37:58 +0000

[...] This post was mentioned on Twitter by Tech news (BOT). Tech news (BOT) said: Reddit/p: Overview of Clojure resources for beginners http://bit.ly/bGacnD [...]

Comment on Clojure Resources by Adrian Mouat

Adrian Mouat — Tue, 18 May 2010 20:12:07 +0000

Thanks Satish, that looks like a pretty good article. I’ll add it to the my post.

Comment on Clojure Resources by Satish Talim

Satish Talim — Tue, 18 May 2010 01:35:09 +0000

The following Clojure Notes for absolute beginners to Lisp and Clojure may be useful -
http://clojure-notes.rubylearning.org/

Comment on Clojure Resources by Feeding the Bit Bucket» Blog Archive » Clojure Resources | Common Lisp WebDev Insider

Fri, 14 May 2010 00:32:34 +0000

[...] Read the rest here: Feeding the Bit Bucket» Blog Archive » Clojure Resources [...]

Comment on Why use diffxml? by Adrian Mouat

Adrian Mouat — Sat, 08 May 2010 20:55:01 +0000

Hi Mark,

Sorry for the slow reply, for some reason WP marked you as spam.

You are right about context matching. I want to get the basics working properly first though!

Comment on The Pain of Premiere Pro by Adrian Mouat

Adrian Mouat — Sat, 08 May 2010 20:32:58 +0000

Those messages are great! Why do we put up with such bad tools though? Adobe seem to aim for as much functionality as possible, but they seem to forget it isn’t functional if it always crashes…

Comment on Why use diffxml? by Mark

Mark — Fri, 09 Apr 2010 00:45:14 +0000

Interesting, but one big problem, no context checking. A standard diff tool checks to make sure the change is really what the patch is, it doesn’t just say “change line three” it says “change the line that comes after these three lines, and before these three lines”. That way if the original file has changed in some non-relevant way ( a few lines added or removed else where), the patch should still work, and if the patch is on top of something else that’s also changed, you can detect the conflict.

For instance, I’ve got a project which has xml docs that we then need to update in “customize” releases. However, as the base project moves along, the original xml doc changes. I could generate a diff (between the orginal and customized version of the xml doc) with your tool, but the instant I added/removed elements from the root doc, the patch would start modify/deleting the wrong elements.

Comment on The Pain of Premiere Pro by AforAnonymous

AforAnonymous — Sat, 16 Jan 2010 22:06:42 +0000

You should take a look at the issues you get wiht Adobe After Effects:
http://futurestack.com/jump/aebugs/

Comment on Hunter S. Thompson and the Death of Objectivity by dotcoma » Blog Archive » Stop being ‘objective’. Be transparent.

Sat, 16 Jan 2010 12:41:35 +0000

[...] must-red for anybody who’s in the news [...]