A Possible Future of Software Development

Channel:Google TechTalks · Length:1:01:33 · Published:2008-05-20 · Views:81897

Watch on YouTube

Summary

Sean Parent of Adobe argues that object-oriented frameworks ultimately fail to deliver scalable, high quality software and proposes combining generic and declarative programming instead. It draws on Stepanov's Elements of Programming.

Why HN recommends it

Frequently cited for the claim that Photoshop's codebase could shrink dramatically with generic programming.

Watch this Sean Parent video — HN, 2017

C, C++, Rust, Go & systems languages · Software architecture & design

Subtitles (excerpt)

>> PAWLIGER: Good afternoon. >> Hello. >> PAWLIGER: Hi. So my name is Marc Pawliger. I'm engineering director for client applications. And I'm here today with Sean Parent from Adobe Systems. Sean and I have known each other since '93, '94 or something like that, long, long time, when we worked together at Adobe on the Photoshop Team. And Sean has done a tremendous amount primarily in and around Photoshop up until recent times for the work that he's going to be talking about today put amongst other things; automation and UI layout and just a tremendous amount of capability into Photoshop. And of--I guess, the last couple of years has moved on into more of the research side of Adobe and has concentrated on areas primarily centering around STL and Adobe editions to them and also sort of looking at the whole problem of user interfaces and their complexity and behavior and why a lot of the software that we have works maybe despite itself and despite the way that it's built. So with that, I'll turn it over to Sean. >> PARENT: Okay. So, is my mic on? Yeah. So, that was a nice introduction. Thanks, Mark. I've been at Adobe now for something like 13 years and about the last four years working

On Hacker News

They make code reuse possible. Watch this Sean Parent video [VIDEO] where he estimates that if Photoshop was rewritten using generics, the code size would go from 3,000,000 LOC to 30,000 LOC. You are right, during compilation, generics are specialized so you end up with code, however going all in on generics removes a lot of accidental complexity. — adamnemecek, 2017-08
"Ask any C++ guru and they will tell you: avoid mutation, avoid side effects, don’t use loops, avoid class hierarchies and inheritance. But you will need strict discipline and total control over your collaborators to pull that off because C++ is so permissive. "Haskell is not permissive, it won’t let you — or your coworkers — write unsafe code. Yes, initially you’ll be scratching your head trying… — wwweston, 2013-09
This book is really good, really dense but the ideas have inspired a generation. In this video, Sean Parent, at the time working at Adobe on Photoshop, estimated that if PS codebase followed ideas from this book, the codebase could be reduced from 3,000,000 LOC to 30,000 LOC. [VIDEO] — adamnemecek, 2019-07
I'll give you a couple. Note that some of these are rehashes of my earlier comments. # Elements of Programming [LINK] This book proposes how to write C++-ish code in a mathematical way that makes all your code terse. In this talk, Sean Parent, at that time working on Adobe Photoshop, estimated that the PS codebase could be reduced from 3,000,000 LOC to 30,000 LOC (=100x!!) if they followed ideas … — adamnemecek, 2017-01
There's this book that I've been mentioning around here called Elements of Programming [LINK] that makes exactly this claim, that we are writing too much code. It proposes how to write C++-ish (it's an extremely minimal subset of C++ proper) code in a mathematical way that makes all your code terse. In this talk, Sean Parent, at that time working on Adobe Photoshop, estimated that the PS codebase… — adamnemecek, 2017-01

Related videos