maxtilford

Sounds like the Eudaimonia Machine concept: https://blog.fentress.com/blog/the-eudaimonia-machine-a-spac...

What you quoted doesn't mention an IDE at all. "extract interface" is just the name of series of steps that you can accomplish with or without an IDE.

Martin Fowler's book 'Refactoring' gives names a whole bunch of these. That might be where the op is coming from.

The demos are broken due to git merge tokens. (line 87 "<<<<<<< HEAD")

That S-expressions can/often contain code doesn't make them more complicated when used for data only. Anything can contain code.

No technical limits were hit. They have nearly the same feature set.

Geocoder's api feels a little bit more modern Geokit (rails3 vs 2). Having read the code for both, Geocoder was cleaner and would be easier to tweak if necessary.

So really it's just a preference: they do the same thing.

I just switched from geokit to geocoder in the app I'm building. I found geocoder to be significantly better for my purposes.

You're welcome to contact me anytime with questions. (emails in profile)

I think this blog post will be relevant: http://blog.sigfpe.com/2006/12/evaluating-cellular-automata-...

CommonPlace -- Cambridge, MA (http://commonplaceusa.com)

We're a nearly-funded startup creating a social platform for local communities and neighborhoods.

* Web Dev Intern: Will be working on a Ruby on Rails web app with some civic-minded Harvard students. Some programming experience nice, but not required. We will help you learn as needed.

Contact maxtilford at gmail

CommonPlace -- Cambridge, MA (http://commonplaceusa.com)

We're a nearly-funded startup creating a social platform for local communities and neighborhoods.

* Web Developer: Will be working on a Ruby on Rails web app with some civic-minded Harvard students.

Contact maxtilford at gmail

C-z

Very nice. That's a tool I was just about to need. My circles and rectangles are a bit sloppy... Scratch that, I found the toolbox. Awesome.

It didn't. I'm pretty sure.

I use linux: gentoo, arch, and ubuntu. But if you're using ruby, you should just use rvm. Then the distro doesn't matter that much.

Mainly, I'm tired of using $.getJson, and I liked your on-server macro. Also, how is the server going to watch references on the server and vice-versa?

Awesome. I've got it up and running. I've been looking for a solution for the client/server distinction for a while. How much have you thought about the implementation of that?

Cambridge, MA

We're building a social network for communities and neighborhoods and ooking for Rails developers.

Contact [email protected] if you're interested.

I spent some time the last couple days learning two songs on a penny whistle. Great fun.

I bought a nice hat from http://www.kleinbottle.com/ and he sent me pictures of it being packaged up, so this sort of thing has been done before. I've no idea about patentability though.

I used it a lot before and I use it a lot now. It took a bit of getting used to, but I rather like the new design. I've found that I'm listening to a lot more new music, where before the redesign I just kept listening to the same stuff over and over.

I think tail call elimination is handled in the Apply method for closures - http://github.com/bobappleyard/golisp/blob/master/lisp/lisp.... . Looks like a trampoline to me.

I play several, but not necessarily what I'd call proficiently.

I have 42 tabs open. I use Firefox's tree tabs add-on. After pruning, I now have 22 tabs open.

http://pushudo.com is trying to solve the specific case of emailing links to people.

disclaimer: I do some part-time work for them.

Yes, that's correct.

Using do-notation is probably cheating, but what do you think of this? (in Haskell):

  do { w <- widgets;
       s <- sprockets;
       l <- locations;
       guard (l `hasInStock` w);
       guard (l `hasInStock` s);
       guard (w `isUsableWith` s);
       return (w, s, l); }

We're trading horizontal space for vertical space. I think it's much clearer than either list comprehensions or plain map/filters. It's the best of both worlds.

Obviously, map and filter are better because ... ah, hmm, I don't know.

I think it is a matter of language design. Higher order functions are not as prominent in Python as say, Haskell, where map & friends are generally preferred for composability. Lispers prefer map & friends just because list comprehensions add all that messy syntax.

If I were a Python programmer, I would probably use list comprehensions, since they seem to be the preferred idiom.

'Bon' is French for 'good'! (It's on the about page.)

I second the request for architecture info.

Last summer I did an internship in Den Haag with Streamtech. (http://www.streamtech.nl) I don't know much about the job situation, but it's a great place to live.