Motivation – Keli Language

Post by csirob » Tue, Sep 01, 2020, 4:21 AM UTC

webmaven wrote: post #270

csirob wrote: post #268

Earlier quoted context omitted.

> If I see "@returns id integer The ID" one more time I'll be tempted to throw my monitor out the window. I honestly believe we're in a dire need for a more up-to-date metaphor that lets us better express our anger at a computer, due to monitors becoming paper thin and lightweight in the past decade or so.

> > If I see "@returns id integer The ID" one more time I'll be tempted to throw my monitor out the window. > I honestly believe we're in a dire need for a more up-to-date metaphor that lets us express our anger at a computer, due to monitors becoming paper thin and lightweight in the past decade or so. My experience may not be representative, but I believe I have encountered variants of "hurl the keyboard at the mon…

Post by genuine_smiles » Tue, Sep 01, 2020, 5:38 AM UTC

mxz3000 wrote: post #235

elwell wrote: post #118

Earlier quoted context omitted.

In Clojure, for functions that will probably have more than a couple args, I like to pass a map, then destructure it by its keys in the function definition. Two benefits are: you don't need to remember the order of args, and it makes refactoring easier in cases where you are simply adding a new optional arg (you don't need to update all the old calls of that function if they aren't using the new option).

That's a pattern I use in a lot of Typescript, it's pretty useful!

  function foo({ bar }: { bar: string }) {

Post by higerordermap » Tue, Sep 01, 2020, 6:55 AM UTC

Post by panzerklein » Tue, Sep 01, 2020, 10:13 AM UTC

csirob wrote: post #268

munk-a wrote: post #251

Earlier quoted context omitted.

I haven't seen evidence of reduced getters & setters in my day to day yet - they still seem pretty prevalent when OOP comes into the picture. I'd even say they got a bit worse because now it's excessive getters and setters with gigantic JavaDoc style comments all around them. If I see "@returns id integer The ID" one more time I'll be tempted to throw my monitor out the window.

> If I see "@returns id integer The ID" one more time I'll be tempted to throw my monitor out the window. I honestly believe we're in a dire need for a more up-to-date metaphor that lets us better express our anger at a computer, due to monitors becoming paper thin and lightweight in the past decade or so.

Post by mattmanser » Tue, Sep 01, 2020, 10:55 AM UTC

munk-a wrote: post #251

mattmanser wrote: post #201

Earlier quoted context omitted.

Maybe in the 00s, but these days most languages have collapsed boiler plate down massively. This comes across as an old fashioned view (bordering on extremely old-fashioned).

I haven't seen evidence of reduced getters & setters in my day to day yet - they still seem pretty prevalent when OOP comes into the picture. I'd even say they got a bit worse because now it's excessive getters and setters with gigantic JavaDoc style comments all around them. If I see "@returns id integer The ID" one more time I'll be tempted to throw my monitor out the window.

    int id;
    public int Id
    {
        get {
          return id;
        }
        set(val) {
            id = val;
        }
     }

    public int Id { get; set; }

    public int Id { get; set; } => generateId();