public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Alternatives to knutclient
Date: Mon, 30 Oct 2017 23:28:21 +0000	[thread overview]
Message-ID: <7158279.1LLyUKUnIt@dell_xps> (raw)
In-Reply-To: <CAGfcS_kegbkMOFfRW-iK9tk+7zRyij9E2yhFxk3qBbPh3Q+7Lw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2929 bytes --]

On Monday, 30 October 2017 21:04:00 GMT Rich Freeman wrote:
> On Mon, Oct 30, 2017 at 4:50 PM, Dale <rdalek1967@gmail.com> wrote:
> > have we profited on today'.   However, when a company is public, stocks
> > and such, then it is about what have we made today with no one caring
> > about years from now.  After all, the people owning the stocks may not
> > even own them next week.
> 
> Nor should they be concerned with the long-term.  

Not all shareholders flip their stock in milliseconds to front-end retail 
investors in market movements.  There are also few(er) long term investors, 
but they have been crowded out by big banks and hedge fund algo desks.


> This should be the
> role of the regulator.  If the regulator wants spare capacity, then
> they should take bids for companies to have spare capacity available
> and they get paid to just sit on their excess capacity.  If the
> regulator wants more redundancy in the transmission network then they
> should set specifications for what is desired and take bids from those
> able to build it out.  If the regulator wants everything to be
> replaced within a certified lifetime based on testing then they should
> specify this, and take bids from those willing to maintain the grid to
> this standard.

The problem is the regulator is typically a toothless entity, a paper tiger, 
put in place to apply soft touch intervention by issuing corrective notices, 
when step-in required to curtail the abusive behaviour of market participants 
is long overdue.

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.


> The problem is that the general public does not see the value in
> infrastructure, so they don't think about it when they're voting.
> Instead they vote based on whatever fringe issues the politicians want
> them to focus on instead.
> 
> If a company is going to get paid the same whether they build for
> extra reliability or not, they're going to opt not to.  Not only does
> this give them more profits, but it makes their bids more competitive
> vs some other company that would just undercut them for
> "over-providing."

Even worse, on the usual design-build-operate contracts they are often 
motivated to undercut reliability for a more competitive price, hoping to bail 
out of the operate part just as the infrastructure is about to fall apart.


> Lax regulation just punishes conscientious market participants.

On tenders evaluated on a quality:price ratio basis this does not happen as 
often, although it is hard to change entrenched behaviours among competitors.

-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2017-10-30 23:28 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 [this message]
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
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=7158279.1LLyUKUnIt@dell_xps \
    --to=michaelkintzios@gmail.com \
    --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