October 2022 - Pharo-dev - lists.pharo.org

Digital Twin applied to Software

by Aik-Siong Koh

Hi: I have a novel idea "Digital Twin applied to Software". See attached slides. It points to the future of improved programming productivity and reliability. Let me know what you think. Thanks, Aik-Siong Koh http://ar-cad.com Abstract Digital Twin applied to Software Aik-Siong Koh askoh.com There has been a major dichotomy in computing right from the beginning: Statically Typed vs Dynamically Typed programming languages. The former languages produce fast executables but are inflexible to program. The latter are just the converse. This dichotomy has been frustrating to programmers who always feel they have to make sacrifices when making a choice. It also often leads to futile language wars. The Digital Twin concept was introduced in engineering where a physical system is modeled digitally in geometry, simulation and other information. The concept has proven so successful that it is being applied to almost everything in engineering from simple mouse traps to complex whole cities. It occurred to the author that this concept can be extended to software too. For example, execution in C++ is famously fast. But development in C++ is notoriously difficulty because of language complexity and long build times. A flexible digital twin can be a program written in Smalltalk which is famous for live programming. "Development at the speed of thought" is the motto and is real. What is gained by this duplication? Firstly, the flexible twin can be use to explore new algorithms, features, solutions and fix bugs quickly. Only desired codes are translated to C++ manually or automatically. Secondly, the two programs can check each other so that bugs are reduced significantly. These two gains will define future programming productivity and quality. The Digital Twin concept will also drive the automatic translation of the flexible language to the fast language. Bio Dr Aik-Siong Koh has a PhD from The University of Texas at Austin where he programed in FORTRAN to simulation mechanical systems. While teaching at Texas Tech University and Nanyang Technological University, he developed interest in Multibody Dynamics. To develop his own Multibody Dynamics simulator, he researched for the most productive programming language and discovered Smalltalk. The live programming capabilities of Smalltalk permitted him to build a successful simulator which he then proceeded to commercialize. His later experience with C++ at Mechanical Dynamics and MathWorks gave him the idea of Digital Twin for Software.

Oct. 28, 2022

This week (43/2022) on the Pharo Issue Tracker

by Marcus Denker

This week (43/2022) on the Pharo Issue Tracker We merged 8 PRs this week: Features ======== - Add a shortcut to extract method refactoring #11814 https://github.com/pharo-project/pharo/pull/11814 - Adding removeKey:ifAbsent: #11821 https://github.com/pharo-project/pharo/pull/11821 - add Collection>>atRandom:weighting: and cie and tests #11829 https://github.com/pharo-project/pharo/pull/11829 Fixes ======== - Fix : missing isScripting method in LessonView #11815 https://github.com/pharo-project/pharo/pull/11815 - made rename method refactor "Spec2 compliant" #11826 https://github.com/pharo-project/pharo/pull/11826 - Cleanup-asCollectionElement-ChunkFileFormatParser #11827 https://github.com/pharo-project/pharo/pull/11827 - Bugfix: Browse class from Meta inspector pane #425 https://github.com/pharo-spec/NewTools/pull/425 Pharo10 ======= - Pharo10: 6191 find between substrings freezes the image #11770 https://github.com/pharo-project/pharo/pull/11770

Oct. 28, 2022

Looking for an engineer position to work on Virtual Machines

by Pierre Misse-Chanabier

