UK Smalltalk User Group meeting - 31 May 2023
Giovanni Corriga <[email protected]> Tue, 30 May 2023 23:37:19 +0100
| Newsgroups | gmane.comp.lang.self,gmane.comp.lang.smalltalk.gnu.general |
|---|---|
| Message-ID | <CAJ3_VgYFa42vVr3NLHJ7Yjwx4fGweDLsjc85vFjTtjL--4Mm1A@mail.gmail.com> |
--===============5168387563242170591== Content-Type: multipart/alternative; boundary="00000000000043854105fcf0d970" --00000000000043854105fcf0d970 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable For our May presentation, Stephane Ducasse will present the vision behind Pharo and how that is been implemented incrementally across multiple releases. In Stef's words: "The vision of Pharo is based on three pillars: - First we want to make sure that Pharo is used to develop complex and robust systems (by complex we means multiple millions lines of code or objects). - Second we want Pharo to be a modular system that can be versatile (Pharo on iot, on large servers, in the web browser=E2=80=A6.) - Third Pharo should be an evolvable system that can adapt to new needs (modular tools, first class slot, new debuggers, packages=E2=80=A6). Sometimes it can be unclear that we follow this vision but over the years we are delivering this vision and we will continue. In this talk I will briefly recall the vision behind Pharo and show the achievements so far. I will show that our development is heavily backed by tests. In the second part of the talk I will focus on the current effort to improve the user interface. I will show that the reimplementation of the Spec UI framework is a cornerstone of the future replacement of Morphic and use of GTK. I will also answer questions about Pharo 11 and Pharo 12." Stephane is an Inria Research Director, currently lead the RMoD team ( http://rmod.lille.inria.fr/ ). Stef is an expert in language design, software quality, program understanding, program visualisations, reengineering and metamodeling. Among his contributions we can list: traits (implemented in Pharo, Perl, PHP and other languages); Moose, an open-source software analysis platform ( http://www.moosetechnology.org/ ). Stef is one of the leaders of Pharo ( http://www.pharo.org/ ), a dynamic reflective object-oriented language supporting live programming, and of the industrial Pharo consortium ( https://consortium.pharo.org/ ). Stef works regularly with companies such as Thales, Wordline, Siemens, Berger-Levrault, Arolla, and others on their software evolution problems. Stef has authored a couple hundred articles ( http://stephane.ducasse.free.fr/Publications.html ) and several books ( http://books.pharo.org/ ). This will be an online meeting from home. If you'd like to join us, please sign up in advance on the meeting's Meetup page ( https://www.meetup.com/ukstug/events/293473947/ ) to receive the meeting details. --00000000000043854105fcf0d970 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">For our May presentation, Stephane Ducasse will present th= e vision behind Pharo and how that is been implemented incrementally across= multiple releases. In Stef's words:<br><br>"The vision of Pharo i= s based on three pillars:<br>- First we want to make sure that Pharo is use= d to develop complex and robust systems (by complex we means multiple milli= ons lines of code or objects).<br>- Second we want Pharo to be a modular sy= stem that can be versatile (Pharo on iot, on large servers, in the web brow= ser=E2=80=A6.)<br>- Third Pharo should be an evolvable system that can adap= t to new needs (modular tools, first class slot, new debuggers, packages=E2= =80=A6).<br><br>Sometimes it can be unclear that we follow this vision but = over the years we are delivering this vision and we will continue. In this = talk I will briefly recall the vision behind Pharo and show the achievement= s so far. I will show that our development is heavily backed by tests.<br>I= n the second part of the talk I will focus on the current effort to improve= the user interface. I will show that the reimplementation of the Spec UI f= ramework is a cornerstone of the future replacement of Morphic and use of G= TK.<br>I will also answer questions about Pharo 11 and Pharo 12."<br><= br>Stephane is an Inria Research Director, currently lead the RMoD team ( <= a href=3D"http://rmod.lille.inria.fr/">http://rmod.lille.inria.fr/</a> ). S= tef is an expert in language design, software quality, program understandin= g, program visualisations, reengineering and metamodeling. Among his contri= butions we can list: traits (implemented in Pharo, Perl, PHP and other lang= uages); Moose, an open-source software analysis platform ( <a href=3D"http:= //www.moosetechnology.org/">http://www.moosetechnology.org/</a> ). Stef is = one of the leaders of Pharo ( <a href=3D"http://www.pharo.org/">http://www.= pharo.org/</a> ), a dynamic reflective object-oriented language supporting = live programming, and of the industrial Pharo consortium ( <a href=3D"https= ://consortium.pharo.org/">https://consortium.pharo.org/</a> ).<br><br>Stef = works regularly with companies such as Thales, Wordline, Siemens, Berger-Le= vrault, Arolla, and others on their software evolution problems. Stef has a= uthored a couple hundred articles ( <a href=3D"http://stephane.ducasse.free= .fr/Publications.html">http://stephane.ducasse.free.fr/Publications.html</a= > ) and several books ( <a href=3D"http://books.pharo.org/">http://books.ph= aro.org/</a> ).<br><br>This will be an online meeting from home.<br><br>If = you'd like to join us, please sign up in advance on the meeting's M= eetup page ( <a href=3D"https://www.meetup.com/ukstug/events/293473947/">ht= tps://www.meetup.com/ukstug/events/293473947/</a> ) to receive the meeting = details.<br><br></div> --00000000000043854105fcf0d970-- --===============5168387563242170591== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Self-interest mailing list -- [email protected] To unsubscribe send an email to [email protected] --===============5168387563242170591==--