Smalltalk › Squeak › Squeak - Dev

image overload

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

27 messages Options

Eliot Miranda-2

image overload

Hi All,

I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

K. K. Subramaniam

Re: image overload

On Friday 12 March 2010 11:29:20 pm Eliot Miranda wrote:
> I'm sure Im opening an old topic but anyway, as I was riding the train
> to work today I saw a shop called "Audio Images" and it struck me how
> overloaded the term image is, and how poor a term for the contents of the
> image file Smalltalk image is. What's in the image is a snapshot of...
> almost the entire system (minus platform-specific virtual machine and
> possibly minus sources). So Smalltalk system file would be a far better
> term and stsys a more unique file extension (and according to Wikipedia STS
> is unused too).
If ever we change the image format, we should also change its name and
extension. The first time people hear the term, they think of 'picture'. I
suppose the term image is a Mac hangover :-).

I prefer "bit bag" (*.bag) or "bag of bits" (*.bob).

BTW, sts is already taken (Microsoft Visual C)

Subbu

Casey Ransberger

Re: image overload

In reply to this post by Eliot Miranda-2

After you get the wheel right, and put it on a bicycle, and once the
bikeshed's built, you still have to get people to agree on what color
the bikeshed should be.

I think with virtualization entering mainstream consciousness, the
term image will be okay. But that's just me. If anything else, though,
I'd recommend "snapshot" which is the colloquial term. Note that this
term also implies photography, and thus, imagery.

I actually think there's value in the metaphor, is what I guess I'm
trying to say.

On Friday, March 12, 2010, Eliot Miranda <[hidden email]> wrote:

> Hi All,
> I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.
>
> P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours
> "And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
> "Ah," said the marketing girl, "Well, we're having a little difficulty there."
> "Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
> The marketing girl soured him with a look.
> "Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."
>

--
Casey Ransberger

Travis Griggs-4

Re: image overload

On Mar 12, 2010, at 10:10 AM, Casey Ransberger wrote:

> After you get the wheel right, and put it on a bicycle, and once the
> bikeshed's built, you still have to get people to agree on what color
> the bikeshed should be.
>
> I think with virtualization entering mainstream consciousness, the
> term image will be okay. But that's just me. If anything else, though,
> I'd recommend "snapshot" which is the colloquial term. Note that this
> term also implies photography, and thus, imagery.
>
> I actually think there's value in the metaphor, is what I guess I'm
> trying to say.

I agree. I remember I used to think it was more skewed/misapplied than
I do now. Now days we talk about virtual images. And disk images.
Quite commonly. It seems to me... yet another case where the world
caught up with Smalltalk. :)

--
Travis Griggs
Objologist
Light travels faster than sound. This is why some people appear bright
until you hear them speak...

Bruce Boyer

Re: [vwnc] image overload

In reply to this post by Eliot Miranda-2

This is rather a sensitive area with me at the moment, as I'm working on indexing docs. I've had to resort to using "image" and "graphical image" to try to distinguish these two, but "image" remains unclear to anyone who doesn't already know.

I could guess that the term "snapshot" came first, as a methaphorical attempt to describe what saving that thing is, and "image" is what snapshots give (or pictures or something even worse for that thing). But, it's only a guess.

If a really good term were proferred, the documentation cost will be amortized over a long period of time, so not a worry. Getting it accepted by smalltalkers will be the harder problem.

I'm not sure, though, that "system file" is right. The file part is just an artifact of saving the state of the system, providing a way to preserving it for a restart.

Is there a recognizable term for the state of memory at a moment? Cognitive scientists might have something, though I'm sure it would be hugely debated whether there is any such thing.

Waste of time? Perhaps. But, beats indexing :)

Bruce

----- Original Message -----

From: [hidden email]

To: [hidden email] ; [hidden email] ; [hidden email]

Sent: Friday, March 12, 2010 9:59 AM

Subject: [vwnc] image overload

Hi All,

I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Eliot Miranda-2

Re: [vwnc] image overload

On Fri, Mar 12, 2010 at 10:51 AM, Bruce Boyer <[hidden email]> wrote:

This is rather a sensitive area with me at the moment, as I'm working on indexing docs. I've had to resort to using "image" and "graphical image" to try to distinguish these two, but "image" remains unclear to anyone who doesn't already know.

