Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > comp.misc > #18038 > unrolled thread

python to deprecate NNTP

Back to article view | Back to comp.misc

Contents

  python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-23 17:44 -0400
    Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-23 21:49 +0000
      Re: python to deprecate NNTP not@telling.you.invalid (Computer Nerd Kev) - 2019-05-23 22:59 +0000
        Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-24 01:51 +0000
        Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-23 22:24 -0400
          Re: python to deprecate NNTP Bob Eager <news0073@eager.cx> - 2019-05-24 07:52 +0000
            Re: python to deprecate NNTP mm0fmf <none@invalid.com> - 2019-05-29 18:06 +0100
          Re: python to deprecate NNTP Richard Kettlewell <invalid@invalid.invalid> - 2019-05-24 13:25 +0100
          Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-24 14:54 +0000
            Re: python to deprecate NNTP Sylvia Else <sylvia@email.invalid> - 2019-05-25 23:41 +1000
              Re: python to deprecate NNTP Huge <Huge@nowhere.much.invalid> - 2019-05-25 16:35 +0000
                Re: python to deprecate NNTP kludge@panix.com (Scott Dorsey) - 2019-05-26 13:38 -0400
                  Re: python to deprecate NNTP not@telling.you.invalid (Computer Nerd Kev) - 2019-05-26 23:21 +0000
                  Re: python to deprecate NNTP Huge <Huge@nowhere.much.invalid> - 2019-05-27 11:06 +0000
              Re: python to deprecate NNTP Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-05-25 14:43 -0300
      Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-23 20:37 -0400
        Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-24 15:00 +0000
        Re: python to deprecate NNTP Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-05-24 17:31 -0300
          Re: python to deprecate NNTP Huge <Huge@nowhere.much.invalid> - 2019-05-25 07:38 +0000
          Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-26 01:36 +0000
      Re: python to deprecate NNTP mm0fmf <none@invalid.com> - 2019-05-29 18:05 +0100
    Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-23 17:51 -0400
    Re: python to deprecate NNTP Sylvia Else <sylvia@email.invalid> - 2019-05-24 14:29 +1000
      Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-24 15:01 +0000
        Re: python to deprecate NNTP Jerry Peters <jerry@example.invalid> - 2019-05-24 20:25 +0000
          Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-24 21:32 +0000
            Re: python to deprecate NNTP not@telling.you.invalid (Computer Nerd Kev) - 2019-05-25 03:23 +0000
            Re: python to deprecate NNTP Jerry Peters <jerry@example.invalid> - 2019-05-25 20:32 +0000
              Re: python to deprecate NNTP Dan Espen <dan1espen@gmail.com> - 2019-05-25 18:08 -0400
                Re: python to deprecate NNTP Mike Spencer <mds@bogus.nodomain.nowhere> - 2019-05-25 21:27 -0300
              Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-27 21:12 -0400
                Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-28 03:06 +0000
                  Re: python to deprecate NNTP Richard Kettlewell <invalid@invalid.invalid> - 2019-05-28 08:16 +0100
                    Re: python to deprecate NNTP Rich <rich@example.invalid> - 2019-05-28 15:19 +0000
                      Re: python to deprecate NNTP Richard Kettlewell <invalid@invalid.invalid> - 2019-05-28 18:26 +0100
                Re: python to deprecate NNTP kludge@panix.com (Scott Dorsey) - 2019-05-28 14:46 -0400
    Re: python to deprecate NNTP "polk" <polka@dot.dot> - 2019-05-25 15:14 +0000
      Re: python to deprecate NNTP RS Wood <rsw@therandymon.com> - 2019-05-26 01:37 +0000
        Re: python to deprecate NNTP Huge <Huge@nowhere.much.invalid> - 2019-05-26 05:45 +0000
    Re: python to deprecate NNTP Robert Munyer <robertm@not-for-mail.invalid> - 2019-06-07 23:03 +0000

Page 1 of 2  [1] 2  Next page →

#18038 — python to deprecate NNTP

