Simplicity Ain't Easy - Stuart Halloway

Channel:ClojureTV · Length:50:00 · Published:2012-12-17 · Views:23958

Watch on YouTube

Summary

Stuart Halloway argues that simplicity is objective, with a definition and etymology useful to programmers, rather than a subjective buzzword. He shows how this view informs Clojure's design and how to make programs simpler.

Why HN recommends it

HN commenters recommend it, alongside Rich Hickey's talk, for its precise definition of simple versus easy and its implications for code design.

He talks about his definition of "simple" (by digging into what the original English definition was) and what that means for code. — HN, 2014

Functional programming · Software architecture & design

Subtitles (excerpt)

um uh you can you can um don't do it during the talk but later if you want do a Google search for simple programming languages or simple programming or simple whatever and and just follow your nose and and the me is is downright hysterical I'm going to share some samples of that so uh people use Simple to mean a lot of different things uh one thing that it often means is has something to do with keeping count right it's a scorekeeping thing so having one of something is simple and two of something is some somewhat more complicated and three of something and in fact some of you probably remember the interminable thread uh on the Google group how many people read this thread right the the title of the thread was simple things should be simple and it was all about the um stuff that Chaz would really uh care about right was all about automation effort around shipping some simple hello program right the the basic Automation and it was all about counting right how many lines how many lines are this how many lines are that how many are boiler plate how many tools it's all about counting uh and the presumption here is that that a small small count is simple and a big count is complex let's think about that there's a bunch

On Hacker News

Stuart Halloway has a great talk on this called "Simplicity Ain't Easy" [0] where he more or less states that a FP language like Clojure is basically a better designed OOP language, because FP is basically contains all its strengths (namespaces, abstractions and the like) and none of its weaknesses (e.g. uncontrolled state mutation) and you are able to select and use specific features you need to… — mindcrash, 2016-05
If you haven’t seen them, I recommend the Clojure guys’ talks about the subject of simplicity. They reached into the etymological history of the word “simple” to pull out its early definition, which is quite precise and IMO tremendously useful in this context, unlike the confused muddle of modern definitions. Rich Hickey, “Simple Made Easy”: [LINK] Stu Halloway, “Simplicity Ain’t Easy”: [VIDEO] — jacobolus, 2015-05
I would suggest to you that Clojure has a very clear "the Clojure Way" I would say, more so then almost any other language. It goes beyond syntax to a pretty deep design level. Its not even all that unique to clojure, you could do 'the clojure way' in other languages, but they usally dont. Some of the importent keynotes from some of the early conjs are really importent, and they really went deep … — nickik, 2014-12
I'll add this to your links: [VIDEO] He talks about his definition of "simple" (by digging into what the original English definition was) and what that means for code. — dkersten, 2014-05
To get an even better explanation on what the word "simple" means and what it derives from, I would recommend "Simplicity Ain't Easy" by Stuart Halloway[1]. While it is very similar to "Simple made Easy", it focuses a lot more on the etymology of the words "simple" and "complex" and how people misuse the word. [1]: [VIDEO] — JeanPierre, 2013-07

Related videos