Re: [go-nuts] Re: Go 1.8.1 is released

[Micky]

It's just politics!

Simply use a VPN, Tor or a proxy to bypass the filter!

On Sun, May 7, 2017 at 8:59 PM, ahochauwa 
wrote:

> Hello,
>
> This issue might help you understand why:
> https://github.com/golang/go/issues/12380
>
> I hope one day Golang would be available without any restrictions :-(
>
> Yoshiyuki
>
> 2017/05/08 0:36、abbasnagh...@gmail.com:
>
> Why the Iranians have blocked?
> Is free and open source language golang?
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Go Fonts: request for feedback

[Micky]

There are several characteristics of a typeface, which only a typeface
designer can truly understand (unless I'm mistaken if you're one). In
particular, the non-uniform ascenders, crossbar and apex of humanistic
style give the font it's weird typical classic shape.

Most people would know about this non-modern look when I referred to other
modern fonts in my previous reply.

On Sat, Feb 4, 2017 at 11:39 AM, andrey mirtchovski <mirtchov...@gmail.com>
wrote:

> I think the original asked for what exactly is bugging you about the
> font, not a general statement that somebody somewhere doesn't like it
> with a link to a broad discussion on the subject of programming fonts.
> Do you have anything that bothers you about them, maybe in
> relationship with the list of fonts that you cited? What's not
> "looking great" to you?
>
> On Fri, Feb 3, 2017 at 11:20 PM, Micky <mickylmar...@gmail.com> wrote:
> > This is a nice initiative.
> >
> > But the font doesn't look great compared to what we already have in the
> OSS
> > toolbelt, e.g. Roboto, Inconsolata, Fira, Open Sans, Office Code, etc.
> >
> > I was hoping for something more extravagant.  Like most people on Hacker
> > News, the font doesn't give me butterflies.
> >
> > That obviously doesn't mean, why others won't find it useful in their
> > projects.
> >
> >
> > On Fri, Feb 3, 2017 at 5:25 AM, Nigel Tao <nigel...@golang.org> wrote:
> >>
> >> Bigelow & Holmes, the designers of the Go Fonts, are preparing an
> >> update to those fonts. The changes so far are:
> >>
> >> • adjusted box/chart/shade/split-integral to align vertically
> >> • adjusted shade characters to align vertically & horizontally (more
> >> or less aesthetically)
> >> • merged the contours of ring of Aring U+00C5 with the A
> >> • renamed U+02C9 -> uni02C9 in Bold and Bold Italic to conform to name
> >> in Regular and Italic and avoid name conflict with "macron"
> >> • added U+FFFD "Replacement" character
> >>
> >> If you have any other bug reports, feature requests, or just like to
> >> comment in general, please reply to the discussion group here, and
> >> I'll pass it on to B
> >>
> >> --
> >> 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.
> >> For more options, visit https://groups.google.com/d/optout.
> >
> >
> > --
> > 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.
> > For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Go Fonts: request for feedback

[Micky]

This is a nice initiative.

But the font doesn't look great compared to what we already have in the OSS
toolbelt, e.g. Roboto, Inconsolata, Fira, Open Sans, Office Code, etc.

I was hoping for something more extravagant.  Like most
 people on Hacker News, the
font doesn't give me butterflies.

That obviously doesn't mean, why others won't find it useful in their
projects.

On Fri, Feb 3, 2017 at 5:25 AM, Nigel Tao  wrote:

> Bigelow & Holmes, the designers of the Go Fonts, are preparing an
> update to those fonts. The changes so far are:
>
> • adjusted box/chart/shade/split-integral to align vertically
> • adjusted shade characters to align vertically & horizontally (more
> or less aesthetically)
> • merged the contours of ring of Aring U+00C5 with the A
> • renamed U+02C9 -> uni02C9 in Bold and Bold Italic to conform to name
> in Regular and Italic and avoid name conflict with "macron"
> • added U+FFFD "Replacement" character
>
> If you have any other bug reports, feature requests, or just like to
> comment in general, please reply to the discussion group here, and
> I'll pass it on to B
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Deleting the /r/golang subreddit

[Micky]

I don't think people realize the gravity of the situation, of what Brad
pointed out.

If I said something (which in reality I never said) and if someone responds
back to me in a way (which they never did), it could have serious
implications on the parties conversing on a topic -- particularly when the
nature of conversation is, software!

(I know people will say they are other mediums of communication but think
of security issues, etc.)

On Fri, Nov 25, 2016 at 4:53 AM, Brad Fitzpatrick 
wrote:

> In light of the CEO of Reddit admitting to editing user comments (see
> dozen news stories today), I propose we delete the /r/golang subreddit.
>
> That is so beyond unethical and immature, I no longer want anything to do
> with that site. I will be deleting my account on Reddit after backing up my
> content, and I will no longer be a moderator of /r/golang.
>
> If other moderators of /r/golang feel strongly that it should remain, I
> suppose you're welcome to keep it going.
>
> But if the other moderators want to abandon it and focus our conversation
> elsewhere (or build a replacement), I'm happy to just delete /r/golang.
>
> Opinions?
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] why this?