https://www.python.org/dev/peps/pep-0594/#nntplib

This affects me, at least.  The little script I use to post articles
from my RSS reader relies on python.  Boo!  Why can't developers just
leave working shit alone?

I'll wind up maintaining a VM with an older distro or something, just
to do what I like to do.  I hate that!

-- 
RS Wood <rsw@therandymon.com>

[toc] | [next] | [standalone]

#18039

RS Wood <rsw@therandymon.com> wrote:
> https://www.python.org/dev/peps/pep-0594/#nntplib
> 
> This affects me, at least.  The little script I use to post articles
> from my RSS reader relies on python.  Boo!  Why can't developers just
> leave working shit alone?

Or... switch to another language for your 'little script':

https://www.tcl.tk/community/tcl2004/Tcl2003papers/kupries-doctools/tcllib/modules/nntp/nntp.man

Handles both reading and posting.

> I'll wind up maintaining a VM with an older distro or something, just 
> to do what I like to do.  I hate that!

An alternative, but if you do *hate* it enough, maybe you might 
consider the switch above?

[toc] | [prev] | [next] | [standalone]

#18041

Rich <rich@example.invalid> wrote:
> RS Wood <rsw@therandymon.com> wrote:
>> https://www.python.org/dev/peps/pep-0594/#nntplib
>> 
>> This affects me, at least.  The little script I use to post articles
>> from my RSS reader relies on python.  Boo!  Why can't developers just
>> leave working shit alone?
> 
> Or... switch to another language for your 'little script':
> 
> https://www.tcl.tk/community/tcl2004/Tcl2003papers/kupries-doctools/tcllib/modules/nntp/nntp.man
> 
> Handles both reading and posting.

Ah, I can just imagine that he goes to the trouble to rewrite
everything in TCL. Then a week later notices a new announcement
post somewhere:
"seeing as other scripting languages, such as Python, have already
 taken the decision to discontinue support for NNTP, we have decided
 to do likewise..."

Granted the slow development of TCL probably makes it less risky than
others, but I wouldn't count on that myself.

>> I'll wind up maintaining a VM with an older distro or something, just 
>> to do what I like to do.  I hate that!
> 
> An alternative, but if you do *hate* it enough, maybe you might 
> consider the switch above?

Or just compile the old Python code on newer distributions and have
it installed as something like "python-old" which is used instead
of "python" only for the NNTP script. A VM seems way overkill to me.

-- 
__          __
#_ < |\| |< _#

[toc] | [prev] | [next] | [standalone]

#18042

Computer Nerd Kev <not@telling.you.invalid> wrote:
> Rich <rich@example.invalid> wrote:
>> RS Wood <rsw@therandymon.com> wrote:
>>> https://www.python.org/dev/peps/pep-0594/#nntplib
>>> 
>>> This affects me, at least.  The little script I use to post articles
>>> from my RSS reader relies on python.  Boo!  Why can't developers just
>>> leave working shit alone?
>> 
>> Or... switch to another language for your 'little script':
>> 
>> https://www.tcl.tk/community/tcl2004/Tcl2003papers/kupries-doctools/tcllib/modules/nntp/nntp.man
>> 
>> Handles both reading and posting.
> 
> Ah, I can just imagine that he goes to the trouble to rewrite
> everything in TCL. Then a week later notices a new announcement
> post somewhere:
> "seeing as other scripting languages, such as Python, have already
> taken the decision to discontinue support for NNTP, we have decided
> to do likewise..."

This is, of course, possible within any ecosystem.

> Granted the slow development of TCL probably makes it less risky than
> others, but I wouldn't count on that myself.

I suspect it won't happen as well.  Plus the NNTP library is part of 
the separate Tcllib package, so its presence/absence does not directly 
effect main Tcl development.  Which might reduce the risk a bit more.

[toc] | [prev] | [next] | [standalone]

#18044

