ATTENTION: You are viewing a page formatted for mobile devices; to view the full web page, click HERE.

Main Area and Open Discussion > Living Room

Trying to remember quote about design and beauty

<< < (2/4) > >>

Curt:
^ hehe, yes.

But it's obviously not what Stoic Joker is looking for:

something to the effect that a machine that was designed to work well/efficiently would therefore be beautiful.-Stoic Joker (August 12, 2016, 07:08 AM)
--- End quote ---
We are not robots.  There's nothing efficient about sitting in a canyon and staring at the view in front of you.  But it's beautiful.  That's because efficiency is not beautiful.  There's nothing efficient about watching a 3+ hour opera called the Marriage of Figaro.  But it's beautiful.

There's nothing beautiful about constantly texting forgettable phrases back and forth for the rest of your life.  but it sure is efficient...I suppose.
-superboyac (October 04, 2010, 05:09 PM)
--- End quote ---
Warning - while you were typing a new reply has been posted. You may wish to review your post.-Post reply
--- End quote ---
Start from what you know people must have, and then try to make that set smaller. When you can make it no smaller, you've reached a nice [starting] place with your project.-zridling (February 18, 2009, 11:14 PM)
--- End quote ---

Anyway: We have this thread named Beautiful Code: In your opinion, what makes code Beautiful?
-it's not machines, but just maybe it includes what you're searching for:

1. It is better to have 20 lines of understandable clear simple code than 4 lines of complexity. - Mouser
2. The real question is does it make any non-negligable difference when it's all compiled down to bytecode anyway? If so, it probably needs to be evaluated for each programming language. - Deozaan
3. If it uses more memory, so what? Premature optimization is the root of all evil. Lets not optimize that until a problem is created by being too organized, which is near impossible. - CodeByter
4. Would you rather have a program use 100k extra memory or have the same program crash more often because its code is hard to understand? - mouser
5. If the program needs to read millions of pieces of data, then 1ms of delay can add up. - Deozaan
6. There's a balance between clear code and complex code with less lines. Just clarity at the cost of crazy insane slowdown would be silly. - Gothi[c]
7. Even when code is slower, you have to ask yourself, is it happening in a place that matters. There are very very few cases where it is better to have ugly short code than longer clearer code. - Mouser
8. We shouldn't strive to write longer code but rather to write code that is easy to understand. - Mouser
9. The goal should be: efficient easy to understand, short if possible, code. - Gothi[c]
--- End quote ---

mouser:
The Buckminster Fuller quote was the one i was going to suggest.

skwire:
Robert Marshall?  "Look what a beautiful mechanism that is. It's obviously designed to do what it does. It must have been made that way."

Stoic Joker:
Robert Marshall?  "Look what a beautiful mechanism that is. It's obviously designed to do what it does. It must have been made that way."
-skwire (August 12, 2016, 01:01 PM)
--- End quote ---


Nice, but no.


The thrust of the quote was that the mechanism's beauty was by virtue of the efficiency of its function.

Another rough-ish guess at what it's supposed to be (something like): If the a machine is designed to do something extremely well, and does, it is by it nature beautiful

1NR1:
Then there is: 

"Art is anything you can get away with."

(Mcluhan).
 
;)

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version