utx00

in this case it's a good way of getting smooth animation specially in a dual core whatever whatever :)

or even adding an "n" in front of the function name goes a loooooooong (emphasis on the "o") way towards helping. nconc, nreverse ...

clojure is smart about it, and only copies what changed. start here: http://clojure.org/state

check out chapter 3 of "on lisp". specially the part about functional interfaces.

i thought it sounded pretty clever

can you outline a sketch? closures by themselves do not guarantee the absence of side effects ie:

  (let ((state 'someobject))
    (defun phase1 ()
      (done1 state))
    (defun phase2 ()
        (done2 state)

. . .

and so on

i think pure functional programming is not a practical possibility. functional systems are functional until they are not (scheme's set!, clojure's transactions, ....) maybe the important thing is to keep in mind which parts of your system mutate data, and which parts do not.

this was either written by someone with no experience in C, or a C uber expert.

a macro can be pointless sure. mostly if the same thing can be accomplished with a function (most of the time, but not exactly). a macro is not a function that's being inlined.

funny that he didn't touch upon the REPL. for me, that's second only to macros. also for examples, just look at news.arc. the vars-form stuff, and the little template languages (trtd) etc ... is far superior than at least all of the django form and template stuff ... and it seems that it was not more than an afterthought; compare with the craziness of having a template language and the difficulty this sometimes presents. sure, adding a tag library in django is not the end of the world, but you can't beat the immediacy of arc's html macros (which you can find for CL on the ansi book). then add a REPL on top, and you are on another league of power and productivity. granted news was written by an expert, but i don't see the comparable power coming from django (and maybe rails) and it's safe to assume those guys know their python.

we have the need to create lots of web forms quickly for work (lots and lots). we used django which was a god-send in this regard, but it was still too time consuming (think deployment, styling, SQL databases). so taking a hint from the html chapter in the ansi book we wrote a system in which you define fields within sections within pages to the point where even the non-programmers can now do it ie:

(defpage page3) (defsection section-x) (definputfield blah :type text :section section-x :page page3)

this is enough to put the field up and tie it into storage (it uses page.section.fieldname as key which could be an issue if you want to move stuff around). you can also do this in the (production) REPL, and the field will show up right away (with an exception if you dup something). we don't do major releases this way, but if a researcher wants something right away and he/she is a big shot then it has to be done now. well, there you go. it's done as fast as we can type it in.

there's your example, and i'm sure there are more. try that with c++.

also, lisp is not in more widespread use for the same reason soap operas, and brittney spears are more popular than shakespeare, and beethoven.

how does it follow from this then, that men are happier?

what if someone changes git history? some rebasing or something like that? how does it affect downstream hg clients?

thanks.

not necessarily. mutt/pine, emacs/vi, irrsi/chatX, python/ruby, .... in general a good thing.

"I’m not surprised to see my cousin use such things as she’s a “people person” - she always wants to be a center of attention - that validates her existence. Don’t get me wrong - I don’t condemn her"

well, as long as he doesn't condemn her.

thanks. i think i'm sticking to js then.

surely all these things and more can be accomplished with straight javascript. look at jquery! and extjs, prototype, ...

jquery has gone so far that it is starting to smell like a DSL. all in js.

thanks for the feedback.

amazing language. hope it takes off.

yes. but how is that generated js being served?

ok. ok. i misunderstood. interesting. so why wouldn't i just write javascript? what is the value added? aside from the fact that i'm not coding in javascript (which i don't consider a negative)

yes. but how is that generated js being served?

what do you think about something like extjs?

very informative. thanks.

i think in cappuccino you do everything in the "backend". there's no need to write javascript/html/css ... which is good in a lot of ways (you can output source for different devices, and i'm even guessing you could generate different backends - php, .NET) - but i'm more interested in the js/AJAX everything model, lighter on the backend.

i've never worked in objectiveC/J but js seems nicer at first glance. but i may just be saying that so that i don't feel like i would miss something should we choose etxjs.

more feedback would be appreciated guys.

does anyone have experience with something like this (or SproutCore, GWT) versus a heavier javascript solutions that uses the backend purely to get data? i'm thinking extjs on the frontend with an api on the backend (probably django for the admin). any feedback? ps: i expect to write js most of the time as opposed to (in this case) python. extjs is rich enough that i don't have to muck with html/css either and i can throw google gears for good measure.

sorry, too long.

appreciate any comments.

what about two feeds?

really? with python/ruby/clojure/erlang/lua/js coming up in the world? ... i thought this was going to be a 1991 article.

people have been using mta pipes to all sorts of scripting/dynamic/futuristic languages for years. that's what procmail is, except it has an ugly language. however it's not like one is using this 10 hours a day. you set it up, and you are done.

if this is 1970ish, then so is typing ls (forks and pipes galore) on a terminal, and i don't see anyone complaining about that. i'm not exaclty thrilled with the use of a SQL backing store either, more to install, more to monitor, more things that can go wrong.

sure most MTAs are byzantine horrors as you put it, but it's not like they need constant tweaking either. you set them up, and off they go (both exim, and postfix). we rarely need to touch their configuration once they're up and running. so why would i introduce yet another piece of infrastructure? what do i gain with this exactly?

the tone is unfair - he was the one who got his act together and got it done. one could make a similar argument/"investigation" about any creation.

you sir, is a genious.