Mountain West Ruby 2012 Capability vs. Suitability by Gary Bernhardt
Confreaks2 HN recommenders · recommended in 2 months, 2015-2023
22K views · 14 years ago · talk · evergreen
Gary Bernhardt argues that software history moves in reactions to earlier tools, and that new tools are not simply better in every way. He distinguishes capability (what a tool allows) from suitability (what it fits), and warns against repeating past mistaken reactions.
HN commenters reuse the capability-versus-suitability framing to discuss languages, restriction versus freedom, and tool design.
28:06MountainWest RubyConf 2014 - But Really, You Should Learn Smalltalk
Confreaks
27K views • 12 years ago
1:03:31Brian Goetz - Stewardship: the Sobering Parts
ClojureTV
39K views • 11 years ago
45:55Ruby Conf 12 - Boundaries by Gary Bernhardt
Confreaks
58K views • 13 years ago
51:57Lone Star Ruby Conference 2010 Real Software Engineering by Glenn Vanderburg
Confreaks
30K views • 15 years ago
39:40"Type-Driven Program Synthesis" by Nadia Polikarpova
Strange Loop Conference
15K views • 8 years ago
36:53Rails Conf 2012 Keynote: Simplicity Matters by Rich Hickey
Confreaks
220K views • 14 years ago
44:59Ada, Past Present and Future
AdaCore
17K views • 15 years ago
1:01:45Four Languages from Forty Years Ago - Scott Wlaschin
NDC Conferences
33K views • 8 years ago
1:32:47Data-Oriented Demo: SOA, composition
Jonathan Blow
201K views • 11 years ago
12:31OSCON 2010: Rob Pike, "Public Static Void"
O'Reilly
119K views • 16 years ago
55:08Rust: A Language for the Next 40 Years - Carol Nichols
ChariotSolutions
367K views • 7 years ago
1:29:49Going Native 2012 Keynote Stroustrup
savage309
33K views • 14 years ago
51:40Constraints Liberate, Liberties Constrain — Runar Bjarnason
Scala World
44K views • 10 years ago
25:06"Making Impossible States Impossible" by Richard Feldman
elm-conf
63K views • 10 years ago
54:55Dconf 2014 Day 2 Keynote: The Last Thing D Needs -- Scott Meyers
The D Language Foundation
19K views • 8 years ago
37:07Scale By The Bay 2018: Bryan Cantrill, Rust and Other Interesting Things
FunctionalTV
45K views • 7 years ago
7:157 minutes of Pharo Smalltalk for Rubyists
Avdi Grimm
37K views • 11 years ago
53:12Yehuda Katz - Why Rails is Hard (Railsberry 2012)
applicake
29K views • 14 years ago
1:09:24Effective ML
Jane Street
30K views • 10 years ago
1:58:46Dynamic Languages Wizards Series - Panel on Language Design
Eduardo Cavazos
16K views • 14 years ago
4 comments from Hacker News
There was this talk ("Capability vs Sustainability") from 2012: ▶ this video Very nearly exactly what you're describing; not sure if it's the same thing you were thinking of, or just part of a similar thought-wave at the time.
This really comes back to the Capability vs. Suitability model that Gary Bernhardt has spoken about: ▶ this video IRC is capable. It is a box of nuts and bolts that lets us communicate and build awesome bots and so on. Bloating the protocol gives us suitability: features that are robust and can federate.
Using Elm, even a little bit, has given me a perspective on what a different language can do in the browser. If you subscribe to Gary Benhardt’s Capability/Suitability theory of programming history [1], JavaScript is the highly capable technology that can be used for any sort of architecture you can imagine, and Elm is a turn towards suitability that says, “some of those architectures are unsound or have a very low floor for quality.” You might want to abstract over DOM APIs for different reasons, but at their semantic core they are fine. [1] ▶ this video
See also the Gary Bernhardt talk, Capability vs. Suitability: ▶ this video Some technologies are radical new developments designed to give people some new capability they never had before. Other technologies are refinements of some previous capability technology, restricting the capabilities but more suitable for some particular problem-space or setting. It's not necessarily "nobody has big ideas anymore", it's just a natural cycle. On the other hand, if you want a less-charitable view, consider this: programming in the 1980s was dominated by ideas from C, a language developed in the 1970s. Programming in the 1990s brought the influence of Smalltalk, a language developed in the 1970s. The 2000s saw the introduction of functional programming ideas from Lisp, a language developed in the 1970s. These days, the hot new programming language features are being taken from Standard ML, a language developed in the 1970s. Someday the 1970s will be mined out, and then we can start coming up with new ideas again.