I could guess that the term "snapshot" came first, as a methaphorical attempt to describe what saving that thing is, and "image" is what snapshots give (or pictures or something even worse for that thing). But, it's only a guess.

Right. That's why I don't like either snapshot or image. What are these snapshots or images of? They are intentionally abstract terms and are unhelpful. Yes, snapshot is much better, but still hopelessly abstract.

If a really good term were proferred, the documentation cost will be amortized over a long period of time, so not a worry. Getting it accepted by smalltalkers will be the harder problem.

I'm not sure, though, that "system file" is right. The file part is just an artifact of saving the state of the system, providing a way to preserving it for a restart.

But I see a snapshot file are more than just a memory dump. It /is/ the entire Smalltalk system, class library, potentially compiler, debugger, tools. It is in a format that requires the virtual machine to run it, but it is in fact the Smalltalk system in quiescent form. It is not a memory dump. It is only a dump of the Smalltalk object heap, not the entire memory space.

It is more than just a way of saving the state. It is also a way of moving that state and resuming it on a different system. Once you have the virtual machine key you can unlock the image, uh, system, but everything you need to program the system (beyond execution display and input devices) is there.

Is there a recognizable term for the state of memory at a moment? Cognitive scientists might have something, though I'm sure it would be hugely debated whether there is any such thing.

I forget...

Waste of time? Perhaps. But, beats indexing :)

Bruce

----- Original Message -----

From: [hidden email]

To: [hidden email] ; [hidden email] ; [hidden email]

Sent: Friday, March 12, 2010 9:59 AM

Subject: [vwnc] image overload

Hi All,

I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Kooyman, Les

RE: [vwnc] image overload

In reply to this post by Bruce Boyer

"Is there a recognizable term for the state of memory at a moment?"

Isn't 'context' a good term for that? I know it's been used before, but seems appropriate.

Secondly, I like 'state' although that's a bit tautological.

From: [hidden email] on behalf of Bruce Boyer
Sent: Fri 3/12/2010 10:51 AM
To: Eliot Miranda; The general-purpose Squeak developers list; Pharo Development; vwnc NC
Subject: Re: [vwnc] image overload

If a really good term were proferred, the documentation cost will be amortized over a long period of time, so not a worry. Getting it accepted by smalltalkers will be the harder problem.

I'm not sure, though, that "system file" is right. The file part is just an artifact of saving the state of the system, providing a way to preserving it for a restart.

Is there a recognizable term for the state of memory at a moment? Cognitive scientists might have something, though I'm sure it would be hugely debated whether there is any such thing.

Waste of time? Perhaps. But, beats indexing :)

Bruce

----- Original Message -----

From: [hidden email]

To: [hidden email] ; [hidden email] ; [hidden email]

Sent: Friday, March 12, 2010 9:59 AM

Subject: [vwnc] image overload

Hi All,

I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Terry Raymond-2

RE: image overload

In reply to this post by Eliot Miranda-2

Well, if you think out of the box a bit, think of it as a sea of objects,

something organic or “ObjectSoup”.

However, what we tend to do is borrow a term that conveys how

we think about the image file. This invariably means the term will

be overloaded.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI 02878
(401) 624-4517 [hidden email]
<http://www.craftedsmalltalk.com>
===========================================================

From: [hidden email] [mailto:[hidden email]] On Behalf Of Eliot Miranda
Sent: Friday, March 12, 2010 12:59 PM
To: The general-purpose Squeak developers list; Pharo Development; vwnc NC
Subject: [squeak-dev] image overload

Hi All,

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

Alan Knight-2

RE: image overload

And it's alive, so maybe something like Sourdough starter, or Yoghurt.

"It sounds to me like your yoghurt is corrupted. You'll want to restart from a known good culture and reload your code."

At 02:24 PM 2010-03-12, Terry Raymond wrote:

Content-Type: multipart/alternative;
         boundary="----=_NextPart_000_0147_01CAC1EF.C3BA4730"
Content-Language: en-us

Well, if you think out of the box a bit, think of it as a sea of objects,
something organic or ObjectSoup.

However, what we tend to do is borrow a term that conveys how
we think about the image file. This invariably means the term will
be overloaded.

Terry