On 2019-05-23, Computer Nerd Kev <not@telling.you.invalid> wrote:
> Rich <rich@example.invalid> wrote:
> Or just compile the old Python code on newer distributions and have
> it installed as something like "python-old" which is used instead
> of "python" only for the NNTP script. A VM seems way overkill to me.

I'm still going to check out tcl, but it now appears I will be able to
continue using Python 2.7 for quite some time more, so that's better
than nothing and keeps me in business for little extra effort.

Other things that have annoyed:

* Firefox drops gopher support because 'scary/safety'
* Opera 12 shits the bed, gets bought by a Chinese company, game over
* the Konqueror browser/everything and the kio_slave ecosystem gets
* basically abandoned when KDE goes to its 4th manifestation
* Gnome 1 with sawfish was pretty darned good other than font rendering
* LiLO, which worked perfectly well, gets deprecated for a system that
  seems ridiculously complex to me
 

[toc] | [prev] | [next] | [standalone]

#18047

On Thu, 23 May 2019 22:24:57 -0400, RS Wood wrote:

> On 2019-05-23, Computer Nerd Kev <not@telling.you.invalid> wrote:
>> Rich <rich@example.invalid> wrote:
>> Or just compile the old Python code on newer distributions and have it
>> installed as something like "python-old" which is used instead of
>> "python" only for the NNTP script. A VM seems way overkill to me.
> 
> I'm still going to check out tcl, but it now appears I will be able to
> continue using Python 2.7 for quite some time more, so that's better
> than nothing and keeps me in business for little extra effort.
> 
> Other things that have annoyed:
> 
> * Firefox drops gopher support because 'scary/safety'
> * Opera 12 shits the bed, gets bought by a Chinese company, game over *
> the Konqueror browser/everything and the kio_slave ecosystem gets *
> basically abandoned when KDE goes to its 4th manifestation * Gnome 1
> with sawfish was pretty darned good other than font rendering * LiLO,
> which worked perfectly well, gets deprecated for a system that
>   seems ridiculously complex to me

systemd



-- 
Using UNIX since v6 (1975)...

Use the BIG mirror service in the UK:
 http://www.mirrorservice.org

[toc] | [prev] | [next] | [standalone]

#18078

On 24/05/2019 08:52, Bob Eager wrote:
> On Thu, 23 May 2019 22:24:57 -0400, RS Wood wrote:
>
>> On 2019-05-23, Computer Nerd Kev <not@telling.you.invalid> wrote:
>>> Rich <rich@example.invalid> wrote:
>>> Or just compile the old Python code on newer distributions and have it
>>> installed as something like "python-old" which is used instead of
>>> "python" only for the NNTP script. A VM seems way overkill to me.
>>
>> I'm still going to check out tcl, but it now appears I will be able to
>> continue using Python 2.7 for quite some time more, so that's better
>> than nothing and keeps me in business for little extra effort.
>>
>> Other things that have annoyed:
>>
>> * Firefox drops gopher support because 'scary/safety'
>> * Opera 12 shits the bed, gets bought by a Chinese company, game over *
>> the Konqueror browser/everything and the kio_slave ecosystem gets *
>> basically abandoned when KDE goes to its 4th manifestation * Gnome 1
>> with sawfish was pretty darned good other than font rendering * LiLO,
>> which worked perfectly well, gets deprecated for a system that
>>    seems ridiculously complex to me
>
> systemd
>
>
>
Is saying systemd in a newsgroup reply a derivative case of Godwin's Law?

[toc] | [prev] | [next] | [standalone]

#18048

RS Wood <rsw@therandymon.com> writes:
> OComputer Nerd Kev <not@telling.you.invalid> wrote:
>> Or just compile the old Python code on newer distributions and have
>> it installed as something like "python-old" which is used instead
>> of "python" only for the NNTP script. A VM seems way overkill to me.
>
> I'm still going to check out tcl, but it now appears I will be able to
> continue using Python 2.7 for quite some time more, so that's better
> than nothing and keeps me in business for little extra effort.

