News for hackers. Stuff that matters.
Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:56AM (#32374996)
Sound like a typical Rob Pike design. Idiosyncratic, not that user friendly, and mostly "works for me" affair (considering things like the Sam editor and parts of Golang).
Re:Ivy – An interpreter for an APL-like language by EdiX on Sunday August 07, 2022 @06:34AM (#32375391)
> Sound like a typical Rob Pike design

It's actually from APL.

Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:32PM (#32379614)
Yes, but adopted to taste, and adopted by a person who shared the design sensibility
Re:Ivy – An interpreter for an APL-like language by samatman on Sunday August 07, 2022 @07:53AM (#32375776)
I wouldn't describe UTF-8 in those exact terms!
Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:33PM (#32379623)
True. That would be the Ken Thompson influence!
Re:Ivy – An interpreter for an APL-like language by pverghese on Sunday August 07, 2022 @11:05AM (#32377036)
Rubbishing someones character for a design choice is just too extreme. Sounds like you have something personal against Rob Pike rather than anything constructive to add
Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:49PM (#32379755)
This is about design tendencies.

Not about character in general, much less about "rubbishing" it.

In light of this, "sounds like you have something personal against Rob Pike", is moot.

Re:Ivy – An interpreter for an APL-like language by Jabbles on Sunday August 07, 2022 @05:44AM (#32375181)
Given that Go does not have the same syntax, you cannot claim that these are examples of "typical Rob Pike design".
Re:Ivy – An interpreter for an APL-like language by masklinn on Sunday August 07, 2022 @05:46AM (#32375189)
GP's not talking about this specific syntax but about Rob Pike's general approach to language and system design.

A flagrant example of

> idiosyncratic, not that user friendly, and mostly "works for me" affair

being date/time patterns in Go.

Re:Ivy – An interpreter for an APL-like language by jasonwatkinspdx on Sunday August 07, 2022 @09:39AM (#32376379)
Except that comment is just straight up wrong.

This approach to precedence comes straight from Iverson and APL itself. Iverson originally started out designing a more uniform mathematical notation. It developed into a programming language secondary to that. Note that J, K, and others in this family all duplicate this choice largely. And there's mainstream languages that have chosen the middle ground of allowing basic precedence for + - * / expressions but require explicit grouping otherwise.

It's not a particularly outlandish idea.

So attributing it to Rob Pike's personality traits is just off the mark. It's ok to be critical but it should be specific and informed, not just bashing someone character as a whole, and if you're gonna take it that far, you'd probably better at least know what you're actually talking about.

And note I've been critical of Rob's choices and behavior surrounding Go's date/time on a particular issue, so note this isn't empty hero worship on my part.

Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:38PM (#32379664)
>So attributing it to Rob Pike's personality traits is just off the mark

That's fine, since I didn't speak about Pike's "personality traits", but to his architecure/design tendencies.

And I didn't attribute this design to him. I know of APL, and even if I didn't the influence is right there in the TFA title. I compared it to his designs ("sounds like a typical Rob Pike design"), i.e. he adopted it because he does have these design tendencies, and so this was to his taste.

>not just bashing someone character as a whole

Where exactly are you getting that from? As if I've called him a "bad person" or something?

Re:Ivy – An interpreter for an APL-like language by Jabbles on Sunday August 07, 2022 @06:24AM (#32375343)
You can't just cherrypick examples and say this is typical.

Even worse, you (GP) can't say this is typical without providing any examples when the most obviously relevant analogy (precendence in Go) does not support your statement.

Re:Ivy – An interpreter for an APL-like language by eis on Sunday August 07, 2022 @06:44AM (#32375449)
You are misunderstanding his point even though masklinn explained it. It's not about the specific point of operator precedence. It is about designing something that has internally sound logic but is very unexpected by a typical new user. And he provided the example of time package patterns in Go which imho fits very well. Yea it makes sense but I'm sure there are hordes of users that think "why doesn't this work like in virtually every other language?".

It's probably good to not take the "typical" too literally and more as a "Rob Pike has done a few designs in the past that have this quality".

Re:Ivy – An interpreter for an APL-like language by mseepgood on Sunday August 07, 2022 @04:34PM (#32379642)
> "why doesn't this work like in virtually every other language?

What's the point in creating something new if you simply repeat what already exists?

Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:42PM (#32379700)
Doing it better in other aspects (e.g. 100% same design but faster or safer, etc.)?

Refactoring?

Making a FOSS version?

Learning?

Doing it in Rust because it's fashionable?

Competition with an existing player in the same market?

And lots of other reasons besides...

Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:40PM (#32379681)
It's not about the particular intepreter or specific precedence design, it's about the tendecies described: what kind of stuff he often appears to like and/or produce.

Now, you might disagree with that, but at least disagree with what I tried to say, not what I didn't mean :)

Re:Ivy – An interpreter for an APL-like language by indymike on Sunday August 07, 2022 @08:25AM (#32375934)
The op was commenting Rob Pike's body of work and Ivy's operator precedence certainly does fit this description to a tee.
Re:Ivy – An interpreter for an APL-like language by ducktective on Sunday August 07, 2022 @06:27AM (#32375357)
Are the `-option` thing in Go CLI apps and method capitalization (`myobject.GetStuff()`) other examples of these idiosyncraticies?
Re:Ivy – An interpreter for an APL-like language by coldtea on Sunday August 07, 2022 @04:47PM (#32379737)
The -option I'd say yes. Although this is vintage UNIX style behavior, in 2009, when Golang emerged, it should have picked GNU-style. No reason except idiosyncrasy or nostalgia to go with single dash.

For method capitalization, I'd say no, as this is the case in any other popular languages too (C# to name but one).

Re:Ivy – An interpreter for an APL-like language by masklinn on Thursday August 11, 2022 @07:54AM (#32424323)
The capitalisation itself isn’t idiosyncratic (though it seems uncommon in the unix world), however that having a semantic impact is rather rare.

Not completely unique (e.g. variables v symbols in erlang, concrete type v generic placeholder in haskell) but really rare, and usually the capitalisation isn’t a switchable thing, it’s a very fixed meaning.