===========================================================
Terry Raymond
Crafted Smalltalk
80 Lazywood Ln.
Tiverton, RI 02878
(401) 624-4517      [hidden email]
< http://www.craftedsmalltalk.com>
===========================================================
From: [hidden email] [[hidden email]] On Behalf Of Eliot Miranda
Sent: Friday, March 12, 2010 12:59 PM
To: The general-purpose Squeak developers list; Pharo Development; vwnc NC
Subject: [squeak-dev] image overload

Hi All,

    I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

Alan Knight [|], Engineering Manager, Cincom Smalltalk

[hidden email]

http://www.cincom.com/smalltalk

Isaac Gouy

Re: [vwnc] image overload

In reply to this post by Bruce Boyer

--- On Fri, 3/12/10, Bruce Boyer <[hidden email]> wrote:

> From: Bruce Boyer <[hidden email]>
> Subject: Re: [vwnc] image overload
> To: "Eliot Miranda" <[hidden email]>, "The general-purpose Squeak developers list" <[hidden email]>, "Pharo Development" <[hidden email]>, "vwnc NC" <[hidden email]>
> Date: Friday, March 12, 2010, 10:51 AM

-snip-

> Is there a recognizable
> term for the state of
> memory at a moment?

It seems that Lispers phrase things a little differently, the SBCL file is called sbcl.core

3.2.3 Saving a Core Image
http://www.sbcl.org/manual/Saving-a-Core-Image.html

Ron Teitelbaum

RE: image overload

In reply to this post by Eliot Miranda-2

Hi Eliot,

How about World. You can shut down the World file and then start it back up and everything still lives. (It’s already part of the Squeak lexicon). What are you doing? You are taking a snapshot of the World. You are producing an image of the World: The Smalltalk World.

Ron Teitelbaum

Hi All,

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

Andreas.Raab

Re: image overload

In reply to this post by Alan Knight-2

On 3/12/2010 11:28 AM, Alan Knight wrote:
> And it's alive, so maybe something like Sourdough starter, or Yoghurt.
>
> "It sounds to me like your yoghurt is corrupted. You'll want to restart
> from a known good culture and reload your code."

Thank you sir, you made my day :-)

Cheers,
- Andreas

> At 02:24 PM 2010-03-12, Terry Raymond wrote:
>> Content-Type: multipart/alternative;
>> boundary="----=_NextPart_000_0147_01CAC1EF.C3BA4730"
>> Content-Language: en-us
>>
>> Well, if you think out of the box a bit, think of it as a sea of objects,
>> something organic or “ObjectSoup”.
>>
>> However, what we tend to do is borrow a term that conveys how
>> we think about the image file. This invariably means the term will
>> be overloaded.
>>
>> Terry
>>
>> ===========================================================
>> Terry Raymond
>> Crafted Smalltalk
>> 80 Lazywood Ln.
>> Tiverton, RI 02878
>> (401) 624-4517 [hidden email]
>> < http://www.craftedsmalltalk.com>
>> ===========================================================
>> *From:* [hidden email] [
>> mailto:[hidden email]] *On Behalf Of
>> *Eliot Miranda
>> *Sent:* Friday, March 12, 2010 12:59 PM
>> *To:* The general-purpose Squeak developers list; Pharo Development;
>> vwnc NC
>> *Subject:* [squeak-dev] image overload
>>
>> Hi All,
>>
>> I'm sure Im opening an old topic but anyway, as I was riding the train
>> to work today I saw a shop called "Audio Images" and it struck me how
>> overloaded the term image is, and how poor a term for the contents of
>> the image file Smalltalk image is. What's in the image is a snapshot
>> of... almost the entire system (minus platform-specific virtual
>> machine and possibly minus sources). So Smalltalk system file would be
>> a far better term and stsys a more unique file extension (and
>> according to Wikipedia STS is unused too). I can imagine that changing
>> form image would be hugely expensive in documentation terms (docs,
>> websites, workspaces, etc, etc). But I can at least dream of a better
>> term.
>>
>> P.S. I know, wasting one's time worrying about names. Almost as bad as
>> worrying about colours
>>
>> "And the wheel," said the Captain, "What about this wheel thingy? It
>> sounds a terribly interesting project."
>> "Ah," said the marketing girl, "Well, we're having a little difficulty
>> there."
>> "Difficulty?" exclaimed Ford. "Difficulty? What do you mean,
>> difficulty? It's the single simplest machine in the entire Universe!"
>> The marketing girl soured him with a look.
>> "Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us
>> what colour it should be."
>
> --
> Alan Knight [|], Engineering Manager, Cincom Smalltalk
> [hidden email]
> [hidden email]
> http://www.cincom.com/smalltalk
>
>
>
>