Hello, My name is Pierre Misse-Chanabier. I'm finishing my PhD in the RMOD team on testing Virtual Machines in about two months. I am therefore looking for a Job, hopefully in the Pharo community ! Ideally, I'm looking to work in the domains of Virtual Machines or Language Tooling, or Meta-programing, but I'm open to other opportunities. See my CV attached. I have to stay in Lille for at least the next year, therefore, I am looking to work remotely. Here are my most important projects and publications about them: Illicium : a framework to generate C code from Pharo code. Github repository: [ https://github.com/hogoww/Illicium | https://github.com/hogoww/Illicium ] IWST'19 Illicium: A modular transpilation toolchain from Pharo to C [ https://hal.archives-ouvertes.fr/hal-02297860/ | https://hal.archives-ouvertes.fr/hal-02297860/ ] version poster SAC'22 & full ICSR'22: Differential testing of simulation-based VM generators: automatic detection of VM generator semantic gaps between simulation and generated VMs [ https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 | https://link.springer.com/chapter/10.1007/978-3-031-08129-3_7 ] [ https://dl.acm.org/doi/abs/10.1145/3477314.3507171 | https://dl.acm.org/doi/abs/10.1145/3477314.3507171 ] Polyphemus: Retro engineering of the Pharo Image, and ease of VM tooling Github Repository: [ https://github.com/hogoww/Polyphemus/ | https://github.com/hogoww/Polyphemus/ ] Video Presentation for Esug Innovation award (I was unable to present it myself): [ https://www.youtube.com/watch?v=zf3cCtNW830 | https://www.youtube.com/watch?v=zf3cCtNW830 ] VMIL'22: Ease VM Level Tooling with Language Level Ordinary Object Pointers [ https://hal.inria.fr/hal-03827632 | https://hal.inria.fr/hal-03827632 ] (preprint) I am particularly interested in my latest work: Polyphemus. I have also worked on many part of the Pharo ecosystem. The Pharo VM, The Pharo bootstrap, Calypso, Debugger, selector extraction, Iceberg scripting, SUnit ... Let me know if you have openings or questions ! Pierre

Oct. 25, 2022

This week (42/2022) on the Pharo Issue Tracker

by Marcus Denker

This week (42/2022) on the Pharo Issue Tracker We merged 9 PRs this week Features ======= - Add a shortcut to extract method refactoring #11814 https://github.com/pharo-project/pharo/pull/11814 Fixes ===== - Fix : missing isScripting method in LessonView #11815 https://github.com/pharo-project/pharo/pull/11815 - Update comment to reflect refactoring actions #11778 https://github.com/pharo-project/pharo/pull/11778 - CI: when getting pharo version/prefix on PR, do not use --first-parent #11780 https://github.com/pharo-project/pharo/pull/11780 - Pharo11: 6191 find between substrings freezes the image #11771 https://github.com/pharo-project/pharo/pull/11771 Cleanups ======== - 11792-FFIConstantHandleTest-calls-deprecated-method-FFIExternalReferencehandle #11793 https://github.com/pharo-project/pharo/pull/11793 - moved the condition creation from the calypso package to the breakpoint #11807 https://github.com/pharo-project/pharo/pull/11807 Tests ===== - This adds an example and a test for Fluid Slot definitions #11786 https://github.com/pharo-project/pharo/pull/11786 Pharo10 ======= - Pharo10: CI: when getting pharo version/prefix on PR, do not use --first-parent #11785 https://github.com/pharo-project/pharo/pull/11785

Oct. 24, 2022

dubbing & subtitles on new MOOC

by Siemen Baader

Hi Stef & everyone interested in the MOOC(s), On Wed, Oct 5, 2022 at 9:09 PM stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > Since more than a year we have been working on a new mooc called: > âAdvanced Object-oriented Design and Developmentâ > > It will be quite good. We are bullet proofing it with a new lecture here > at Lille. > It will indeed - like the original one! ;) > The mooc will be produced in english (and may be dub in french). > Have you thought about using synthetic voices to autogenerate dubs in several languages from the subtitles? They have become quite good and it can be very seamless. Perhaps it will also be cheaper? cheers Siemen

Oct. 24, 2022

Re: About Bag API

by stephane ducasse

thanks clement. I was looking for at: while occurrencesOf: was it. Now I introduced removeKey: ifAbsent: and keys because they are missing. S > On 23 Oct 2022, at 16:49, ClÃ©ment Dutriez <dutriezcle(a)gmail.com> wrote: > > Hello Everyone, > > It also makes sense to me. > > the message `addAll: aCollection`, is defined in **Collection** object. > The behavior of addAll: is to add every object of the collection. > So every dev who learn pharo will understand `addAll: aCollection` message, add all object of the collection aCollection. > If you want to count a String just send an `add:` message to Bag object. > > Finally the behavior of the Pharo Bag seems similar to Python Counter Object [1]. > > I don't understand why you found this behavior strange. > > I hope it will help. > > [1] : https://docs.python.org/3/library/collections.html#collections.Counter <https://docs.python.org/3/library/collections.html#collections.Counter> > -- > Dutriez ClÃ©ment > > > Le dim. 23 oct. 2022 Ã 13:35, Sebastian Jordan Montano <sebastian.jordan(a)inria.fr <mailto:sebastian.jordan@inria.fr>> a Ã©crit : > For me it makes sense that in your example `aBag at: $a` returns `5` > > Because as you said, a Bag is for keeping occurrences. So, at: $a should return how many occurrences $a has > > Sebastian > > ----- Mail original ----- > > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> > > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org <mailto:pharo-dev@lists.pharo.org>> > > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > > Objet: [Pharo-dev] Re: About Bag API > > > it is because at: is in fact occurrencesOf: > > > > S > > > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr>> wrote: > >> > >> Hi > >> > >> I wonder why I cannot get values of a entry using at: > >> > >> | aBag | > >> aBag := Bag new. > >> aBag addAll: âaabbbacacccaâ. > >> aBag at: $a > >>>>> 5 > >> > >> I have the impression that this is because Bag API never got the correct amount > >> of love > >> but may be Iâm wrong. > >> > >> What is your opinion? > >> > > > S

