Computer Old Farts Forum
 help / color / mirror / Atom feed
From: athornton at gmail.com (Adam Thornton)
Subject: [COFF] Popular Programming languages over time
Date: Thu, 19 Mar 2020 13:44:06 -0700	[thread overview]
Message-ID: <CAP2nic3Cdfa=9=rDb3YuP+AzoyBNnt5zy99Qu-xHL+C430EqkA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2NA9HeVidtRSURMB3UPqQL3iaENGuEY42_g4M1HmA0HqA@mail.gmail.com>

PHP was the BASIC of the late 90s and early 2000s; Javascript was (and is)
the BASIC of the subsequent generation.

I mean that, of course, in both good and bad ways, and as someone whose
initial experience was BASIC in the ROMs of Apple IIs and C64s.  Bad in
that neither one is a well-(or even particularly-intentionally) designed
language.  Good in that it's easy to get the results you want with some
iteration and very little theory or formal training; a novice can
bootstrap/cargo-cult something into being pretty easily.

Adam

On Thu, Mar 19, 2020 at 8:04 AM Clem Cole <clemc at ccc.com> wrote:

> I saw that a while ago.  I'd love to know more about the dataset behind it
> as Larry asked,
>
> FWIW: Pascal/Delphi being big did not surprise me as it was what was
> taught in the colleges in the 70s.   Today they are teaching Python and
> Java so we see generations of new programmers going into the world with
> those skills (like my own daughter).
>
> Larry - I think the way to explain Ada, is that it was very big for a
> while when DoD, DoC and some of DoE when USG bids required it.  But as fast
> as it rose, it fell pretty fast from favor.
>
> For me, I'm always amazed at things like Javascript and PHP, but their
> rise is directly mapped to people creating web sites.
>
> On Wed, Mar 18, 2020 at 10:34 PM Larry McVoy <lm at mcvoy.com> wrote:
>
>> I'd like to know where the data came from.  Ada that big?  Says who?
>>
>> On Wed, Mar 18, 2020 at 03:41:22PM -0700, David Barto wrote:
>> > https://www.youtube.com/watch?v=Og847HVwRSI
>> >
>> > It???s kind of amazing how long Pascal hangs on to #1.
>> > And you can watch the ascent of web programming.
>> >
>> >       David
>> > _______________________________________________
>> > COFF mailing list
>> > COFF at minnie.tuhs.org
>> > https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>>
>> --
>> ---
>> Larry McVoy                  lm at mcvoy.com
>> http://www.mcvoy.com/lm
>> _______________________________________________
>> COFF mailing list
>> COFF at minnie.tuhs.org
>> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>>
> _______________________________________________
> COFF mailing list
> COFF at minnie.tuhs.org
> https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20200319/3e38628b/attachment.html>


  parent reply	other threads:[~2020-03-19 20:44 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-18 22:41 david
2020-03-19  2:34 ` lm
2020-03-19 15:04   ` clemc
2020-03-19 15:31     ` pechter
2020-03-19 15:57       ` clemc
2020-03-19 16:01       ` jpl.jpl
2020-03-19 20:44     ` athornton [this message]
2020-03-20  0:29       ` wobblygong

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='CAP2nic3Cdfa=9=rDb3YuP+AzoyBNnt5zy99Qu-xHL+C430EqkA@mail.gmail.com' \
    --to=coff@minnie.tuhs.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;
as well as URLs for NNTP newsgroup(s).