Comments on: Futurist Programming 2.2

By: itjob123

itjob123 — Wed, 02 Dec 2009 19:49:13 +0000

thanks for information

By: meshula

meshula — Sat, 07 Nov 2009 02:32:47 +0000

In order to reject the past, the futurist must properly understand what is being rejected. I refer you to Lebbeus Woods’ essay on one of the primal Futurists, Antonio Sant’Elia.

http://lebbeuswoods.wordpress.com/2009/11/02/santelias-words/

Despite Sant’Elias’ protestations it is evident that his constructions are grounded in classical from and proportion.

I refer you also to Watterson’s Calvin & Hobbes, or Schultz’ Charlie Brown. Despite the apparent simplicity of their art, Watterson and Schultz are fine classical artists. Their mastery of classical form allowed them to simplify their work to radical elegant gesture.

So I contend that a good Futurist Programmer is altogether aware of all the reasons and precedents behind a choice.

By: Brian Royal

Brian Royal — Wed, 13 May 2009 14:45:11 +0000

Aras’ idealogy is what produces opaque source, reduced scalability and larger footprints, even if the resulting executable is effective, it will never be as tight as code written with at least an appreciation of the mistakes of our predecessors.

My impression of futurist programming is that futurists are actually rebirth programmers who are too lazy to study a little bit of the past.

By: leyond

leyond — Mon, 02 Feb 2009 09:57:16 +0000

null

By: admin

admin — Sat, 10 May 2008 20:54:19 +0000

Traceback: http://aras-p.info/blog/2008/05/09/on-job-titles-and-design-patterns/
Aras writes It’s the final result that matters. Futurist programming for the win.