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
Channel: People & Blogs Uploaded: May 20, 2008 at 2:18 am Author:googletechtalks
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 ...
DJFishlips(Thursday 1st of January 2009 08:14:38 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 :)
craiggybear(Saturday 13th of September 2008 09:25:54 PM)
So, Sean, this is why Adobe products are riddled with more holes than a sieve these days?
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.
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.
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.