Wallen, David

RE: [vwnc] image overload

In reply to this post by Eliot Miranda-2

I kind of like the idea of suspended animation, or suspension, but there must be better terms that convey this.

- Dave W

From: [hidden email] [mailto:[hidden email]] On Behalf Of Eliot Miranda
Sent: Friday, March 12, 2010 11:05 AM
To: Bruce Boyer
Cc: vwnc NC; Pharo Development; The general-purpose Squeak developers list
Subject: Re: [vwnc] image overload

On Fri, Mar 12, 2010 at 10:51 AM, Bruce Boyer <[hidden email]> wrote:

If a really good term were proferred, the documentation cost will be amortized over a long period of time, so not a worry. Getting it accepted by smalltalkers will be the harder problem.

I'm not sure, though, that "system file" is right. The file part is just an artifact of saving the state of the system, providing a way to preserving it for a restart.

Is there a recognizable term for the state of memory at a moment? Cognitive scientists might have something, though I'm sure it would be hugely debated whether there is any such thing.

I forget...

Waste of time? Perhaps. But, beats indexing :)

Bruce

----- Original Message -----

From: [hidden email]

To: [hidden email] ; [hidden email] ; [hidden email]

Sent: Friday, March 12, 2010 9:59 AM

Subject: [vwnc] image overload

Hi All,

I'm sure Im opening an old topic but anyway, as I was riding the train to work today I saw a shop called "Audio Images" and it struck me how overloaded the term image is, and how poor a term for the contents of the image file Smalltalk image is. What's in the image is a snapshot of... almost the entire system (minus platform-specific virtual machine and possibly minus sources). So Smalltalk system file would be a far better term and stsys a more unique file extension (and according to Wikipedia STS is unused too). I can imagine that changing form image would be hugely expensive in documentation terms (docs, websites, workspaces, etc, etc). But I can at least dream of a better term.

P.S. I know, wasting one's time worrying about names. Almost as bad as worrying about colours

"And the wheel," said the Captain, "What about this wheel thingy? It sounds a terribly interesting project."
"Ah," said the marketing girl, "Well, we're having a little difficulty there."
"Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty? It's the single simplest machine in the entire Universe!"
The marketing girl soured him with a look.
"Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what colour it should be."

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

Georg Heeg

AW: [vwnc] image overload

Originally image was called virtual image. When I tried to explain what a virtual image was I also used the words virtual word of objects.

Georg

Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812

Tel. +49-3496-214328, Fax +49-3496-214712

Von: [hidden email] [mailto:[hidden email]] Im Auftrag von Wallen, David
Gesendet: Freitag, 12. März 2010 21:52
An: Eliot Miranda; Bruce Boyer
Cc: vwnc NC; The general-purpose Squeak developers list; Pharo Development
Betreff: Re: [vwnc] image overload

I kind of like the idea of suspended animation, or suspension, but there must be better terms that convey this.

- Dave W

kobetic

Re: [vwnc] image overload

In reply to this post by Eliot Miranda-2

I get a feeling that we're talking about two different things here:

1) the file
2) the live system running

I think that 2) isn't particularly different from any other running program, be it a Java app or even a C app. So maybe it doesn't even need a special term, it's the running application.

It's the 1) that people seem to have difficulty with. For that I find 'snapshot' quite fitting as it emphasises the important property that the system isn't really live and running, it's a snapshot of the system at a particular moment in time. I don't think it's particularly different from a memory dump either (ignoring minor technical details). The practical difference is that we can readily revive the system from the snapshot and have it continue from that point on. As many times as we want in fact. That's probably not as easy with a memory dump, although presumably not impossible.

The obvious and direct analogy are the virtualization technologies reliving their renaisance these days. From what I've seen the term snapshot is used there as well for pretty much the same thing.

"Georg Heeg"<[hidden email]> wrote:

