coding in forth is fun!!

I might be getting the hang of this a lil.

It seems unix and its networking will be tuffest part.....but anything
on this box works nicely.

On Tuesday, July 17, 2012 4:15:06 PM UTC-5, quiet_lad wrote:
> I might be getting the hang of this a lil.
>
> It seems unix and its networking will be tuffest part.....but anything
> on this box works nicely.

Building up your own vocabulary to an understanding of your computing tasks is more fun than decoding arguments to swiss army knife commands.

On Tuesday, July 24, 2012 8:19:33 PM UTC-7, Clyde W. Phillips Jr. wrote:
> On Tuesday, July 17, 2012 4:15:06 PM UTC-5, quiet_lad wrote:
> > I might be getting the hang of this a lil.
> >
> > It seems unix and its networking will be tuffest part.....but anything
> > on this box works nicely.
>
> Building up your own vocabulary to an understanding of your computing tasks is more fun than decoding arguments to swiss army knife commands.

tttootally!!

forth is awesomeer the more I use it

today was amazed at how upgrading a backup called zmanda is took mysql php perl centos libs gcc ncurses balh blha blha blha liek 40 libs

how could same be done with forth?

I bet way weeeyy ezer

On Wednesday, July 25, 2012 7:20:01 PM UTC-5, (unknown) wrote:
> On Tuesday, July 24, 2012 8:19:33 PM UTC-7, Clyde W. Phillips Jr. wrote:
> > On Tuesday, July 17, 2012 4:15:06 PM UTC-5, quiet_lad wrote:
> > > I might be getting the hang of this a lil.
> > >
> > > It seems unix and its networking will be tuffest part.....but anything
> > > on this box works nicely.
> >
> > Building up your own vocabulary to an understanding of your computing tasks is more fun than decoding arguments to swiss army knife commands.
>
> tttootally!!
>
> forth is awesomeer the more I use it
>
> today was amazed at how upgrading a backup called zmanda is took mysql php perl centos libs gcc ncurses balh blha blha blha liek 40 libs
>
> how could same be done with forth?
>
> I bet way weeeyy ezer

The standard forth methodology would be to interactively build up your "zmanda" (a backup? program) as source to load when when needed, then write an "upgraded" zmanda and load it when you want to use it, instead of loading the older zmanda. The forth equivalent of upgrade in this case would be the forth word forget, assuming the older zmanda is loaded it would forget it, then load the upgraded zmanda. Upgrade complete.

On Thursday, July 26, 2012 9:31:05 AM UTC-7, Clyde W. Phillips Jr. wrote:
> On Wednesday, July 25, 2012 7:20:01 PM UTC-5, (unknown) wrote:
>
> > On Tuesday, July 24, 2012 8:19:33 PM UTC-7, Clyde W. Phillips Jr. wrote:
>
> > > On Tuesday, July 17, 2012 4:15:06 PM UTC-5, quiet_lad wrote:
>
> > > > I might be getting the hang of this a lil.
>
> > > >
>
> > > > It seems unix and its networking will be tuffest part......but anything
>
> > > > on this box works nicely.
>
> > >
>
> > > Building up your own vocabulary to an understanding of your computing tasks is more fun than decoding arguments to swiss army knife commands.
>
> >
>
> > tttootally!!
>
> >
>
> > forth is awesomeer the more I use it
>
> >
>
> > today was amazed at how upgrading a backup called zmanda is took mysql php perl centos libs gcc ncurses balh blha blha blha liek 40 libs
>
> >
>
> > how could same be done with forth?
>
> >
>
> > I bet way weeeyy ezer
>
>
>
> The standard forth methodology would be to interactively build up your "zmanda" (a backup? program) as source to load when when needed, then write an "upgraded" zmanda and load it when you want to use it, instead of loadingthe older zmanda. The forth equivalent of upgrade in this case would be the forth word forget, assuming the older zmanda is loaded it would forget it, then load the upgraded zmanda. Upgrade complete.

ideally the code would be good enuf

I also would not use mysql nor a lamp app to back it up