Oct. 23, 2022

Re: About Bag API

by ClÃ©ment Dutriez

Hello Everyone, It also makes sense to me. the message `addAll: aCollection`, is defined in **Collection** object. The behavior of addAll: is to add every object of the collection. So every dev who learn pharo will understand `addAll: aCollection` message, add all object of the collection aCollection. If you want to count a String just send an `add:` message to Bag object. Finally the behavior of the Pharo Bag seems similar to Python Counter Object [1]. I don't understand why you found this behavior strange. I hope it will help. [1] : https://docs.python.org/3/library/collections.html#collections.Counter -- Dutriez ClÃ©ment Le dim. 23 oct. 2022 Ã 13:35, Sebastian Jordan Montano < sebastian.jordan(a)inria.fr> a Ã©crit : > For me it makes sense that in your example `aBag at: $a` returns `5` > > Because as you said, a Bag is for keeping occurrences. So, at: $a should > return how many occurrences $a has > > Sebastian > > ----- Mail original ----- > > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr> > > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > > Objet: [Pharo-dev] Re: About Bag API > > > it is because at: is in fact occurrencesOf: > > > > S > > > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> > wrote: > >> > >> Hi > >> > >> I wonder why I cannot get values of a entry using at: > >> > >> | aBag | > >> aBag := Bag new. > >> aBag addAll: âaabbbacacccaâ. > >> aBag at: $a > >>>>> 5 > >> > >> I have the impression that this is because Bag API never got the > correct amount > >> of love > >> but may be Iâm wrong. > >> > >> What is your opinion? > >> > > > S >

Oct. 23, 2022

Re: About Bag API

by Sebastian Jordan Montano

For me it makes sense that in your example `aBag at: $a` returns `5` Because as you said, a Bag is for keeping occurrences. So, at: $a should return how many occurrences $a has Sebastian ----- Mail original ----- > De: "Stephane Ducasse" <stephane.ducasse(a)inria.fr> > Ã: "Pharo Development List" <pharo-dev(a)lists.pharo.org> > EnvoyÃ©: Dimanche 23 Octobre 2022 09:27:45 > Objet: [Pharo-dev] Re: About Bag API > it is because at: is in fact occurrencesOf: > > S > >> On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: >> >> Hi >> >> I wonder why I cannot get values of a entry using at: >> >> | aBag | >> aBag := Bag new. >> aBag addAll: âaabbbacacccaâ. >> aBag at: $a >>>>> 5 >> >> I have the impression that this is because Bag API never got the correct amount >> of love >> but may be Iâm wrong. >> >> What is your opinion? >> > > S

Oct. 23, 2022

Re: About Bag API

by StÃ©phane Ducasse

it is because at: is in fact occurrencesOf: S > On 23 Oct 2022, at 11:26, stephane ducasse <stephane.ducasse(a)inria.fr> wrote: > > Hi > > I wonder why I cannot get values of a entry using at: > > | aBag | > aBag := Bag new. > aBag addAll: âaabbbacacccaâ. > aBag at: $a >>>> 5 > > I have the impression that this is because Bag API never got the correct amount of love > but may be Iâm wrong. > > What is your opinion? > > S

Oct. 23, 2022

About Bag API

by stephane ducasse

Hi I wonder why I cannot get values of a entry using at: | aBag | aBag := Bag new. aBag addAll: âaabbbacacccaâ. aBag at: $a >>> 5 I have the impression that this is because Bag API never got the correct amount of love but may be Iâm wrong. What is your opinion? S

Oct. 23, 2022