0x434D53

21 ms·

1.
by 0x434D53 10y ago
That happens, when a content marketer write about a technical topic... Just sad.
2.
by 0x434D53 11y ago
Which also teaches horrible security practices. Pleas also use gorilla/csrf and not your own brown "solution".
3.
by 0x434D53 11y ago
So what's the conclusion of this besides some useless numbers?
4.
by 0x434D53 11y ago
Wow, trying to doxx people is just the lowest.
5.
by 0x434D53 11y ago
You are not forced to handle errors. Or do you check for the errors returned by fmt.Print? I guess not. This was my point: In many areas go forces the developer to the right thing (no unnecessary imports, gofmt...) and does not rely on deve
6.
by 0x434D53 11y ago
Go is one of my working languages. Like with every other language (Python, OCAML, C#, some Java, Swift) i have a love-hate relationship with go. What i agree on: What i agree on with the presentation: Concurrency using goroutines and channe
7.
by 0x434D53 12y ago
For an array (which are value types in go) you have the obvious element-wise equality. For slices? Also element-wise? Even with different capacities? If the refer to the same window in the underlying array? Is there a need to copy the slice
8.
by 0x434D53 12y ago
A slice is not an array of bytes. That's exactly the point. See http://blog.golang.org/go-slices-usage-and-internals to get a basic understanding
9.
by 0x434D53 12y ago
I don't get that outcry and panic inside the Scala community. We should give the 2 forks a chance and see what it leads to. There is still the chance then to reunite the community behind "one" scala. Also they could have gr
10.
by 0x434D53 12y ago
It's the users fault! App.net was a alternative to twitter, but a paid one. Failed. So users are in no position that they are the product sold to advertisers. They actively decided to be the product.