> Originally image was called virtual image. When I tried to explain what a
> virtual image was I also used the words virtual word of objects.
>
>
>
> Georg
>
>
>
> Georg Heeg eK, Dortmund und Köthen, HR Dortmund A 12812
>
> Tel. +49-3496-214328, Fax +49-3496-214712
>
> Von: [hidden email] [mailto:[hidden email]] Im Auftrag
> von Wallen, David
> Gesendet: Freitag, 12. März 2010 21:52
> An: Eliot Miranda; Bruce Boyer
> Cc: vwnc NC; The general-purpose Squeak developers list; Pharo Development
> Betreff: Re: [vwnc] image overload
>
>
>
> I kind of like the idea of suspended animation, or suspension, but there
> must be better terms that convey this.
>
>
>
> - Dave W
>
>
>
>
> _______________________________________________
> vwnc mailing list
> [hidden email]
> http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
>

Colin Putney

Re: image overload

In reply to this post by Terry Raymond-2

On 2010-03-12, at 11:24 AM, Terry Raymond wrote:

> Well, if you think out of the box a bit, think of it as a sea of objects,
> something organic or “ObjectSoup”.

Actually, in NewtonScript, the place where objects live really is called "the soup." I think it's a great term.

Colin

Nicolas Cellier

Re: image overload

2010/3/13 Colin Putney <[hidden email]>:

>
> On 2010-03-12, at 11:24 AM, Terry Raymond wrote:
>
>> Well, if you think out of the box a bit, think of it as a sea of objects,
>> something organic or “ObjectSoup”.
>
> Actually, in NewtonScript, the place where objects live really is called "the soup." I think it's a great term.
>
> Colin
>

If the living image is a soup, then the snapshot is Freeze-drying
(also known as lyophilization or cryodesiccation - wikipedia says).
Just pour a bit of water, and your objects are floating back in the soup.

Nicolas

Karl Ramberg

Re: image overload

In reply to this post by Eliot Miranda-2

The word state is kind of good. Its both a place and a condition and
is ambiguous enough to cover what we talk about.

karl

On Fri, Mar 12, 2010 at 5:59 PM, Eliot Miranda <[hidden email]> wrote:

> Hi All,
> I'm sure Im opening an old topic but anyway, as I was riding the train
> to work today I saw a shop called "Audio Images" and it struck me how
> overloaded the term image is, and how poor a term for the contents of the
> image file Smalltalk image is. What's in the image is a snapshot of...
> almost the entire system (minus platform-specific virtual machine and
> possibly minus sources). So Smalltalk system file would be a far better
> term and stsys a more unique file extension (and according to Wikipedia STS
> is unused too). I can imagine that changing form image would be hugely
> expensive in documentation terms (docs, websites, workspaces, etc, etc).
> But I can at least dream of a better term.
> P.S. I know, wasting one's time worrying about names. Almost as bad as
> worrying about colours
> "And the wheel," said the Captain, "What about this wheel thingy? It sounds
> a terribly interesting project."
> "Ah," said the marketing girl, "Well, we're having a little difficulty
> there."
> "Difficulty?" exclaimed Ford. "Difficulty? What do you mean, difficulty?
> It's the single simplest machine in the entire Universe!"
> The marketing girl soured him with a look.
> "Alright, Mr. Wiseguy," she said, "if you're so clever, you tell us what
> colour it should be."
>
>
>

J G

Re: [vwnc] [squeak-dev] image overload

In reply to this post by Alan Knight-2

On Sat, Mar 13, 2010 at 3:28 AM, Alan Knight <[hidden email]> wrote:
> And it's alive, so maybe something like Sourdough starter, or Yoghurt.
>
> "It sounds to me like your yoghurt is corrupted. You'll want to restart from
> a known good culture and reload your code."

I tried to save an image as hacking.im the other day and rename Object
as Dharma. VW took seconds to get this done and then I have the whole
image changed to Dharma world. This is not useful one might think. But
enlightened me, honestly.
--
Best Regards,

Jim G

Stéphane Rollandin

Re: image overload

In reply to this post by Nicolas Cellier

> If the living image is a soup, then the snapshot is Freeze-drying
> (also known as lyophilization or cryodesiccation - wikipedia says).
> Just pour a bit of water, and your objects are floating back in the soup.

but they loose some taste in the process... well, as long as they don't
loose state.

Stef