[Micky]

TL, the simplest reason is this:

You can live without the "ok idiom" when retrieving a map value but you
cannot when type asserting. Think of the consequences for rest of your
program, if you forgot to check the status of assertion that is failed (but
you didn't know) because the compiler didn't panic! It would be a travesty.

For compiler's perspective, see Andrey's response.

On Thu, Sep 29, 2016 at 10:06 AM, Henrik Johansson <dahankz...@gmail.com>
wrote:

> I am not sure but perhaps as simple as it is a very natural and known
> behavior of maps and to make it work syntactically as the type assertion
> would make it weird.
>
> On Thu, Sep 29, 2016, 07:02 T L <tapir@gmail.com> wrote:
>
>>
>>
>> On Thursday, September 29, 2016 at 12:56:57 PM UTC+8, Micky wrote:
>>>
>>> The reason is directly stated in the Go language spec:
>>>
>>> "If the type assertion holds, the value of the expression is the value
>>> stored in x and its type is T. If the type assertion is false, a run-time
>>> panic <https://golang.org/ref/spec#Run_time_panics> occurs."
>>>
>>> Here "hold" means if it succeeds.
>>>
>>>
>> I know of the syntax in spec.
>> I just want to understand what is the deep reason for the syntax
>> inconsistency between map index and type assert.
>>
>>
>>>
>>> On Thu, Sep 29, 2016 at 9:53 AM, T L <tapi...@gmail.com> wrote:
>>>
>>>>
>>>>
>>>> On Thursday, September 29, 2016 at 12:32:48 PM UTC+8, Henrik Johansson
>>>> wrote:
>>>>>
>>>>> This is just how type assertion works.
>>>>> If you don't use the dual return it panics if the actual type is
>>>>> different from the one you try to assert.
>>>>>
>>>>
>>>> but what is the underlining reason for the inconsistency between map
>>>> index and type assert?
>>>>
>>>>
>>>>>
>>>>> On Thu, Sep 29, 2016, 05:26 T L <tapi...@gmail.com> wrote:
>>>>>
>>>>>> package main
>>>>>>
>>>>>> func main() {
>>>>>> var m = map[string]int{}
>>>>>> _, _ = m["abc"] // ok
>>>>>> _ = m["abc"] // ok
>>>>>>
>>>>>> var i interface{} = 789
>>>>>> _, _ = i.(bool) // ok
>>>>>> _ = i.(bool) // panic: interface conversion: interface is int,
>>>>>> not bool
>>>>>> }
>>>>>>
>>>>>> --
>>>>>> 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...@googlegroups.com.
>>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>>
>>>>> --
>>>> 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...@googlegroups.com.
>>>> For more options, visit https://groups.google.com/d/optout.
>>>>
>>>
>>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.
>>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] why this?

[Micky]

The reason is directly stated in the Go language spec:

"If the type assertion holds, the value of the expression is the value
stored in x and its type is T. If the type assertion is false, a run-time
panic  occurs."

Here "hold" means if it succeeds.


On Thu, Sep 29, 2016 at 9:53 AM, T L  wrote:

>
>
> On Thursday, September 29, 2016 at 12:32:48 PM UTC+8, Henrik Johansson
> wrote:
>>
>> This is just how type assertion works.
>> If you don't use the dual return it panics if the actual type is
>> different from the one you try to assert.
>>
>
> but what is the underlining reason for the inconsistency between map index
> and type assert?
>
>
>>
>> On Thu, Sep 29, 2016, 05:26 T L  wrote:
>>
>>> package main
>>>
>>> func main() {
>>> var m = map[string]int{}
>>> _, _ = m["abc"] // ok
>>> _ = m["abc"] // ok
>>>
>>> var i interface{} = 789
>>> _, _ = i.(bool) // ok
>>> _ = i.(bool) // panic: interface conversion: interface is int, not
>>> bool
>>> }
>>>
>>> --
>>> 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...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] image: algorithm to convert to grayscale

[Micky]

On Thu, Sep 29, 2016 at 3:19 AM, Rodolfo Carvalho 
wrote:

> gift [3]:
> y := 0.299*px.R + 0.587*px.G + 0.114*px.B
>
> I did not understand why image/color adds an extra 0.5 (500/1000) to y.
> Could anybody give me a clue?
>

To directly answer your question:

*GIFT also adds 0.5 to round off. *

Wanna know where? Try to make up a call stack:

gift.Grayscale() > returns Filter > is colorFilter > has a callback fn >
returns pixel > contains float32s

pixel is a struct containing float32s
Filter is an interface, made of Draw() and Bounds()
colorFilter implements Filter

