Smalltalk VS git-sizer

• Pure Object-Oriented Language
  Smalltalk is consistently object-oriented. Everything is an object, including primitive operations, which simplifies the mental model for developers.
• Interactive Development Environment
  Smalltalk offers a rich, dynamic development environment with tools for live code updates and immediate feedback, enhancing productivity and experimentation.
• Simple Syntax
  The language has a small and easily understandable syntax, which makes it more accessible to beginners and allows developers to focus more on problem-solving.
• Dynamic Typing
  Smalltalk's dynamic typing allows for flexible coding and polymorphism, making it easy to write generic and reusable code components.
• Mature and Influential
  As one of the oldest object-oriented languages, Smalltalk has a rich history, influencing many modern languages like Java, Ruby, and Python.

Possible disadvantages

• Performance
  Smalltalk can suffer from slower performance due to its high level of abstraction and dynamic typing, which may not be suitable for compute-intensive applications.
• Niche Community
  The Smalltalk community is relatively small compared to more mainstream languages, which can limit resources, libraries, and support available for developers.
• Learning Curve
  While the syntax is simple, Smalltalk's unique development environment and paradigms can introduce a learning curve for developers coming from other languages.
• Limited Integration
  Interfacing Smalltalk with non-Smalltalk systems can be challenging, limiting its use in mixed technology environments without proper bridging mechanisms.
• Dynamic Typing Drawbacks
  While flexible, dynamic typing can also lead to runtime errors that are not caught at compile time, potentially making debugging more difficult.

• Comprehensive Repository Analysis
  git-sizer analyzes many different dimensions of a Git repository including commit count, tree size, blob size, history depth, and reference counts, providing a holistic view of repository health and potential scaling issues.
• Easy to Use
  The tool is simple to run with minimal setup—just execute it within a git repository—and it produces clear, human-readable output that highlights potential problem areas without requiring complex configuration.
• Identifies Performance Bottlenecks
  It helps identify specific issues that could degrade Git performance, such as excessively large blobs, deep history, large trees, or too many references, which is valuable before migrating or scaling repositories.
• Open Source and Maintained by GitHub
  Being an official GitHub project, it benefits from credibility, community trust, and ongoing maintenance, and it is well documented with clear explanations of what each metric means.
• Useful for Pre-Migration Checks
  It's particularly helpful for teams migrating repositories to new platforms or consolidating repos, as it flags potential issues that could cause problems during migration or with hosting providers' limits.

Possible disadvantages

• No Automatic Remediation
  git-sizer only identifies and reports issues but does not offer any built-in tools or automated processes to fix problems like large blobs or excessive history depth—users must use separate tools like BFG Repo-Cleaner or git-filter-repo.
• Output Can Be Overwhelming for Beginners
  While detailed, the output includes many metrics and threshold levels that may be confusing for users unfamiliar with Git internals, requiring some learning curve to fully interpret results.
• Limited to Local Analysis
  The tool analyzes a local clone of the repository, so it requires users to have a full local copy of the repo (or at least enough history) to get accurate results, which can be time-consuming for very large repositories.
• No Real-Time Monitoring
  It functions as a one-time analysis tool rather than providing continuous or real-time monitoring of repository health, requiring manual reruns to track changes over time.
• Command-Line Only Interface
  The tool lacks a graphical user interface, which may be less accessible for users who prefer visual dashboards or are less comfortable with command-line tools.

No analysis of Smalltalk yet.

• Old version of offline Scratch that had a secret OS

  Also, it's not really an "operating system", nor was it implemented by the ST. It's just part of Squeak (you got the name right), the "engine" Scratch 1.x was made with (which lets you edit the code in the same window it's running in). Source: over 3 years ago

• Ask HN: Alternatives to organizing code in files and folders?

  Just downloaded https://squeak.org/ to play around with this concept. I wonder if there is already a modern tool/suite for Node/Python inspired by Smalltalk... - Source: Hacker News / over 3 years ago

• What are some important differences between the popular versions of OOP (e.g. Java, Python) vs. the purist's versions of OOP (e.g. Smalltalk)?

  AFAIK the major SmallTalk distributions are https://squeak.org/ and https://pharo.org/. I've heard that Pharo is more complex and "practical", while Squeak is more educational and beginner-friendly. But both stick to their roots with... Source: over 3 years ago

View more

• how to keep github repos small?

  Also there’s a cool project from GitHub you can use to help understand the size of git’s objects in your git repo https://github.com/github/git-sizer. This might help you determine what the best cloning strategy could be. Source: almost 5 years ago