Based on the schedule proposed in the link you can keep using any Python
up to and including 3.9 before needing to take a copy of the NNTP
library.

-- 
https://www.greenend.org.uk/rjk/

[toc] | [prev] | [next] | [standalone]

#18049

RS Wood <rsw@therandymon.com> wrote:
> On 2019-05-23, Computer Nerd Kev <not@telling.you.invalid> wrote:
>> Rich <rich@example.invalid> wrote:
>> Or just compile the old Python code on newer distributions and have
>> it installed as something like "python-old" which is used instead
>> of "python" only for the NNTP script. A VM seems way overkill to me.
> 
> I'm still going to check out tcl, but it now appears I will be able to
> continue using Python 2.7 for quite some time more, so that's better
> than nothing and keeps me in business for little extra effort.

Alternatives where one does not have to rewrite existing, working, 
scripts are generally better.  FWIW, the NNTP library in Tcllib is 
reasonably nice to use, I've created several different little Tcl 
scripts for Usenet stuff along the way using it.

> Other things that have annoyed:
> 
> * LiLO, which worked perfectly well, gets deprecated for a system that
>  seems ridiculously complex to me

This one, however, is not exactly LILO's fault [1].  The hardware 
makers (largely at MS's insistence) moved away from legacy BIOS into 
the new fancy EFI system.

Classic LILO expects legacy BIOS calls to handle several stages of its 
bootstrapping, so it just no longer works with EFI only hardware.

But, there is eLILO for EFI hardware: 
https://sourceforge.net/projects/elilo/


[1] I'm excluding here those distros that choose to go grub even though 
lilo would have still worked here, as that was by choice of the distro, 
not because the hardware changes forced the change.

[toc] | [prev] | [next] | [standalone]

#18057

On 25/05/2019 12:54 am, Rich wrote:
> RS Wood <rsw@therandymon.com> wrote:
>> On 2019-05-23, Computer Nerd Kev <not@telling.you.invalid> wrote:
>>> Rich <rich@example.invalid> wrote:
>>> Or just compile the old Python code on newer distributions and have
>>> it installed as something like "python-old" which is used instead
>>> of "python" only for the NNTP script. A VM seems way overkill to me.
>>
>> I'm still going to check out tcl, but it now appears I will be able to
>> continue using Python 2.7 for quite some time more, so that's better
>> than nothing and keeps me in business for little extra effort.
> 
> Alternatives where one does not have to rewrite existing, working,
> scripts are generally better.  FWIW, the NNTP library in Tcllib is
> reasonably nice to use, I've created several different little Tcl
> scripts for Usenet stuff along the way using it.
> 
>> Other things that have annoyed:
>>
>> * LiLO, which worked perfectly well, gets deprecated for a system that
>>   seems ridiculously complex to me
> 
> This one, however, is not exactly LILO's fault [1].  The hardware
> makers (largely at MS's insistence) moved away from legacy BIOS into
> the new fancy EFI system.

Nevertheless, Grub is horribly complicated. One shouldn't have to climb 
a learning curve every time one wants to make a trivial change to the 
configuration of a corner of the system that one almost never touches, 
and hence cannot maintain a working knowledge of.

Sylvia.

[toc] | [prev] | [next] | [standalone]

#18059

On 2019-05-25, Sylvia Else <sylvia@email.invalid> wrote:

[snippage]

> Nevertheless, Grub is horribly complicated. One shouldn't have to climb 
> a learning curve every time one wants to make a trivial change to the 
> configuration of a corner of the system that one almost never touches, 
> and hence cannot maintain a working knowledge of.

*applause*


-- 
Today is Setting Orange, the 72nd day of Discord in the YOLD 3185
       Comes in bells, your servant, don't forsake him 

[toc] | [prev] | [next] | [standalone]

#18067

Huge  <usenet@huge.org.uk> wrote:
>On 2019-05-25, Sylvia Else <sylvia@email.invalid> wrote:
>
>[snippage]
>
>> Nevertheless, Grub is horribly complicated. One shouldn't have to climb 
>> a learning curve every time one wants to make a trivial change to the 
>> configuration of a corner of the system that one almost never touches, 
>> and hence cannot maintain a working knowledge of.
>
>*applause*

Grub is complicated for two reasons:

1. EFI is a mess

2. The whole dual-boot process is a mess.

Of course, both EFI and dual-booting are consequences of Windows, so perhaps
that is only one reason.

Now, admittedly grub2 is more complicated than regular grub, for no apparent
reason at all.
--scott

-- 
"C'est un Nagra. C'est suisse, et tres, tres precis."

[toc] | [prev] | [next] | [standalone]

#18068

Scott Dorsey <kludge@panix.com> wrote:
> Huge  <usenet@huge.org.uk> wrote:
>>On 2019-05-25, Sylvia Else <sylvia@email.invalid> wrote:
>>
>>[snippage]
>>
>>> Nevertheless, Grub is horribly complicated. One shouldn't have to climb 
>>> a learning curve every time one wants to make a trivial change to the 
>>> configuration of a corner of the system that one almost never touches, 
>>> and hence cannot maintain a working knowledge of.
>>
>>*applause*
> 
> Grub is complicated for two reasons:
> 
> 1. EFI is a mess
> 
> 2. The whole dual-boot process is a mess.
> 
> Of course, both EFI and dual-booting are consequences of Windows, so perhaps
> that is only one reason.

A lot of people do seem to dual boot with different Linux distros as
well, myself included (3x Linux and 0x Windows on one system).

> Now, admittedly grub2 is more complicated than regular grub, for no apparent
> reason at all.

Indeed, and again incompatible so that on the above three-Linux
system I have to make Grub load Grub2 in order to load one of
the distros (or the other way 'round - as already stated, it's
easy to forget these things).

-- 
__          __
#_ < |\| |< _#

[toc] | [prev] | [next] | [standalone]

#18069

On 2019-05-26, Scott Dorsey <kludge@panix.com> wrote:
> Huge  <usenet@huge.org.uk> wrote:
>>On 2019-05-25, Sylvia Else <sylvia@email.invalid> wrote:
>>
>>[snippage]
>>
>>> Nevertheless, Grub is horribly complicated. One shouldn't have to climb 
>>> a learning curve every time one wants to make a trivial change to the 
>>> configuration of a corner of the system that one almost never touches, 
>>> and hence cannot maintain a working knowledge of.
>>
>>*applause*
>
> Grub is complicated for two reasons:
>
> 1. EFI is a mess
>
> 2. The whole dual-boot process is a mess.

3. No-one GAS about putting a user-friendly front end on this mess.


-- 
Today is Boomtime, the 1st day of Confusion in the YOLD 3185
       Comes in bells, your servant, don't forsake him 

[toc] | [prev] | [next] | [standalone]

#18060

Sylvia Else <sylvia@email.invalid> writes:

> Nevertheless, Grub is horribly complicated. One shouldn't have to
> climb a learning curve every time one wants to make a trivial change
> to the configuration of a corner of the system that one almost never
> touches, and hence cannot maintain a working knowledge of.

Remeber the slogan, "Life-long learning"?  It was supposed to mean
learning *new* stuff, stuff that cast a new light on what you already
knew or extended the range of what you undestood.

Now it's coming to mean learning the *same* stuff over and over again.

-- 
Mike Spencer                  Nova Scotia, Canada

[toc] | [prev] | [next] | [standalone]

#18043

On 2019-05-23, Rich <rich@example.invalid> wrote:
> RS Wood <rsw@therandymon.com> wrote:
>> https://www.python.org/dev/peps/pep-0594/#nntplib
>> 
>> This affects me, at least.  The little script I use to post articles
>> from my RSS reader relies on python.  Boo!  Why can't developers just
>> leave working shit alone?
>
> Or... switch to another language for your 'little script':
>
> https://www.tcl.tk/community/tcl2004/Tcl2003papers/kupries-doctools/tcllib/modules/nntp/nntp.man
>
> Handles both reading and posting.
>
>> I'll wind up maintaining a VM with an older distro or something, just
>> to do what I like to do.  I hate that!
>
> An alternative, but if you do *hate* it enough, maybe you might
> consider the switch above?

Interesting, thanks!  I had no idea it existed. I also don't know much
about TCL, so i've got some learning to do.

Currently I use the newsbeuter/newsboat RSS reader, pipe the article
into a little bash script that prompts for title, whatever, creates a
little text file in /tmp with the body of the RSS article plus those
respones, then stuffs the text file into the postnews python script.
Has worked a treat since 2014.

I'll check this out, thanks!

However, I'll still bitch and moan: I'm just annoyed that things that
work, stop working or are deprecated because "not enough people use
them."  Yeah I know, someone has to mantain the code, and there aren't
enough volunteers, etc.  Just annoyed things I like continued to evolve.

Meanwhile, whiskey has generally assuaged my general sense of annoyance
that technology evolves.  :)

[toc] | [prev] | [next] | [standalone]

#18050

RS Wood <rsw@therandymon.com> wrote:
> On 2019-05-23, Rich <rich@example.invalid> wrote:
>> RS Wood <rsw@therandymon.com> wrote:
>>> https://www.python.org/dev/peps/pep-0594/#nntplib
>>> 
>>> This affects me, at least.  The little script I use to post articles
>>> from my RSS reader relies on python.  Boo!  Why can't developers just
>>> leave working shit alone?
>>
>> Or... switch to another language for your 'little script':
>>
>> https://www.tcl.tk/community/tcl2004/Tcl2003papers/kupries-doctools/tcllib/modules/nntp/nntp.man
>>
>> Handles both reading and posting.
>>
>>> I'll wind up maintaining a VM with an older distro or something, just
>>> to do what I like to do.  I hate that!
>>
>> An alternative, but if you do *hate* it enough, maybe you might
>> consider the switch above?
> 
> Interesting, thanks!  I had no idea it existed. I also don't know much
> about TCL, so i've got some learning to do.

It (TCL) is a wee bit more LISP like than most, but beyond that, if you 
know how to write scripts in Python, you've got the needed requirements 
(how to write a program) and the difference is more on the line of "how 
do I do X in language Y".

> Currently I use the newsbeuter/newsboat RSS reader, pipe the article
> into a little bash script that prompts for title, whatever, creates a
> little text file in /tmp with the body of the RSS article plus those
> respones, then stuffs the text file into the postnews python script.
> Has worked a treat since 2014.

Sounds similar to the little Tcl GUI I've got for creating my posts 
here.  Paste in title, url, quote from article, push "post".

> However, I'll still bitch and moan: I'm just annoyed that things that
> work, stop working or are deprecated because "not enough people use
> them."  Yeah I know, someone has to mantain the code, and there aren't
> enough volunteers, etc.  Just annoyed things I like continued to evolve.

The sad part about dropping NNTP support is that the NNTP protocol has 
not changed in a very long time, so unless the module has a discovered 
security bug (unlikely) there should be no 'maintenence' to have to 
perform.  It should just continue to work, since nothing it would talk 
to is changing out from under it.

But, if the Python folks continue their typical expiring/changing of 
basic language functionality such that the NNTP module has to be 
updated to the "new flash in the pan" function they've come up with 
lately, then there's the maintence.  But then that's self imposed, and 
not caused by NNTP changing somewhere.

[toc] | [prev] | [next] | [standalone]

#18053

RS Wood <rsw@therandymon.com> writes:

> However, I'll still bitch and moan: I'm just annoyed that things that
> work, stop working or are deprecated because "not enough people use
> them."  Yeah I know, someone has to mantain the code, and there aren't
> enough volunteers, etc.  Just annoyed things I like continued to evolve.

I may have to wait another three years before I'm old enough to
address you as "Hey, kid..." but I'm guessing you're over 40.  The
answer to this problem is not to get old.  I spend a lot of time
defeating new, kewl crap that keeps  gushing out of the Web
Experience -- hours spent being my own doggedly cranky UX engineer.

But it's not just the web or the net; the Real World(tm) suffers from
similar, albeit at a slightly slower pace. Just off the top of my
head, the hardware store no longer stocks waterglass (sodium
silicate), copper screen wire (now fiberglass), metal roof
gutters/downspouts (now plastic) or knives with carbon steel (viz. not
stainless) blades. Now have to go find a chemical or ceramics supply
house for waterglass, industrial supplier for copper screen. Had to
get a pocket knife custom-made to get a good steel blade.

I just tried to buy knee pads to replace 10 yo ones -- old guy,
y'know?  Bending over can seize up my back but dropping to my knees
works in shop, garden, woodpile.  The store has a dozen varieties, all
much spiffier than my old ones but (demonstrated by me) less
functional.  They don't make the ugly but functional ones any more.

Oh, and I can't buy black 550 Levis any more, at least not in Canada.
I tried a personal letter to Levi Strauss exec. VP James Curleigh
because he's a Nova Scotia boy but had no response.  Seems he's also
just taken over as CEO of Gibson Guitars to rescue them from chapter
11 (who knew?) so I guess he's too busy to respond to Old Guys at the
retail level.  (Anybody here know Curleigh personally or have an
inside track at Levi Strauss?  These Mordor^H^H^H^H^H^H Walmart black
jeans look okay but don't fit/feel right.)


> Meanwhile, whiskey has generally assuaged my general sense of annoyance
> that technology evolves.  :)

The *is* a potential downside to that strategy.  But you knew that
already.  I suggest Glen Livet.

-- 
Mike Spencer                  Nova Scotia, Canada

[toc] | [prev] | [next] | [standalone]

#18056

On 2019-05-24, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>
> RS Wood <rsw@therandymon.com> writes:
>
>> However, I'll still bitch and moan: I'm just annoyed that things that
>> work, stop working or are deprecated because "not enough people use
>> them."  Yeah I know, someone has to mantain the code, and there aren't
>> enough volunteers, etc.  Just annoyed things I like continued to evolve.
>
> I may have to wait another three years before I'm old enough to
> address you as "Hey, kid..." but I'm guessing you're over 40.  The
> answer to this problem is not to get old. 

I don't see this as much of an option.

-- 
Today is Setting Orange, the 72nd day of Discord in the YOLD 3185
       Comes in bells, your servant, don't forsake him 

[toc] | [prev] | [next] | [standalone]

#18064

On 2019-05-24, Mike Spencer <mds@bogus.nodomain.nowhere> wrote:
>
> RS Wood <rsw@therandymon.com> writes:
>
>> However, I'll still bitch and moan: I'm just annoyed that things that
>> work, stop working or are deprecated because "not enough people use
>> them."  Yeah I know, someone has to mantain the code, and there aren't
>> enough volunteers, etc.  Just annoyed things I like continued to evolve.
>
> I may have to wait another three years before I'm old enough to
> address you as "Hey, kid..." but I'm guessing you're over 40.  The

LOL: I turn 48 this year, but I appreciate it that you gave me the
benefit of the doubt!

> But it's not just the web or the net; the Real World(tm) suffers from
> similar, albeit at a slightly slower pace. Just off the top of my
> head, the hardware store no longer stocks waterglass (sodium
>

Yep, and everything is cheaper and more poorly made.  Knives are a good
example.  
>
>> Meanwhile, whiskey has generally assuaged my general sense of annoyance
>> that technology evolves.  :)
>
> The *is* a potential downside to that strategy.  But you knew that
> already.  I suggest Glen Livet.

Solves a lot of problems common to life, actually!  Also useful to make
a surprising number of people significantly easier to bear :)

[toc] | [prev] | [next] | [standalone]

Page 1 of 2  [1] 2  Next page →

Back to top | Article view | comp.misc

csiph-web