public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Wols Lists <antlists@youngman.org.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternatives to knutclient
Date: Tue, 31 Oct 2017 16:56:53 +0000	[thread overview]
Message-ID: <59F8AB55.7050504@youngman.org.uk> (raw)
In-Reply-To: <7158279.1LLyUKUnIt@dell_xps>

On 30/10/17 23:28, Mick wrote:
> The regulator does not hold the budget, central government departments do and 
> the regulator cannot (or will not) control abnormal profits privatised 
> utilities are making year after year.  However, the regulator will engage 
> enthusiastically in the a theatre of regular reviews of market conditions, in 
> an attempt to convince consumers and tax payers the most gratuitous abuse of 
> power is kept in check.

Quite often that's the government's fault too ...

The reason British Telecom made obscene profits for YEARS after they
privatised was because they inherited terrible infrastructure that cost
a lot of money just to keep going.

And the reason it cost so much was that every time the General Post
Office tried to put money aside to replace said infrastructure, the
Government (the sole shareholder) declared a large dividend and took it
away. The alternative was for the GPO to borrow, but every time they did
that the Treasury said "that money is part of Government Borrowing.
We're committed to reducing government borrowing so you're not allowed
to borrow".

So BT made gazillions because a brand new exchange, with a ten year
warranty, probably cost about two years' maintenance of the exchange it
replaced. And because BT were quite visibly cutting prices (not by
much!) but the new infrastructure was reducing costs so much faster,
their profits soared.

Cheers,
Wol


  parent reply	other threads:[~2017-10-31 16:57 UTC|newest]

Thread overview: 40+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-28  8:58 [gentoo-user] Alternatives to knutclient Mick
2017-10-28 14:18 ` Daniel Frey
2017-10-28 16:48   ` Mick
2017-10-28 23:51     ` Daniel Frey
2017-10-29  1:56       ` Dale
2017-10-29  8:49         ` Mick
2017-10-29 11:21           ` Dale
2017-10-29 19:01             ` Wols Lists
2017-10-29 19:11               ` Mick
2017-10-29 19:30                 ` Wols Lists
2017-10-29 21:38                 ` Neil Bothwick
2017-10-29 19:46               ` Dale
2017-10-30  9:10                 ` Peter Humphrey
2017-10-30 10:15                   ` Mick
2017-10-30 14:09                     ` Daniel Frey
2017-10-30 14:47                       ` Mick
2017-10-30 19:33                         ` Daniel Frey
2017-10-30 19:37                           ` Daniel Frey
2017-10-30 19:40                           ` Rich Freeman
2017-10-30 21:01                             ` Dale
2017-10-30 23:39                               ` Mick
2017-10-31  0:09                                 ` mad.scientist.at.large
2017-10-31 17:33                                   ` Wols Lists
2017-10-31 23:29                                     ` Peter Humphrey
2017-11-01 12:45                                       ` Wols Lists
2017-11-01 13:47                                         ` Peter Humphrey
2017-10-31  0:26                                 ` Dale
2017-10-31  0:55                             ` Daniel Frey
2017-10-30 20:51                         ` mad.scientist.at.large
2017-10-30 20:50                   ` Dale
2017-10-30 21:04                     ` Rich Freeman
2017-10-30 23:28                       ` Mick
2017-10-30 23:42                         ` Rich Freeman
2017-10-31 17:05                           ` Wols Lists
2017-10-31 17:13                             ` Rich Freeman
2017-10-31 16:56                         ` Wols Lists [this message]
2017-10-31 17:08                           ` Rich Freeman
2017-10-30 22:59                     ` Mick
2017-10-30 23:32                       ` Rich Freeman
2017-10-31 17:17                         ` Wols Lists

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=59F8AB55.7050504@youngman.org.uk \
    --to=antlists@youngman.org.uk \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox