2 ms·
"Provably the most productive" seems to boil down to estimating that Smalltalk is more terse in statements per function point. Incidentally, by that metric Pyth
by prodigal_erik 10y ago
"Provably the most productive" seems to boil down to estimating that Smalltalk is more terse in statements per function point. Incidentally, by that metric Python is only half as productive as Visual Basic, which doesn't seem plausible. No comment about extra test coverage and prod bugs caused by lack of static typing.
"Image-based persistence" means your production-ready code and dinking around during prototyping (in a language with frictionless monkey-patching!) are all buried in one big mutable blob. It's often argued the impedance mismatch with version control is what killed Smalltalk.
- horrido 10y ago"It's often argued the impedance mismatch with version control is what killed Smalltalk." Wrong argument. Here's the truth: https://medium.com/smalltalk-talk/why-smalltalk-failed-to-dominate-the-world-93e7e4195039 https://medium.com/smalltalk-talk/why-smalltalk-failed-to-do... Smalltalk does have version control. It's just not the same version control software that everybody else uses (eg, Git, Subversion, etc.).