3 ms·

The problem is that developers have been brainwashed to dislike what Smalltalk has to offer. If you tell them to use a Smalltalk-like system they will complain

The problem is that developers have been brainwashed to dislike what Smalltalk has to offer. If you tell them to use a Smalltalk-like system they will complain to no end about the lack of file-centric infrastructure, while what Smalltalk has to offer is decades ahead of what they can do with other systems.

harha 4y ago
Any recommendations on where to get started to understand the idea behind it, where it’s used and how to approach typical problems?
rscho 4y ago
In a much less interactive manner, the Unison language seems like it revolves around some stuff found in Smalltalk
agumonkey 4y ago
market dynamics wiped lisp in the 80s, then smalltalk in the 90s such is life, it's gonna popup again in php10 or typescript5 for sure
TheAceOfHearts 4y ago
How is version control usually handled in these kinds of systems?
- melvinroest 4y ago
  <= Pharo 8: Monticello >= Pharo 9: Git (through something called Iceberg)
- throwawayForMe2 4y ago
  When I did Smalltalk in a corporate team environment we used a tool called Team/V. Code is stored in a shared repository. Everyone starts with the same clean image, loaded with the tools and options chosen for the project. From your clean running image, you open the Repository Browser window. You load app code from the repository, make changes etc., and commit back to the shared repository. There were many options for organizing “packages” and creating lists of packages and version numbers for a “build”. Also different options for ownership of code, locking code from changes, difference reports, etc. Open source tools I have not used.
urthor 4y ago
The problem is, what's the single best use case for Smalltalk? Web apps are too dominant, and the fact is much of backend engineering is mildly unsuitable for a dynamic language runtime due to raw performance. I think that's the issue. No golden use case like Ruby on Rails. If Apple supported Smalltalk for native iOS apps things would be fine. But pigs would fly first.

harha 4y ago

Any recommendations on where to get started to understand the idea behind it, where it’s used and how to approach typical problems?

rscho 4y ago

In a much less interactive manner, the Unison language seems like it revolves around some stuff found in Smalltalk

agumonkey 4y ago

market dynamics wiped lisp in the 80s, then smalltalk in the 90s such is life, it's gonna popup again in php10 or typescript5 for sure

TheAceOfHearts 4y ago

How is version control usually handled in these kinds of systems?

melvinroest 4y ago
<= Pharo 8: Monticello >= Pharo 9: Git (through something called Iceberg)
throwawayForMe2 4y ago
When I did Smalltalk in a corporate team environment we used a tool called Team/V. Code is stored in a shared repository. Everyone starts with the same clean image, loaded with the tools and options chosen for the project. From your clean running image, you open the Repository Browser window. You load app code from the repository, make changes etc., and commit back to the shared repository. There were many options for organizing “packages” and creating lists of packages and version numbers for a “build”. Also different options for ownership of code, locking code from changes, difference reports, etc. Open source tools I have not used.

urthor 4y ago

The problem is, what's the single best use case for Smalltalk? Web apps are too dominant, and the fact is much of backend engineering is mildly unsuitable for a dynamic language runtime due to raw performance. I think that's the issue. No golden use case like Ruby on Rails. If Apple supported Smalltalk for native iOS apps things would be fine. But pigs would fly first.