- Esug-list - lists.esug.org

Job offer at RMOD around Moose
by Stéphane Ducasse Jan. 14, 2020

Jan. 14, 2020

Hello We got a two years position as engineer in our team. We should do the administration to declare it in our lovely hiring tool. But I wanted to let you know that we have this position and that it can interest some of you. The goal is to work on the new moose IDE and develop some tools for the team and companies. The follow up can also be to participate to start-up program. S. -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

OpenQwaq python bridge
by Jan Vrany Jan. 2, 2020

Jan. 2, 2020

Hi there, does anyone know how OpenQwaq's Python bridge was/is implemented? Does it use a VM plugin/ffi to interact with Python runtime? If yes, does anyone know if sources are available (under some usable license)? If so, where can I find them? My google-fu failed me, as usual. All the best in 2020! Jan

2 2

Re: [Esug-list] OpenQwaq python bridge
by Jan Vrany Jan. 2, 2020

Jan. 2, 2020

Hi Tobias > > If so, where can I find them? My google-fu failed me, as usual. > > Have you tried https://github.com/itsmeront/openqwaq ? > License is GPLv2 No, and this is indeed what I was looking for. Thanks a lot! Best, Jan

1 0

‹Programming› 2020 : Call for Participation
by Fabio Niephaus Dec. 8, 2019

Dec. 8, 2019

‹Programming› 2020 : The Art, Science, and Engineering of Programming March 23-26, 2020, Porto, Portugal https://2020.programming-conference.org The International Conference on the Art, Science, and Engineering of Programming is a new conference focused on programming topics including the experience of programming. We have named it ‹Programming› for short. The conference is co-located with several workshops, a poster and a demo session, a Coding Dojo, and the student research competition. Keynote ------- Guy L. Steele Jr. (Oracle Labs) Workshops --------- Convivial Computing Salon https://2020.programming-conference.org/home/salon-2020 ENIAC’20 https://2020.programming-conference.org/home/eniac-2020 ICW https://2020.programming-conference.org/home/icw-2020 MoreVMs’20 https://2020.programming-conference.org/home/MoreVMs-2020 NIP https://2020.programming-conference.org/home/nip-2020 PX/20 https://2020.programming-conference.org/home/px-2020 ProWeb’20 https://2020.programming-conference.org/home/proweb-2020 CoCoDo 2020 https://2020.programming-conference.org/home/cocodo-2020 Tutorials --------- https://2020.programming-conference.org/track/programming-2020-tutorials AntidoteDB : Just the Right Kind of Consistency! Bela Workshop Learning Haskell: a project-based approach Meta-Programming for the masses PharoIoT ******************************************************** ORGANIZATION ******************************************************** General Chair Ademar Aguiar, Universidade do Porto Program Chair Stefan Marr, University of Kent Organizing Committee https://2020.programming-conference.org/committee/programming-2020-organizi… Program Committee https://2020.programming-conference.org/committee/programming-2020-papers-p… ******************************************************** SUPPORTERS ******************************************************** ACM In-Cooperation Universidade do Porto City of Porto AOSA ******************************************************** For more information, visit https://2020.programming-conference.org

1 0

Postdoc "Advanced and extendable tools and virtual machines for debugging"
by Stéphane Ducasse Dec. 7, 2019

Dec. 7, 2019

