On Tue, Mar 16, 2021 at 12:00 PM Space A. <reexist...@gmail.com> wrote:
> There is always a "discussion", most people (as well as I) will look only > at the final version of proposal, if and when they have time. And what's > the point of having formal proposals if you don't respect that process? > Once you published, please notify everyone and give them time to come back > with critics. Or just do what you do, but don't tell me or anyone that > there is any "community" behind, "decade of discussion" and all that stuff. > This seems very dismissive of the many members of the community which *did* invest the time and energy to discuss the design for the past years. When the contracts design was announced in 2018 <https://blog.golang.org/go2draft>, the process was explained. Including the fact that it is a draft, which will see several revisions, that this process will likely take a couple of years and how we can participate in it. Many of us have seen that announcement and understood it for what it was and thus - even if (like me) they were opposed to the idea of generics in Go - decided to participate in it to do their best to ensure the outcome was a good design or a rejection. So, no offense, but I don't understand how you could in good faith argue that the community was not involved, the process not respected or the intention not announced. It was announced on the largest Go conference in the world, accompanied by a blog post and several threads on golang-nuts and golang-dev. With regular updates on the progress, again at most of the large Go conferences, the blog, on this mailing list, several times on the largest community-run Go podcast and in basically every medium I can think of. If you didn't want or didn't have the time to participate in the process, that's certainly unfortunate. But I believe it is fair to say that the Go team went above and beyond to make the process as broadly accessible and known as they can. And are you saying that "consensus" is how many emojis "up", "down" or > "confused" were collected? You know that it's pretty easy to cheat with > that system right? > Not to point out the obvious, but you where the first person in this thread to ask for a poll. And Ian has been pretty clear about the flaws of that idea and that it's not how the Go project is run. Again, it is very hard to interpret your words and actions in good faith here. > > > > > вт, 16 мар. 2021 г. в 01:03, Ian Lance Taylor <i...@golang.org>: > >> On Mon, Mar 15, 2021 at 5:08 AM Space A. <reexist...@gmail.com> wrote: >> > >> > > For example, the multiple proposals that flowed out of >> > >> https://go.googlesource.com/proposal/+/master/design/go2draft-error-handling-overview.md >> . >> > None of them have been adopted. >> > >> > I remember what was happening to "try" error handling proposal. It was >> withdrawn only because of active resistance by the community. >> > >> > And what's happened to a new "generics" proposal, it also got a lot of >> critics but was "accepted" in less than a month after formal publication on >> github. As Russ said "No change in consensus". What does it mean? Who are >> these people who can change the consensus? How was it measured? A few days >> after Russ locked it, so nobody can even say a word against it if they >> wanted. So it looks very much that company management learned from "try" >> proposal. >> >> The design draft was put up for discussion for months before it became >> a formal proposal. It was not new. >> >> The formal proposal (https://golang.org/issue/43651) got 1784 thumbs >> up and 123 thumbs down (and ten "confused"). Yes, there were critics. >> But I think it is fair to say that the proposal has far more >> supporters than critics. >> >> The "no change in consensus" comment refers to the discussion after >> the proposal was moved to "likely accept" status: >> https://github.com/golang/go/issues/43651#issuecomment-772744198. >> After it was marked as "likely accept", there was no change to the >> consensus that it should be accepted. (Note that the "likely accept" >> comment got 60 thumbs up and 0 thumbs down (and one "confused").) >> >> None of this is anything like the "try" proposal >> (https://golang.org/issue/32437), which had 318 thumbs up and 794 >> thumbs down (and 132 "confused"). >> >> Ian >> > -- You received this message because you are subscribed to the Google Groups "golang-nuts" group. To unsubscribe from this group and stop receiving emails from it, send an email to golang-nuts+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/golang-nuts/CAEkBMfGbAYQxCoCgL4kofLEdAgV1KvP_62Vo8j9PMJ7Nz9LnnA%40mail.gmail.com.
