From owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org  Sun Jul 10 00:05:35 2016
Return-Path: <owner-sc22wg5+sc22wg5-dom8=www.open-std.org@open-std.org>
X-Original-To: sc22wg5-dom8
Delivered-To: sc22wg5-dom8@www.open-std.org
Received: by www.open-std.org (Postfix, from userid 521)
	id 499ED35892C; Sun, 10 Jul 2016 00:05:35 +0200 (CEST)
Delivered-To: sc22wg5@open-std.org
Received: from mail.jpl.nasa.gov (sentrion2.jpl.nasa.gov [128.149.139.106])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by www.open-std.org (Postfix) with ESMTP id DF7EA358287
	for <sc22wg5@open-std.org>; Sun, 10 Jul 2016 00:05:20 +0200 (CEST)
Received: from [137.79.7.57] (math.jpl.nasa.gov [137.79.7.57])
	by smtp.jpl.nasa.gov (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id u69M5DWC024378
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128 bits) verified NO)
	for <sc22wg5@open-std.org>; Sat, 9 Jul 2016 15:05:16 -0700
Subject: Counter argument to the "slow down" sentiment
From: Van Snyder <Van.Snyder@jpl.nasa.gov>
Reply-To: Van.Snyder@jpl.nasa.gov
To: sc22wg5 <sc22wg5@open-std.org>
Content-Type: text/plain; charset="ISO-8859-1"
Organization: Yes
Date: Sat, 09 Jul 2016 15:05:13 -0700
Message-ID: <1468101913.25709.292.camel@math.jpl.nasa.gov>
Mime-Version: 1.0
X-Mailer: Evolution 2.32.3 (2.32.3-36.el6) 
Content-Transfer-Encoding: 7bit
X-Source-Sender: Van.Snyder@jpl.nasa.gov
X-AUTH: Authorized
Sender: owner-sc22wg5@open-std.org
Precedence: bulk

In a message on comp-fortran-90, a correspondent made this remark:

        Unless and until the pace of change can be accelerated and newer
        and better features can be introduced quickly and made
        available, keep in mind this all appears rather moot for
        industry.

I understand the part about "and made available" depends upon available
resources, and each vendor's priorities.  But if we delay specifying new
features, they don't get implemented at all, rather than being
implemented slowly and at different times by each vendor.  I prefer to
have the specs laid down in the standard, not waiting in the wings until
every vendor agrees the feature would be near the top of their
individual customer-base priority list.

I work for an organization whose motto is "Dare Mighty Things."  If we
don't dare anything, we don't accomplish anything.