Hello, we have an open post-doc position in the RMoD team, Inria Lille - Nord Europe on the following topic: Advanced and extendable tools and virtual machines for debugging. Level of qualifications required : PhD or equivalent Starting date : ASAP Duration of contract : 1 year, 6 months Town/city : Villeneuve d'Ascq Inria Center : CRI Lille - Nord Europe <http://www.inria.fr/centre/lille> To apply: https://jobs.inria.fr/public/classic/en/offres/2019-02204 <https://jobs.inria.fr/public/classic/en/offres/2019-02204> Contact: Steven Costiou, steven.costiou(a)inria.fr <mailto:steven.costiou@inria.fr> Stéphane Ducasse, stephane.ducasse(a)inria.fr <mailto:stephane.ducasse@inria.fr> Please find the detailed job offer below and attached to this mail. Best Regards, ----------- Steven Costiou Researcher, RMoD/Inria https://kloum.io/costiou/ <https://kloum.io/costiou/> =========Detailed job offer========= Context Debuggers are applications that users use to debug other applications. Lots of tools provide users with a large variety of debugging capabilities. However several aspects of the debugging activity are poorly covered by scientific and technical state-of-the-art. For example, it is still very hard to debug concurrent or parallel systems. It is also not very clear how to implement advanced debugging tools such as back-in-time debuggers, or what support should a run-time infrastructure (e.g., a virtual machine) provide for advanced debugging. Finally, often tools are inflexible and cannot be adapted to specific domain or projects. New generation tools should not only support the developers customising tools to their own workflow and domain, but also be dynamically activated even if the virtual machine does not support them. Therefore, virtual machines should also be extendable with new, user-defined primitives and support for debugging. Results will be submitted to international conferences and journals and an effort will be put to produce systems that can be used by (normal) developers so that user experiences provide real data. The work will happen in collaboration between Inria Lille (RMOD team) and Vrije Universitat Brussels (SOFT lab). Assignment Objectives The goal of this Postdoc is to build new advanced debuggers to explore and experiment one or more of the following topics: Back-in-time and scriptable debuggers How to build back-in-time debuggers? What abstractions do we need to take advantage of back-in-time debuggers? (scripting, DSLs…) How can users extend, customise and enhance their debugger?   (following PhD of A. Chis on Moldable Tools and the work of T. Dupriez on scriptable debuggers) Extendable virtual machines for advanced debugging support What primitives do we need from the virtual machine to support advanced debugging tools?   (back-in-time debuggers, object-centric debuggers, etc.) How can users create new debugging primitives and enable them on-demand when a particular bug happens and requires investigation without restarting the program?  Advanced debuggers for concurrency How can we track specific objects in a concurrent execution and how this capability helps in debugging concurrent programs?   (following the PhD of S. Costiou on unanticipated object-centric debugging) What are and how to express object-centric debugging queries on the flow of objects, shared by concurrent processes? Can we leverage Dynamic Software Update techniques to safely instrument running concurrent programs with advanced debugging instrumentation?  (following the PhD of P. Tesone on DSU for live and production environments)  Support for debugging tools Can we use type inferencers to ease the design of debugging tools and limit their impact on performance and memory on dynamic languages runtimes? (following work on RoelTyper and PhD of L. Spoon on type inference) References: Thomas Dupriez, Guillermo Polito, Steven Costiou, Vincent Aranega, and Stéphane Ducasse. 2019. Sindarin: a versatile scripting API for the Pharo debugger. In Proceedings of the 15th ACM SIGPLAN International Symposium on Dynamic Languages (DLS 2019). Pablo Tesone, Guillermo Polito, Noury Bouraqadi, Stéphane Ducasse, Luc Fabresse. Dynamic Software Update from Development to Production. The Journal of Object Technology, Chair of Software Engineering, 2018 Steven Costiou, Mickaël Kerboeuf, Alain Plantec, and Marcus Denker. 2018. Collectors. In Conference Companion of the 2nd International Conference on Art, Science, and Engineering of Programming (Programming'18 Companion). Matteo Marra, Elisa Gonzalez Boix, Steven Costiou, Mickaël Kerboeuf, Alain Plantec, Guillermo Polito, and Stéphane Ducasse. 2017. Debugging Cyber-Physical Systems with Pharo: An Experience Report. In Proceedings of the 12th edition of the International Workshop on Smalltalk Technologies (IWST '17). A. Chis, T.Girba, Tudor and O. Nierstrasz, The Moldable Debugger: A Framework for Developing Domain-Specific Debuggers, Software Language Engineering, 2014. Lienhard, Girba, Nierstrasz: Practical Object-Oriented Back-in-Time Debugging, Proceeding ECOOP '08. Proksch, Sebastian ; Lerch, Johannes ; Mezini, Mira : Intelligent Code Completion with Bayesian Networks. http://doi.acm.org/10.1145/2744200 <http://doi.acm.org/10.1145/2744200> ACM Transactions on Software Engineering and Methodology (TOSEM), 25 (1) 3:1-3:31. 2015 C. Hofer, M. Denker and S. Ducasse, Design and Implementation of a Backward-In-Time Debugger, Node 06, 2006. S. A. Spoon and O. Shivers, Demand-Driven Type Inference with Subgoal pruning: Trading Precision for Scalability, Proceedings of ECOOP'04, 2004 Main activities The plan is to: Join the team work around debugging, that includes 3 researchers and 1 phd student Survey the key developer activities Define new model and enhance current Realize prototypes, possibly using Pharo Run validation with real end-users Publish results in top venues Skills Technical skills and level required OOP, TDD Reflective programming Program transformation Language English Relational skills Good team work skills Other valued appreciated Knowledge of the Pharo language is a plus A strong interest about debugging and/or dynamic languages is also appreciated Benefits package Subsidized meals Partial reimbursement of public transport costs Leave: 7 weeks of annual leave + 10 extra days off due to RTT (statutory reduction in working hours) + possibility of exceptional leave (sick children, moving home, etc.) Possibility of teleworking (after 6 months of employment) and flexible organization of working hours Professional equipment available (videoconferencing, loan of computer equipment, etc.) Social, cultural and sports events and activities Access to vocational training Remuneration Gross monthly salary (before taxes) : 2 653 RMOD ==== The goal of RMoD is to support remodularization and development of modular object-oriented applications. We tackle this objective from two complementary perspectives: reengineering, and constructs for dynamic languages. In the context of languages, we revisit language concepts such as modules and composition; we are also working on a new generation of reflective systems. We experiment with these programming constructs using Pharo, an open source, reflective, object-oriented language. http://rmod.inria.fr <http://rmod.inria.fr/> About the research centre or Inria department The Inria Lille - Nord Europe Research Centre was founded in 2008 and employs a staff of 360, including 300 scientists working in sixteen research teams. Recognised for its outstanding contribution to the socio-economic development of the Hauts-De-France région, the Inria Lille - Nord Europe Research Centre undertakes research in the field of computer science in collaboration with a range of academic, institutional and industrial partners. The strategy of the Centre is to develop an internationally renowned centre of excellence with a significant impact on the City of Lille and its surrounding area. It works to achieve this by pursuing a range of ambitious research projects in such fields of computer science as the intelligence of data and adaptive software systems. Building on the synergies between research and industry, Inria is a major contributor to skills and technology transfer in the field of computer science. -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

Designing a Visual Enviroment (potentially with Pharo)
by Stéphane Ducasse Nov. 30, 2019

Nov. 30, 2019

Hi guys Please distribute widely > "VisualArc, an SF-based startup, is looking to hire a team to build a next-generation visual programming environment using Smalltalk. The intention behind the company is to make programming much easier to learn through data visualization, and we are targeting enterprises who are teaching employees how to program. We are primarily looking for a technical co-founder / CTO at the moment, but we are open to speaking with anyone who might be interested in working on this project. If you are interested in Smalltalk, visual programming, data visualization or programming education, we would love to hear from you! If you would like to learn more about this project, email VisualArc CEO Bobby Lancaster at bobby.lancaster(a)gmail.com <mailto:bobby.lancaster@gmail.com>. Stef -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

1 0

ECOOP'20 Berlin - Call for Papers
by Fabio Niephaus Nov. 29, 2019

Nov. 29, 2019

============================================================ The 34th Edition of ECOOP Call for Papers 13th-17th July 2020 Berlin, Germany https://2020.ecoop.org/ ============================================================ ECOOP is a conference about programming. Originally its primary focus was on object orientation, but now it looks at a much broader range of programming topics. Areas of interest include, at least, the design, implementation, optimization, analysis, and theory of programs, programming languages, and programming environments. It solicits both innovative and creative solutions to real problems as well as evaluations of existing solutions—evaluations that provide new insights. It also encourages the submission of reproduction studies. ECOOP 2020 solicits high-quality submissions describing original, unpublished results. The program committee will evaluate the technical contribution of each submission as well as its general relevance and accessibility to the ECOOP audience according to the following criteria: - Originality. Papers must present new ideas and place them appropriately within the context established by previous research in the field. - Significance. The results in the paper must have the potential to add significantly to the state of the art or practice. - Evidence. The paper must present evidence supporting its claims. Examples of evidence include implemented systems, experimental results, statistical analyses, case studies, formalizations, and proofs. - Clarity. The paper must present its contributions and results clearly. On submission, authors will be asked to identify their paper with one of the following categories: - Research Paper. This is the most traditional category and solicits high quality research papers that demonstrate advances in the field. (As an alternative to being published in the conference proceedings, authors may wish to submit research papers to be considered for publication in ACM TOPLAS or Science of Computer Programming.) - Tool Insights Paper. These submissions focus on the practical details of the design and implementation of PL tools—details that are often omitted from regular research papers, despite being fascinating and worthy of communication. A strong Tool Insights Paper should communicate engineering experience and insights that are likely to be useful to other members of the PL community, who may face similar problems in future. Examples of issues that Tool Insights Papers might focus on include, but are not limited to: performance, reliability, portability, inter-tool integration, infrastructure re-use, evaluation issues, theory/practice gaps, precision/efficiency, and soundness/efficiency trade-offs. - Reproduction Study. A Reproduction Study is an empirical evaluation. It reconstructs an already published experiment but in a different context (for example, using a different virtual machine or platform, or in a different class of applications) in order to validate or refute important results of earlier work. A good Reproduction Study includes thorough empirical evaluation as well as a detailed comparison with the previous results, providing reasons for possible disagreements. (A thoroughly-conducted Reproduction Study that perfectly replicates an existing experiment and reaches the same conclusions will be regarded as significant, so long as said experiment is significant enough to be worthy of reproduction.) - Experience Report. Such reports focus on noteworthy applications of known PL techniques, tools, and ideas in interesting domains and by other communities. Examples include, but are not limited to, applications of PL techniques in industry, open source, education, and other academic disciplines. We welcome reports on successful applications of PL ideas and reports that shed light on limitations and problems that may provide inspiration for future research. - Pearl. This category solicits articles that explain a known idea in a new and elegant way, to the benefit of the PL community. A Pearl may well be shorter than a regular research paper, but there is no hard requirement on this. - Brave New Idea. The Brave New Idea category solicits forward-looking articles on ideas in the field of PL that may take some time to substantiate, but for which early communication to the community is likely to be of benefit. For this category we welcome papers that are particularly conceptually novel or unconventional and that as a result may be harder to back up by traditional evaluation methods. A Brave New Idea paper may well be shorter than a regular research paper, but there is no requirement for it to be so. Paper Submission ================ Only papers that have not been published and are not under review for publication elsewhere may be submitted. Double submissions will be rejected without review. If major parts of an ECOOP submission have appeared elsewhere in any form, authors are required to notify the ECOOP program chair and explain the overlap and relationship. Authors are also required to inform the program chair about closely related work submitted to another conference while the ECOOP submission is under review. Papers must be no longer than 25 pages, excluding references. See below for information about appendices. Authors will not be penalized for papers that are shorter than the page limit. Submissions will be carried out electronically via the conference website [1]. ECOOP Proceedings are published by Dagstuhl LIPIcs. Papers must be written in English and follow the Dagstuhl LIPIcs LaTeX-style template [2]. Authors retain ownership of their content. Note: Submitted papers do not need to include the ACM classification or keywords. Also, please DO NOT put your name in either the \author or \Copyright macro, in order to maintain anonymity for double-blind reviewing (see below). Anonymity ========= ECOOP will use light double-blind reviewing: authors’ identities are withheld until a reviewer submits his or her review (as usual, reviews are anonymous). To facilitate this, submitted papers must adhere to two rules: - Author names and institutions must be omitted. - References to authors’ own other work should be in the third person (for example, not “We build on our previous work…” but rather “We build on the work of…”). When in doubt, contact the Program Chair. Additional Material =================== Clearly marked additional appendices containing analyses, statistics, supporting proofs, etc. of possible value to reviewers but not published in the final publication, may be included beyond the page limit. The submission system provides an option to submit supplementary material; for example, a technical report including proofs, or web pages and repositories that cannot easily be anonymized. This supplementary material will be made available to reviewers after the initial reviews have been completed, when author names are revealed. Reviewers are under no obligation to examine such appendices and supplementary material. Therefore, the paper must be a stand-alone document - the appendices and supplementary material are a way of providing useful information that cannot fit in the page limit; they are not a means to extend the page limit. Authors of papers that have been submitted but not accepted by previous conferences may optionally submit a Note to Reviewers. The Note to Reviewers should provide the following information: - the identity of the previous venue(s) (for example, ESOP 2020, ‹Programming› 2020, POPL 2020, OOPSLA 2019) - a list the major issues identified by the reviews at those venues - a description of the changes made to the paper in response to those reviews These notes will be made available to reviewers after their initial reviews have been completed and author names have been revealed. Response Period =============== Authors will be given a three-day period to read and respond to the reviews of their papers before the program committee meeting. Responses have no formal length limit, but concision is likely to be effective. Artifact Evaluation =================== To reward the creation of artifacts and support replication of experiments, authors of accepted research papers may submit artifacts (such as tools, data, models, or videos) to be evaluated by an Artifact Evaluation Committee. Artifacts that pass muster will be recognized officially. Important Dates =============== - Paper submission: 10 January 2020 (Fri) - Author response: 16–18 March 2020 (Mon-Wed) - Author notification: 8 April 2020 (Wed) Journal First ============= We have Journal First arrangements with ACM Transactions on Programming Languages and Systems and Elsevier Science of Computer Programming. Common to both routes --------------------- Only new research papers are eligible for the Journal First routes to ECOOP 2020. That is, it is not acceptable to submit an extension of a previous conference paper, even if the associated journal solicits extended papers via its standard submission route. Authors of all accepted Journal First papers will be invited to submit a short abstract for their paper to appear in the ECOOP 2020 conference proceedings. Journal First papers will be included along with research papers submitted directly to the conference when a Distinguished Paper is selected. Science of Computer Programming route ------------------------------------- See this dedicated web page [3] for full details of how to submit to the ECOOP 2020 Science of Computer Programming (SCP) special issue. Submission deadline: December 2, 2019 (Mon) ACM Transactions on Programming Languages and Systems route ----------------------------------------------------------- See this announcement [4] for details of the TOPLAS scheme whereby papers submitted to TOPLAS can be presented at selected conferences. Authors interested in this route should submit their paper to TOPLAS via its usual submission system and mark it as an ECOOP 2020 submission. The ECOOP Program Chair will then be informed of this submission and will have some input into the review process. Submission deadline: October 10, 2019 (Thu) More Information ================ For additional information, please contact the ECOOP Program Chair, Robert Hirschfeld [5]. [1] https://2020.ecoop.org/track/ecoop-2020-papers [2] https://www.dagstuhl.de/en/publications/lipics/instructions-for-authors/ [3] https://www.journals.elsevier.com/science-of-computer-programming/call-for-… [4] https://toplas.acm.org/announcements.cfm#submit-a-paper-for-pldi-2016 [5] https://www.hpi.uni-potsdam.de/hirschfeld/people/hirschfeld/

1 0

Smalltalk meetup end of January?
by Alexandre Bergel Nov. 28, 2019

Nov. 28, 2019

Dear Smalltalkers, A nice delegation of Smalltalkers from Chile and Bolivia will be in San Francisco and the Bay Area at the end of January 2019. We are currently sensing the Smalltalk community to organize a meetup. The goal is to meet, discuss about Smalltalk, do some presentations, demonstrations, and have fun. We have prepared a google form for people interested in it: https://forms.gle/aZ4z5T7nvXttw5Rj6 If you feel like to meet, then please answer before Wednesday 4, December 2019. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.

1 0

ESUG 2020 Novisad 31.8. – 4.9.
by Stéphane Ducasse Nov. 26, 2019

Nov. 26, 2019

Dear Friends we are happy to confirm that ESUG will happen in NoviSad from 31.8. – 4.9. 2020 S. -------------------------------------------- Stéphane Ducasse http://stephane.ducasse.free.fr / http://www.pharo.org 03 59 35 87 52 Assistant: Julie Jonas FAX 03 59 57 78 50 TEL 03 59 35 86 16 S. Ducasse - Inria 40, avenue Halley, Parc Scientifique de la Haute Borne, Bât.A, Park Plaza Villeneuve d'Ascq 59650 France

4 6

Fwd: VAST (VA Smalltalk) Version 9.2 Now Available!
by Mariano Martinez Peck Nov. 22, 2019

Nov. 22, 2019

FYI. ---------- Forwarded message --------- From: Instantiations, Inc. <info(a)instantiations.com> Date: Fri, Nov 22, 2019 at 3:00 PM Subject: VAST (VA Smalltalk) Version 9.2 Now Available! To: <marianopeck(a)gmail.com> Experience the faster JIT-based virtual machines along with dozens of other enhancements. [image: Instantiations Logo] [image: VAST (VA Smalltalk) Version 9.2] *VAST 9.2 Now Available!* The latest version of VAST has dozens of new features and enhancements including: - Significantly faster virtual machines with just-in-time (JIT) compilers - HiDPI support for Windows® - Fully featured SMTP/IMAP support - Native PostgreSQL driver *See full list below* *Free upgrades to VAST 9.2 for customers with active support subscriptions. Fully functional free trials are available for evaluating VAST.* VAST (VA Smalltalk) continues to be compatible with IBM® VisualAge® for Smalltalk. Make upgrades fast and easy using the latest migration guide <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> . Download VAST 9.2 <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> *What's New in VAST 9.2?* Major performance increase with all new just-in-time (JIT) compiler for 32 and 64-bit virtual machines! - *Platform*: - AArch64 joins the ARM family lineup* - Major FFI performance increases - Support for returning struct-by-value in FFI - Transitioned to latest Clang compiler for Windows - Updated LLVM code generator - Walkback generator provides more useful information and pluggability - Updated virtual machine C-interface - *Base Libraries*: - CSV support - STON support - Many APIs added for dialect portability - *Graphics*: - Full HiDPI support on Windows - Scintilla editor fonts use DirectWrite (GPU-accelerated rendering) by default - 20x speedup in PNG reading - PNG interlaced frame handling support - Updated look-and-feel of the Windows application icon, *Environments* banner, and splash screens - *Unicode*: - Kernel-level EsCodePageUtilities with enhanced Unicode conversion - Seaside Unicode updates - Grease UTF-8 enhancements - Iconv updates for Unix - Zip streams UTF-8 support for file names and comments - *Compression*: - Brotli compression streams - ZStandard compression streams - *Communications*: - New IMAP client - New SMTP client - SASL authentication framework - Mail examples - SstHttpClient support for HTTP requests (PUT, DELETE...) - Absolute/relative redirect support for SstHttpClient - SNI support for SstHttpClient - Seaside improvements - *Security*: - LibreSSL compatibility - Probabilistic Signature Schemes (RSA-PSS) - Server name indication support - *Databases*: - Native PostgreSQL driver - PostgreSQL database abstraction layer integration - GLORP updates - *Development Tools*: - Cross-development enhancements (XD) - SstDebugger now supports reading .sdf files - MonticelloImporter loading enhancements - SUnit enhancements - *EMSRV*: - Improvements to PAM authentication - *Deployment*: - Dynamic packaging rules using static code analysis for warning reduction - Significant reduction of packaging warnings on shipped apps - Seaside packaging works out-of-the-box - *VAST Environments Launcher*: - Copy installations to new location - Move *Environments* to a new location - Default editor/file explorer identifier for Linux - *Documentation*: - Seaside headless packaging examples in server guide - Stack dumping and remote debugging with Seaside documentation - Updated migration guide - *Research/Development and Open Source Projects*: - TensorFlow machine learning for VAST (tensorflow-vast on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Git support for VAST with Tonel interchange (tonel-vast on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Git/Tonel examples (tonel-demos on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Docker examples (docker-examples on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Pigpio bindings for VAST (pigpio-vast on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Pharo to VAST porting tool (pharo2va on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) - Eclipse MQTT Paho client for VAST (paho-mqtt-vast on Github <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> ) **Beta feature: contact us for more details* *Read More:* VAST 9.2 Full Documentation <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> VAST 9.2 Data Sheet <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> Download VAST 9.2 <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> [image: Follow us on LinkedIn.] <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> [image: Follow us on Twitter.] <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> [image: Follow us on GitHub.] <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> [image: Subscribe on YouTube] <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> Google Groups Forum <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> instantiations.com <https://instantiations.us2.list-manage.com/track/click?u=40d53f69de264c389f…> © 2019 Instantiations, Inc. All rights reserved. All product names, trademarks, and registered trademarks are property of their respective owners. All company, product, and service names are used for identification purposes only. Use of these names, trademarks, and brands does not imply endorsement. Instantiations, Inc. 4917 Waters Edge Drive Suite 268 Raleigh, NC 27606 Add us to your address book <https://instantiations.us2.list-manage.com/vcard?u=40d53f69de264c389f24ea8e…> Want to change how you receive these emails? You can update your preferences <https://instantiations.us2.list-manage.com/profile?u=40d53f69de264c389f24ea…> or unsubscribe from this list <https://instantiations.us2.list-manage.com/unsubscribe?u=40d53f69de264c389f…> . -- Mariano Martinez Peck Email: marianopeck(a)gmail.com Twitter: @MartinezPeck LinkedIn: www.linkedin.com/in/mariano-martinez-peck <https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/> Blog: https://marianopeck.wordpress.com/

1 0