Oh, and yes, image-based programming was a total lose. I think of it as the "ball of mud" paradigm. Proper layering and abstraction isn't some horrid side effect of using "inferior" languages, it's a vital thing for architecting systems in the large.
-
-
Replying to @perrymetzger @StephenPiment
Image-based programming is a great win versus ten hours to initialize hello world on the JVM or .NET.
2 replies 0 retweets 3 likes -
Replying to @Ngnghm @StephenPiment
It's also a win vs. running all your code under OS/360. You realize you're damning with faint praise.
2 replies 0 retweets 0 likes -
Replying to @perrymetzger @StephenPiment
You miss the point of images. They are a different paradigm. See Dick Gabriel's essay on the Incommensurability of the systems paradigm and the programming languages paradigm. Lisp is all about systems.
1 reply 0 retweets 1 like -
Replying to @Ngnghm @StephenPiment
I'm aware of the arguments for them. They were a good idea and a worthy experiment. My opinion is that, in practice, they break modularity and abstraction too much. I note that many capability systems ended up failing for similar reasons (but see Capsicum for an exception.)
3 replies 0 retweets 0 likes -
idk, from a certain POV browsers are image-based, plenty wrong with them but not the image part, so is Emacs which has worked for me decades. I love types and all but for some use cases there's no substitute for something like Pharo. Plenty of examples out there if you look.
2 replies 0 retweets 6 likes -
Replying to @deech @perrymetzger and
A case could be made that PostGres also qualifies and is very successful. AFAICT a large % of the web dev's stack consists of images and making them talk to each other.
2 replies 1 retweet 5 likes -
Postgres is most certainly not image based. To be clear: image based means a system that operates by checkpoint/restart, and not initialization from scratch. If you run a Pharo image today, there are literally objects that were instantiated 40 years ago in it.
7 replies 0 retweets 1 like -
The SBCL model is to constantly regenerate base images from source. Best of both worlds.
1 reply 0 retweets 0 likes -
It's really just a fancy source build, the way that Emacs is. There's nothing like the persistence you find in a capability OS or a Smalltalk system or what have you. And that's to the good, btw.
1 reply 0 retweets 0 likes
No, it's more than a source build, it's an incremental meta-source build. The source doesn't directly reflect the object, but is evaluated to create the object. And thanks to cached intermediate images can do so incrementally.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
Read my blog!