Hello Stéphane i use Pharo in combination with Seaside because it is a really good platform for end user applications. (although i am currently not so active on this, because of other IT tasks) This went so far that I didn't even use the internal GUI for the apps user panels. instead everything via internet browser.. There should be more Internet Service Providers which offer (faster) Pharo/Seaside environments. As of today, most of ISPs don't even know what Seaside or Smalltalk is. (in-system intranet apps are mostly not a problem, fast enough) If this providing problem is solved than i see a great future for Smalltalk web based apps. because almost everything is in the same smalltalk environment, easy to program (well, once you learned Smalltalk) debug, and maintain. Cool. I found no other programming language that is so pleasant to work with as Smalltalk. and i like the Pharo development environment. You might recall the discussions i also was involved in about downward compatibility etc.. we had discussions about the impact of changes. Therefore: I'd prefer to see the Pharo environment (metaphorically) rather like a sun/star: solid core and more and more flexible going outwards.. in principle: the deeper (inner) one changes things the harder it becomes for the outer layer objects (apps) --- I think Smalltalk will evolve much further through the years Dreaming of a Smalltalk (or Self?) environment with no external data (like databases) except import export (oops, Collection classes need a drastic overhaul then :o) Everything integrated concept: VLI (Very Large Image. Terabytes..) Running IN a mainframe. Like a living entity. With the computers still rapidly improving this becomes very feasible. to backup? simply copy push down the whole image :o) Kind Regards Thanks all for Pharo. Ted (currently active with system support and making websites.) www.tedvg.com (one has to make a living again, hope i succeed.. :o\ On 02/19/2012 01:43 PM, Stéphane Ducasse wrote:
I would like to get from you why you use Pharo?
After thinking a lot about that recently I think that I would like to have something like that:
Pharo a plastic language to build evolvable and debuggable applications. With Pharo and its ecosystem you can build powerful tools (web application, data management, business processesâ¦). Pharo philosophy is driven by domain driven design. Modeling is agile. Pharo is an executable modeling language. Pharo is not only a language but an infrastructure with powerful tools like Moose.
Plastic = "(in science and technology) of or relating to the permanent deformation of a solid without fracture by the temporary application of force."
Pharo: ease of modeling, essence of agile, close to objects all the time.
Stef