News for hackers. Stuff that matters.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by jacquesm on Thursday February 22, 2018 @06:10AM (#16436775)
While I'm very much in support of Guido winning this award the 'Its code should be understandable as plain English.' goal was clearly not met.

It is interesting to me because many high level languages have had this exact same goal (COBOL for instance!) and none have ever delivered.

Is Python the language that comes closest to this goal? And if not, which is?

Re:Computer History Museum 2018 Fellow: Guido van Rossum by elcapitan on Thursday February 22, 2018 @07:55AM (#16437199)
I'm not sure closeness to natural language is necessarily something you would want. I remember some super painful experiments with AppleScript (https://en.wikipedia.org/wiki/AppleScript) 10 years ago, which really pushed me away from that ideal. The languageification of a programming language creates a lot of cruft.

    if the text returned of (display dialog "Username" default answer "") is userAns

Similar issues can be seen in some of the monstrosities created as ruby DSLs, for example in rspec

    expect(true).to eq true
where it becomes hard to understand what's actually going on.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by wolfgang42 on Thursday February 22, 2018 @01:18PM (#16439854)
HyperTalk came closer than anything else I'm aware of to this ideal:

    ask "Username"
    if it is "Harry" then put "Hi there, Harry!" into field Greeting
    else put "Hey, you're not Harry, you're" && it into field Greeting
Re:Computer History Museum 2018 Fellow: Guido van Rossum by moomin on Thursday February 22, 2018 @07:24AM (#16437044)
Once you've accepted the need for precision in computer code, it becomes apparent that the correct standard is "as understandable as legal English". I don't think we're doing too bad on that metric.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by benhoyt on Thursday February 22, 2018 @07:37AM (#16437110)
I hereby declare, proclaim, and certify that I consider the Python programming language no less than 100 times as understandable, clear, and readable than English written for a legal, formal, or legislative context.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by elcapitan on Thursday February 22, 2018 @07:29AM (#16437068)
I wish "plain English" was as understandable as python.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by gnclmorais on Thursday February 22, 2018 @06:15AM (#16436799)
I would say Ruby is closer to the dream than Python.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by glaberficken on Thursday February 22, 2018 @06:27AM (#16436840)
Could you give an example code snippet that "reads more naturally" in Ruby than in Python?

I'm an amateur programmer (Python, JS) and I have been wondering for a long time if there is a language more readable than python.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by aianus on Thursday February 22, 2018 @08:16AM (#16437307)
1) Multi-line lambdas (no equivalent in python afaik):

  collection.map do |i|
    blah = something(i.something)
    blah.something_else
  end
2) Easily chainable object methods instead of weird global functions:

  a.length
  collection.map { |x| x^2 }
vs

  len(a)
  map(lambda x: x^2, collection)

3) Closing braces instead of whitespace make it a lot easier to judge indentation level
Re:Computer History Museum 2018 Fellow: Guido van Rossum by pvg on Thursday February 22, 2018 @08:28AM (#16437373)
The 'equivalent' for that sort of thing in Python these days is comprehensions. The other stuff is pretty subjective. There is a blurb in the FAQ about things like 'len' and it makes the argument it's more readable.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by santiagobasulto on Thursday February 22, 2018 @07:17AM (#16437015)
I don't think that's true. Both Python and Ruby are readable enough. Both languages encourage good practices in different ways. I'm a 100% Python developer, but I like many ideas of Ruby; for example, the convention of using question marks to indicate that a method returns a boolean.

When you're working in a large project with +10K LOC, the project structure and the quality of the code you write is much more important than the language itself.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by gnclmorais on Thursday February 22, 2018 @09:23AM (#16437680)
If we’re talking about Rails, even there Ruby is possibly better. Rails has been around for a long time and its community is very clear on readability and maintenance.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by pmontra on Thursday February 22, 2018 @08:41AM (#16437436)

    10.times do
       something
    end

    (1..10).each do |i|
      something_with i
    end
Re:Computer History Museum 2018 Fellow: Guido van Rossum by joshuamorton on Thursday February 22, 2018 @12:09PM (#16439129)

    for _ in range(10):
        something

    for i in range(10):
        something_with(i)
Can you explain why the Ruby reads more naturally?

The major differences, as I see them are that ruby requires end blocks, and uses methods instead of global functions for things.

In my opinion, python takes great pains to make things consistent, which is valuable. There's one function, range, instead of two methods, times and each. The syntax is unified: `for N in range`, which `_` being a convention if `N` is unused, as opposed to Ruby where you can define the looping variable, or not, depending on the method that was called (I guess?).

Ruby does appear to read more like something you might say, although still with weirdish grammar, but on the other hand, replace ":" with "repeat" and be explicit about the elided 0 in range, and you get "for i in the range 0 to 10, repeat something with i" which is english, as opposed to Ruby which is "take the range 1-10 and for each do unto i something with i", which imo appears significantly less natural.

This actually extend's to the stuff about "len" vs ".length", where you're asking which is more natural, to "do something to the length of X" or "do something to X's length". And that's very much a subjective question, but Python's answer establishes stronger consistency.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by pmontra on Sunday March 04, 2018 @02:47PM (#16516259)
IMHO (1..10) is much more explicit than range(10). No questions about what it is. Where does range(10) starts from? -infinity, 0, 1? Or where does it ends at? Is 10 the starting point? Probably not but who knows. One should read the manual for that. BTW I hate Ruby's three dots (1...10) because it's (1..9) and I never remember which one is what when I find it in somebody's else code. Languages should not trick developers into mistakes. I only write the two dots.

However:

1) if one comes from Ruby, then Python is a Ruby designed by someone with a weird mind

2) if one comes from Python, then Ruby is a Python designed by someone with a weird mind

I'm coming from Ruby, a historical accident I can't change. No hard feelings.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by gnclmorais on Thursday February 22, 2018 @09:24AM (#16437684)
Adding the the examples aianus posted here, Ruby needs no `__self__` or `self` being passed everywhere. You only use `self` when you really need it.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by unixhero on Thursday February 22, 2018 @07:32AM (#16437086)
print "yes".reverse

-> sey

Quite readable and fun. I've never loved a language like I do Ruby. Everytime I am stuck, and find a simple, fun and elegant solution I like it even more.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by sannee on Thursday February 22, 2018 @02:03PM (#16440355)
If you spend as much time learning Python as you spent learning english, it would likely be much more understandable than english.

On the other hand, maybe there is some upper limit as to how well can humans internalize programming concepts.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by the-dude on Thursday February 22, 2018 @07:05AM (#16436971)
BASIC, Logo
Re:Computer History Museum 2018 Fellow: Guido van Rossum by shakna on Thursday February 22, 2018 @07:49AM (#16437177)
> Is Python the language that comes closest to this goal? And if not, which is?

In the end, it's subjective. And "understandable" and "plain English" may not sit together well, as it can lead to overly verbose code.

But, here's a few examples for you to judge between. (Examples lifted from RosettaCode, which is well worth the look.)

All these languages have claimed, at some time or another, to be easy to read, and close to "plain English". Obviously, this is just a taste.

Python

    def fib(n,x=[0,1]):
       for i in range(abs(n)-1): x=[x[1],sum(x)]
       return x[1]*pow(-1,abs(n)-1) if n<0 else x[1] if n else 0

    for i in range(-30,31): print fib(i),
Ada (A safety-oriented language)

    with Ada.Text_IO, Ada.Command_Line;
    procedure Fib is
        X: Positive := Positive'Value(Ada.Command_Line.Argument(1));

       function Fib(P: Positive) return Positive is
       begin
          if P <= 2 then
             return 1;
          else
             return Fib(P-1) + Fib(P-2);
          end if;
       end Fib;
 
    begin
       Ada.Text_IO.Put("Fibonacci(" & Integer'Image(X) & " ) = ");
       Ada.Text_IO.Put_Line(Integer'Image(Fib(X)));
    end Fib;
AppleScript (Seeing less support from Apple these days, but part of macOS)

    on fib(n)
        if n < 1 then
            0
        else if n < 3 then
            1
        else
            fib(n - 2) + fib(n - 1)
        end if
    end fib
BASIC (Easy to read, easy to use, easy to get lost.)

    FUNCTION itFib (n)
        n1 = 0
        n2 = 1
        FOR k = 1 TO ABS(n)
            sum = n1 + n2
            n1 = n2
            n2 = sum
        NEXT k
        IF n < 0 THEN
            itFib = n1 * ((-1) ^ ((-n) + 1))
        ELSE
            itFib = n1
        END IF
    END FUNCTION
Clojure (A modern Lisp, bits of Scheme, Common Lisp and Java)

    (defn fibs []
      (map first (iterate (fn [[a b]] [b (+ a b)]) [0 1])))
COBOL, it's so ridiculously verbose, I'm not adding it here. See https://www.rosettacode.org/wiki/Fibonacci_sequence#COBOL

CoffeeScript (Billed as a better JavaScript, it was popular until ES2016)

    fib_rec = (n) ->
      if n < 2 then n else fib_rec(n-1) + fib_rec(n-2)
Delphi (One of my first programming languages. Probably the least verbose staticly typed language without inference I've seen.)

    function FibonacciI(N: Word): UInt64;
    var
      Last, New: UInt64;
      I: Word;
    begin
      if N < 2 then
        Result := N
      else begin
        Last := 0;
        Result := 1;
        for I := 2 to N do
        begin
          New := Last + Result;
          Last := Result;
          Result := New;
        end;
      end;
    end;
 
Elixir (Kinda like Ruby, but running atop Erlang's massively-concurrent VM.)

    defmodule Fibonacci do
        def fib(0), do: 0
        def fib(1), do: 1
        def fib(n), do: fib(0, 1, n-2)
 
        def fib(_, prv, -1), do: prv
        def fib(prvprv, prv, n) do
            next = prv + prvprv
            fib(prv, next, n-1)
        end
    end
 
    IO.inspect Enum.map(0..10, fn i-> Fibonacci.fib(i) end)
Elm (A new language for the web. More a framework that replaces HTML, CSS and JS than just JS.)

    fibonacci : Int -> Int
    fibonacci n = if n < 2 then
            n
        else
            fibonacci(n - 2) + fibonacci(n - 1)
FORTRAN (I've done too much professional work with FORTRAN to like it. It looks straight-forward, but you can do pretty much whatever you feel like with memory, and it'll let you.)

      FUNCTION IFIB(N)
      IF (N.EQ.0) THEN
        ITEMP0=0
      ELSE IF (N.EQ.1) THEN
        ITEMP0=1
      ELSE IF (N.GT.1) THEN
        ITEMP1=0
        ITEMP0=1
        DO 1 I=2,N
          ITEMP2=ITEMP1
          ITEMP1=ITEMP0
          ITEMP0=ITEMP1+ITEMP2
    1   CONTINUE
      ELSE
        ITEMP1=1
        ITEMP0=0
        DO 2 I=-1,N,-1
          ITEMP2=ITEMP1
          ITEMP1=ITEMP0
          ITEMP0=ITEMP2-ITEMP1
    2   CONTINUE
      END IF
      IFIB=ITEMP0
      END
Go (Google's somewhat naive language, can be odd to set up, but is fast, static and fairly readable. Lots of people switch from Python to Go.)

    func fib(a int) int {
      if a < 2 {
        return a
      }
      return fib(a - 1) + fib(a - 2)
    }
Julia (It's a language aimed at scientific application. That means a great number system, a really good compiler, and access to things you usually need FORTRAN for.)

    fib(n) = n < 2 ? n : fib(n-1) + fib(n-2)
Lua (Fast but small. Standard library isn't much bigger than C, but has LuaRocks, a decent package manager, with an active community. Some think of it as a better JavaScript, though it was designed for embedding and has a fantastic C-interop story.)

    function fibs(n) 
      return n < 2 and n or fibs(n - 1) + fibs(n - 2) 
    end
Nim (Think Python, but staticly typed, and much faster.)

    proc Fibonacci(n: int): auto =
      var fn = float64(n)
      var p: float64 = (1.0 + sqrt(5.0)) / 2.0
      var q: float64 = 1.0 / p
          return int64((pow(p, fn) + pow(q, fn)) / sqrt(5.0))
Re:Computer History Museum 2018 Fellow: Guido van Rossum by analog31 on Thursday February 22, 2018 @08:16AM (#16437311)
To be fair, here's plain English (from Wikipedia, re-entered by me):

The sequence f(n) of Fibonacci numbers is defined by the recurrence relation:

f(n) = f(n-1) + f(n-2),

with seed values

f(0) = 0 and f(1) = 1

And a possible variant in Python:

    f = [0, 1]
    for i in range(100):
        f.append(f[-1] + f[-2])
Re:Computer History Museum 2018 Fellow: Guido van Rossum by joshuamorton on Thursday February 22, 2018 @12:15PM (#16439193)
heck, if you really want that:

    @functools.lru_cache
    def fibs(n):
        if n == 0:
            return 0
        elif n == 1:
            return 1
        else:
            return fibs(n-1) + fibs(n-2)
Technically you could also write it as

    def f(n):
        if n in {0, 1}:
            return n
        return f(n-1) + f(n-2)
which is a bit trickier, but arguably better matches the way the seed values are described in english.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by detaro on Thursday February 22, 2018 @08:04AM (#16437245)
What's totally missing from this comparison is that languages allow multiple styles. E.g. the Python variant is for some reason not recursive, and you could write a Python version that looks a lot more like the Go or Lua versions than this Python version. (Which also can be seen as a weakness of Python from a readability point of view: freedom to choose a style also means you can pick the wrong one or a reader can be surprised by more uncommon one)
Re:Computer History Museum 2018 Fellow: Guido van Rossum by shakna on Thursday February 22, 2018 @08:10AM (#16437272)
For the most part, I tried to choose styles that match the language, but yes, just a taste of the languages.

> E.g. the Python variant is for some reason not recursive

Because of the recursion limit in Python, really, as Python doesn't do tail-call elimination. That limit can make recursive code a real pain point, so iterative styles tend to work better.

Re:Computer History Museum 2018 Fellow: Guido van Rossum by dom96 on Thursday February 22, 2018 @08:30AM (#16437380)
Where did you find the Nim example? It's by far the strangest fibonacci implementation I have seen (and I am a Nim developer).

Anyway, I translated the Go example to Nim for a better comparison:

    proc fib(a: int): int =
      if a < 2:
        return a
      return fib(a - 1) + fib(a - 2)
Re:Computer History Museum 2018 Fellow: Guido van Rossum by detaro on Thursday February 22, 2018 @08:27AM (#16437363)
Many of these programs do not get tail-call elimination (e.g. I think most languages can not automatically optimize the equivalent of "return f(n-1) + f(n-2)", if they do tail-call elimination at all). The nicest ones do not bother with negative n, some others don't. IMHO not a very useful set of comparisons.
Re:Computer History Museum 2018 Fellow: Guido van Rossum by joshuamorton on Thursday February 22, 2018 @12:16PM (#16439205)
As I mentioned elsewhere, in python the correct way would be to add the @functools.lru_cache decorator. That way you get the caching behavior of the tricky to write methods, with the clarity of the obvious recursive solution.