Mountain West Ruby 2012 Capability vs. Suitability by Gary Bernhardt

Channel:Confreaks · Length:19:43 · Published:2012-06-05 · Views:21710

Watch on YouTube

Summary

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.

Why HN recommends it

HN commenters reuse the capability-versus-suitability framing to discuss languages, restriction versus freedom, and tool design.

Very nearly exactly what you're describing — HN, 2023

Programming language design · Software architecture & design

Subtitles (excerpt)

[Music] [Music] okay as you can see I'm trying to approach looking like the image I always put up before my talks getting closer and closer every time I do this maybe I should roll my sleeves up it'll be a little bit more accurate um so the this talk is those who forget the past some of you have seen this at uh scna but this is a slightly different version of it I am Gary burnhard uh I look like that on the internet and I run a company called destroy all software and this talk structure is going to look like this first of all capability and suitability I'm going to define those terms I will give you some examples of what I mean by those words then we'll look at patterns over the history of the industry uh with capability and Su suitability then the junk drawer every talk needs a junk drawer and this one is about relationships and then finally uh productivity the word productivity which I hate and then some divination about what might happen in the future so first up capability and suitability by capability I mean the power for a software system to EXP Express an idea this could be a language or a practice or a tool and uh the canonical capable system is lisp and I'm thinking here of a fully

On Hacker News

There was this talk ("Capability vs Sustainability") from 2012: [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. — al2o3cr, 2023-06
See also the Gary Bernhardt talk, Capability vs. Suitability: [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 anym… — thristian, 2015-10
This really comes back to the Capability vs. Suitability model that Gary Bernhardt has spoken about: [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. — fnord123, 2019-07
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… — zachrose, 2018-10

Related videos