Still, it just occurred to me that one could use integration with scm like git or mercurial to get the same kind of benefit as the Smalltalk change log+image.
What if every change to a function was snapshotted, and the developer could easily scroll/flip through these snapshots? Merging the change back to a main branch would then be like image saving in Smalltalk. This would give developers the ability to try really risky development, since they would always be able to quickly get back to a previous state.
(This can already be done, but by making the integration really seamless, it has a synergistic effect with development.)
But you should disable them by default, they are confusing!
Edit: Why the downvote(s)?
It's not your fault, but YouTube's. I just find computer generated gibberish funny.
It may be computationally impractical though.
So good transcriptions would be good, regardless of the noise environment. It might give some false positives, but I expect that a good price to pay to avoid the kind of mess they create now.
For example, the difference between "its" and "it's", "red" and "read", "know" and "no" is irreconciliable without understanding the rest of the sentence these trouble words appear in.
What I'm proposing is to pass the output of speech recognition through a binary classifier that answers the question "is this text gibberish?", which is trained with the help of a textual language model, unrelated to the speech recognition pass.
Sorry, I've been a professional in Smalltalk since 1998, and I've never encountered a corrupted image. The closest thing I've seen to that is de-sync with source code. (Which you don't care much about if you're using SCM, for the same reasons everyone else uses SCM.)
stateful (wtf were they thinking?) web-apps.
Same things others were thinking at the time -- you're just seeing a slice of history. People still rave over the debugging in Seaside like it's magic, though.
Typing `C-c p d b` in my Emacs inserts this macro:
import sys; sys.stdout = sys.__stdout__; import ipdb; ipdb.set_trace()
All the benefits of a Lisp REPL and a Smalltalk debugging environment in a language people actually use. Tab-completion, dumps, breakpoints, testing assumptions/data, running arbitrary code inside a specific environ...the works.
I can use it in my virtualenvs without having to explain to an IDE what a virtualenv, a running test in Nose, a normal script, or a running web server. It's normal code so I can wrap the trace in a condition or whatever else I want.
Sometimes I toss stuff out there in the hopes of being shown something better. It's teaches me new things.
Lets take a moment to think on our poor brethren still tossing print statements all over the place though.
Also let me take another moment to call you out on the "corrupted image" BS.
Yes but, want what? What does my little ipdb snippet not do that you want?
Oh, and let me take another moment to call you out for your "corrupted image" BS.
(I've often said around here that things would've worked out better if there wasn't such a barrier between stuff happening in Smalltalk and outside in the OS -- community wise. But if you're willing to play just in the Smalltalk sandbox, it's a pretty awesome experience.)
I've only used Smalltalk/V during university, back in 1995, if memory serves me right.
I've seen integration problems migrating code between implementations, lack of proper support for source control specially in distributed teams, lack of integration with the operating system for desktop applications.
I know that many of these problems have been solved in newer implementations, but maybe now it is too late.
I have been using it daily for a few months now, it's a bit like re-discovering coding because it's just way more fun to code with it.
And I will definitely consider creating a Kickstarter project.
# List your project dependencies here.
# For more details, see:
then people might try out your software more easily.
"Nope, that's a bad idea right there in you thoughts."
"WARNING: Usage of public pools during hot weather is deprecated. Misuse may lead to a degradation of your insurance policy. At short-term-alpha memory, synapse group #23AE18-123, phase shift 3"