A Possible Future of Software Development
Google Tech Talks July, 25 2007 ABSTRACT This talk begins with an overview of software development at Adobe and a look at industry trends towards systems built around object oriented frameworks; why they “work”, and why they ultimately fail to deliver quality, scalable, software. We’ll look at a possible alternative to this future, combining generic programming with declarative programming to build high quality, scalable systems. Speaker: Sean Parent Sean Parent is a principal scientist at Adobe Systems and engineering manager of the Adobe Software Technology Lab. One of his team’s current projects is the Adobe Source Libraries
Related posts:
June 30th, 2010 at 11:16 am
[...] on June 30, 2010 by ciprianpt New blog post A Possible Future of Software Development here: http://www.softwarepeer.com/windows/a-possible-future-of-software-development/ This entry was posted in Uncategorized. Bookmark the permalink. ← [...]
June 30th, 2010 at 11:40 am
@ProphetVS concrete class with template constructor taking an arg of any T and holds the arg via type-erasure. Operations on the held arg are done through free-functions found via Argument Dependent Lookup.
June 30th, 2010 at 12:32 pm
Regarding my earlier question, the answer seems to be the “External Polymorphism” design pattern.
June 30th, 2010 at 12:45 pm
There is a bullet point at the bottom of the slide at 38:52. It says:
“Extend generic programming to apply to runtime polymorphism.”
This intrigued me. Generic program using C++ and templates is a form of compile time polymorphism. To use runtime polymorphism, you virtual functions.
So I’m wondering what Sean meant in that bullet point. How do you extend generic programming, via C++, to apply to runtime polymorphism?
June 30th, 2010 at 1:01 pm
What does adobe mean?
June 30th, 2010 at 2:00 pm
Vejam este:
/watch?v=BPXzkli6NOg
June 30th, 2010 at 3:00 pm
Nice Informative Video. Keep it up
June 30th, 2010 at 3:15 pm
Did he ever solve the integer question, the problem of brainstorming a non-peano integer definition, which is more appropriate to programming?
June 30th, 2010 at 4:09 pm
This is what Dijkstra said software development should be!
June 30th, 2010 at 5:06 pm
This sounds a great deal like why Erlang uses functional programming (no side effects) and actor-based messaging. A spreadsheet is the most common sort of functional programming. You have established a sort of analogy between a spreadsheet, a DAG and your programming tasks. It seems like this suggests that we are going to see more functional programming. Time to brush up on Lisp/Scheme/Clojure, Erlang, Scala or F#.
June 30th, 2010 at 5:56 pm
yeah…real programmers work with a magnet.
June 30th, 2010 at 6:49 pm
Sorry – I haven’t been monitoring the questions here. Paper mentioned (incorrectly attributed to Doug Gregor – who’s done other good work) is:
Ronald Garcia, Jaakko Järvi, Andrew Lumsdaine, Jeremy Siek, and Jeremiah Willcock. An Extended Comparative Study of Language Support for Generic Programming. Journal of Functional Programming, 17(2):145–205, March 2007
June 30th, 2010 at 7:02 pm
Does anyone have a citation for the survey paper mentioned around 0:50:00?
June 30th, 2010 at 7:46 pm
The internet ruined everything, lowering the standards of what a “computer programmer” is.
June 30th, 2010 at 7:56 pm
yeah, sure… Did you know that Adobe revolutionized the print industry with PostScript then PDF, “fag software” like Illustrator, they were the first to use Bézier curves for vector graphics, etc.
“without Macromedia’s technology Adobe will be history today …”
Creating Fireworks would be impossible without using technologies invented by Adobe.
Or at least, that is my opinion
June 30th, 2010 at 8:02 pm
Hahaha. True.
June 30th, 2010 at 8:38 pm
Can’t wait till Windows 7 comes out. This concept reminds me of SimpleBasic and Boku and XNA concepts.
June 30th, 2010 at 9:13 pm
Adobe sucks, Macromedia software ruled, they buyed them and ruined everything … including Flash, Fireworks and Dreamweaver the 3 most powerful web apps ever maked, they had go-live and such fag software that nobody used … without Macromedia’s technology Adobe will be history today …
June 30th, 2010 at 9:47 pm
So, Sean, this is why Adobe products are riddled with more holes than a sieve these days?
June 30th, 2010 at 9:56 pm
3p6gkOZeNa8D6EIocsgd
Who says it ain’t easy being sleazy? I’m bored and I want a adult to do me!
c40geO53QtgE5BXccbrxgZ
June 30th, 2010 at 10:11 pm
Software companies and enegenerig in Russia is growng every day !
Investments in russian Software is a good idea !
June 30th, 2010 at 10:38 pm
Agreed. The video is a great case study on how to build a quality reusable library/framework.
Kudos to you and everyone involved to make ASL open source in MIT license. I’m one of the fortunate (paid) open source developers as well.
My original comment meant to point out that the title of the video might be a bit misleading to people who’re expecting new methodologies and/or new tools/languages.
June 30th, 2010 at 11:27 pm
As with geometry, there is no royal road to computer science. It is a challenge to the industry to learn to collect our knowledge into (re)usable components and the responsibility of every professional engineer and scientist to contribute.
July 1st, 2010 at 12:05 am
It’s still the same old approach to software engineering though: look at a class of specific problems to see if it can be solved by a more general solution, which is basically a reusable library. By properly limiting the scope and expressiveness of the library via a DSL, you reduce the probability of errors. Somebody still have to have solved the class of problems before one can embark on writing such generic libraries.
There is just no silver bullet in software engineering.
July 1st, 2010 at 12:45 am
really important matter.
how to talk about the future of things that should be mainstream for 50 years