So, it eventually boils down to: [1]

*colorFilter.Draw() > parallelize() > newPixelSetter().SetPixel() >
f32u16()

color.Color uses uint32s while gift.pixel uses float32s. I guess gift uses
floats for cosmetic reasons. But they both round off while applying the
grayscale filter.

[1]
https://github.com/disintegration/gift/blob/703be73d60d8baeaa84c47be0d31551b466ea84a/pixels.go#L304

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

[Micky]

Thanks for the correction :-)

On Thu, Sep 29, 2016 at 2:26 AM, Dave Cheney <d...@cheney.net> wrote:

> s/go build/go install/g
>
> On Thursday, 29 September 2016 01:41:31 UTC+10, Micky wrote:
>>
>> go list ...
>> go build ...
>>
>> It will build only if it it needs to! Otherwise add -a to force.
>>
>> On Wed, Sep 28, 2016 at 8:30 PM, Tim K <tim@gmail.com> wrote:
>>
>>> OK, so all that should happen is just re-install the binaries in
>>> $GOPATH/bin. Does anyone have any tips or helper scripts that help automate
>>> re-installing all these binaries? There's a pile of them which makes it a
>>> bit difficult to find out what exact package path they came from so they
>>> can be rebuilt.
>>>
>>> Thanks!
>>>
>>>
>>> On Wednesday, September 28, 2016 at 7:43:18 AM UTC-7, Chris Hines wrote:
>>>>
>>>> I'm pretty sure that the last few versions of Go (since 1.5 maybe) are
>>>> smart enough to do it automatically. I believe the .o files in the pkg tree
>>>> have the compiler version embedded in their meta data for this purpose.
>>>
>>> --
>>> 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...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] Re: do packages need to be recompiled when Go is upgraded?

[Micky]

go list ...
go build ...

It will build only if it it needs to! Otherwise add -a to force.

On Wed, Sep 28, 2016 at 8:30 PM, Tim K  wrote:

> OK, so all that should happen is just re-install the binaries in
> $GOPATH/bin. Does anyone have any tips or helper scripts that help automate
> re-installing all these binaries? There's a pile of them which makes it a
> bit difficult to find out what exact package path they came from so they
> can be rebuilt.
>
> Thanks!
>
>
> On Wednesday, September 28, 2016 at 7:43:18 AM UTC-7, Chris Hines wrote:
>>
>> I'm pretty sure that the last few versions of Go (since 1.5 maybe) are
>> smart enough to do it automatically. I believe the .o files in the pkg tree
>> have the compiler version embedded in their meta data for this purpose.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.
>

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] What 5 things does Go need in 2017?

[Micky]

Go doesn't need anything. You just need to write more code ;)

On Sun, Sep 11, 2016 at 6:43 PM, Mark Richman  wrote:
> I'm somewhat new to the community, and seek to understand its challenges
> better. I'm also looking for opportunities to contribute.
>
> To that end, what 5 things does Go need in 2017?
>
> For example: language features, tooling, advocacy, community, platform
> support, etc.
>
> --
> 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.
> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.

Re: [go-nuts] A proposal for generic in go

[Micky]

I guess that's for diplomatic reasons. If you watch talks of core
contributors then I believe you'll know what I mean :)

On Tue, Jun 21, 2016 at 5:15 AM, Rodrigo Kochenburger <div...@gmail.com> wrote:
> Micky, I'm not sure where you're quoting from but they never said it's never
> gonna happen.
>
> From the FAQ: "Generics may well be added at some point." and "This remains
> an open issue".
>
> https://golang.org/doc/faq#generics
>
>
> On Mon, Jun 20, 2016 at 4:54 PM Micky <mickylmar...@gmail.com> wrote:
>>
>> It's never going to happen! To quote the powers-to-be, "The language is
>> done".
>> Good luck!
>>
>> On Wed, Jun 15, 2016 at 6:04 AM, xingtao zhao <zhaoxing...@gmail.com>
>> wrote:
>> > Here is my proposal for generic in go:
>> >
>> > https://docs.google.com/document/d/1nO7D15c2B3eq2kF62C0yUs_UgpkyPL2zHhMAmlq1l98/edit?usp=sharing
>> >
>> > Many parts has not been finished, and just initial thoughts. In the
>> > proposal, I want to keep back compatibility. And I try to add the
>> > orthogonal
>> > feature only and keep the language still simple enough.
>> >
>> > Please add your comments on it. Hope it is useful and could inspire some
>> > new
>> > features in go 2.0
>> >
>> > Thanks!
>> >
>> > --
>> > 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.
>> > For more options, visit https://groups.google.com/d/optout.
>>
>> --
>> 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.
>> For more options, visit https://groups.google.com/d/optout.

-- 
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.
For more options, visit https://groups.google.com/d/optout.