At ESUG, I gave a talk about the Glamorous Toolkit, and the talk is now online. We have announced the Glamorous Toolkit project two years ago at the same conference. On that occasion I argued that IDEs should have different properties than what typical IDEs have to offer today. Over the last two years, we introduced 4 significant tools inside Pharo, namely Inspector, Playground, Spotter, and Debugger, and in this talk I focused on how these tools can affect the way you think about programs and programming.
Please take a look, and let us know what you think.
We are very happy to make the following announcement:
Lam Research, a leading supplier of wafer fabrication equipment and services to the global semiconductor industry, is an experienced user of the Smalltalk programming language. Smalltalk is a key component in Lam's software control system for a broad range of the equipment it manufactures. Tudor Girba is a leading member of the tools and environment development effort in Pharo, having architected the Glamorous Toolkit for live programming. Eliot Miranda is author of the Cog virtual machine that underlies Pharo and other Smalltalk dialects.
Lam has engaged Tudor and Eliot to explore potential enhancements in Lam's use of Smalltalk. These enhancements range from running highly optimized Smalltalk on low cost, single board computers, to enhancing Lam's Smalltalk development practices with state-of-the-art live programming. During the engagement, Tudor and Eliot successfully moved a key communication component of the control system to Pharo. It was a challenging task aimed at extending the reach of Lam’s system to the Pharo world including the option of executing on ARM processors.
Cheers, Tudor Girba, Eliot Miranda and Chris Thorgrimsson
Posted by Tudor Girbaat 25 August 2016, 11:16 amlink
Over the last couple of weeks I worked on a new importer for Java code that can be used for Moose, and I am happy to announce that I released version 1.0.1.
jdt2famix is an open-source project, and the repository can be on Github. It is implemented in Java as a standalone project, and it is based on JDT Core (developed as part of the Eclipse project and available under the EPL2 license) and Fame for Java (originally developed by Adrian Kuhn and is available under the LGPL license).
The current implementation has an extensive coverage of entities that it can import, namely:
Go to the root folder where you have the sources and dependency libraries of a Java system (e.g., mysystem)
The result will be an MSE file having the same name as the name of the folder from which you executed the command (e.g., mysystem.mse).
Let’s look at a concrete example. For this purpose, we pick the Maven project. We first download the 3.3.9 sources. These are only the plain sources, but to be able to import the complete model, we also need to have the dependencies available in the same folder.
As Maven is a Maven project (no pun intended), we can use the configuration to download the dependencies locally:
Over the past year, I conducted an informal study on how developers think about code reading. The study took the form of a dialogue that I have with software engineers. I had it in various forms with more than 1000 engineers.
The dialog goes like this:
Me: I help teams to not read code. Engineer: Not to read code? Me: Yes. Engineer: Intriguing. What do you mean? Me: Well. Do you agree if I say that you spend 50% or more of your time reading code? Engineer: Hmm. Yes. Me: Ok. When was the last time you talked about it? Engineer: About what? Me: About how you read code? Engineer: Talk about reading code … I don’t remember … never? Me: In fact, nobody really talks about it. Is it not strange that we are spending most of our budget on something we never talk about? Engineer: Indeed. I never thought of it in this way … Me: I think we have to start talking about it. If we would talk about it we would see that we do not really want to read code. We want to understand code. Engineer: Right. Me: This means that reading is just the approach we employ. Yet, reading is the most manual way to retrieve information out of data. And our systems are just that: data. So, not only that code reading is expensive, it is also the least scalable approach. Engineer: Hmm… so, what is the solution? Me: The solution is to look at programmers at what they are: programmers. Their job is to automate someone else’s decision making and they can use exactly the skills they are paid for to improve their own decisions...
The amazing thing is that I encountered only minimal deviations from this dialogue regardless of the experience level, programming technology background, domain and even country of the interviewee.