[ann ] ODBC framework for Pharo

There is now an ODBC framework for Pharo, available at the pharo-rdbms github site:
https://github.com/pharo-rdbms/Pharo-ODBC
This is based on the Dolphin Smalltalk Database Connection ODBC framework. Provided a suitable driver manager is installed this should work on MacOS and Linux in addition to Windows. 
Thanks to InfOil for supporting the development, to Torsten for tidying up and hosting the code, and Andy and Blair (Dolphin developers) for the original framework.  
Regards,


John Aspinall

New company selling PharoJS products

Hi everyone,
I’m glad to announce a new Pharo-based commercial product: PLC3000 (https://plc3000.com).
It’s a SaaS solution for teaching PLC programming for factory automation. The server side is based on Zinc and the client side uses PharoJS.
This wouldn’t have been possible without the great work done by the community in large, and more specifically, the Pharo consortium. 
Thank you all,Noury

Progress report 2021/06/09

We are slowly moving on to a “ready to release” status, but there are still some tasks to do and in fact we have one new short term task. Still, it does not looks but we have improve the stability and the speed of integrations, which means an overall better life and status to move on :)Also, I splitted the short term goals in easier to messure tasks, so I can remove them 😉


Short-term goals:

– Improve quality and quantity of tests in StInspector 

– Improve quality and quantity of tests in StSpotter 

– Improve quality and quantity of tests in StPlayground

– Improve quality of class comments in Spec2 framework.

– Since we are in freeze mode: fixing important bugs on Pharo9 and its components (this issue will stay here until release).

– include M1 in PharoLauncher

– Remove pharo catalog from image


Medium-term goals:

– Removal of GTSpotter

– M1 VM release.

– Release 9.0


Long-term goals: 

– Removal of remaining GTTools

– Removal of Glamour- Removal if Spec1


## Last week
– ED (Emergency debugger) fixed (the UI was revamped to work on OSWindow and the SDL2 backend, in fact).

– Pass on Spec and NewTools repositories. Now development branches are called dev-1.0 and stable branch is “Pharo9.0” (will fit better the development cycle),

– Some enhancements in the new spotter

– For Spec, enhance tests in trees/lists/dropdowns.

– Stef added some improvements to microdown (Still for P10).

– Pablo made some fixes to the test runner- … and Marcus was busy fixing bugs and integrating PRs


### This week (starting 2021-06-07):


– Some final cleanups (GTSpotter and Catalog… yes, catalog is out because for now is better not having nothing that havign something that misslead people)

– Take care about some crashes in the new M1

– adapting PharoLauncher to download M1 VMs- more on PharoLauncher command line

Promote your Pharo project via the PharoProject Tweet account …

Tweeting all the interesting stuff is a lot of work.. if you released some library or wrote a blog post (or just found something interesting) where you think “that should be tweeted by @pharoproject”, now we have a submit link: https://app.apptivegrid.de/api/r/60a4dff49fcca3409b7e7248[9:53 AM](the link is in the “bio” of the twitter account, thus easy to find if needed)

Our journey to JIT and other beasts.

Since six months we are working different optimizations such as basic block introduction in CogIt, basic block reordering to maximise fallthrough and more recently we started to write tests and fix a bit the Scorch native optimizer developed by C. Béra.

This is an amazing way to learn a domain and I’m learning a lot. Our idea is to use scenario to assess the weak points of our infrastructure and to be able to fix it in the future. Our goal is to get a better Slang, a better and more flexible VM and nativizer. And step by step we are learning things that I would have never thought I would be learning, so this is an amazing and cool feeling.

During this journey we found strange logic in Slang (the VM generator), Clang’s bugs generating assembly code that we cannot even dissambled but for plain normal little C functions, extended the ARM back-end to support more exotic instructions than the JIT on such architecture. And recently we got some a surprising behavior on carry and underflow on ARM.

Most of the work is done by Guillermo Polito and I love spending days pair programming with him on that (I’m the lurker but learning lurker). Guille wrote a little anedocte on the carry behavior on ARM and I want to share it with you.https://thepharo.dev/2021/05/23/debugging-the-jit-compiler-hotspot-detection-for-arm64/

Stef (having fun with JIT and other beasts).

Pharo 90 is getting beta

Hi

After a long alpha version and a large list of enhancements and new exciting features, Pharo 90 is entering in beta freeze.

What does this means?

  1. No more features, just bugfixes
  2. No more fixes of things that can wait until Pharo 10

In two/three weeks we will open the Pharo 10 development branch, up to then, please help fixing what’s important for Pharo 90! We tagged the issues to reflect such information (Milestones + importance).

The Pharo crew

Advanced stepping with the new Pharo debugger

The new Pharo debugger is getting exciting after object-centric features we can now define our own commnands https://thepharo.dev/2021/04/28/advanced-stepping-and-custom-debugging-actions-in-the-new-pharo-debugger/

Well done

JIT VM for M1 beta testers

Hi

Just read on discord that you can download now the new ARM64 JIT vm in that machine. Just need to do

wget -O - get.pharo.org/90+vm | bash

S.