agnivade

11 ms·

1. 61.▲
   by agnivade 8y ago

   That is correct. Now you can clone and build Go repos anywhere. Note that support is still experimental, so if you want stability, it is advised to remain inside GOPATH for another release. This is a good post - https://systemdum
2. 62.▲
   by agnivade 8y ago

   Yes, the release notes are a bit humble about it. Specifically, optimized assembly instructions are used now in crypto code and also lot of optimizations have gone into the ARM assembler. One example - https://gist.github.com&#x2
3. 63.▲
   by agnivade 8y ago

   There has been some tremendous improvements for ARM architecture. If you run some serious code on raspberry PIs, get ready to be amazed.
4. 64.▲
   by agnivade 8y ago

   I think your expectations from huge open source projects are a bit too much. There are over 3500 issues open currently as of this moment, and new issues get opened every 15-20 minutes. The Go core team is like 10 people. That being said - &
5. 65.▲
   by agnivade 8y ago

   Yep, this is it. Russ himself admits it. He was corresponding with Sam about his ideas and thought that would be sufficient. Whereas, he should have done that with the entire community and been more explicit about where he was going.
6. 66.▲
   by agnivade 8y ago

   oops, my bad. I assumed with those big checkins that this is the first time this is getting introduced.
7. 67.▲
   by agnivade 8y ago

   The newly introduced prove pass is probably the biggest game changer. And it provides a ground work for new optimizations to be done on top of it.
8. 68.▲
   by agnivade 8y ago

   Fair summary. I would like to add a couple of quick points that we are working on. * GOPATH is going to go away soon. Once vgo gets fully baked in to the language. Probably by 1.12 - https://github.com/golang/go/i
9. 69.▲
   by agnivade 8y ago

   How costly are these devices ? Are these readily available in the market to buy ?
10. 70.▲
    by agnivade 8y ago

    Dude, I can't even begin to start counting how many times I have had to rm -rf the node_modules/ folder and do an npm install afresh, just because some dependency has screwed up the other. yarn has given me peace that I did not th
11. 71.▲
    by agnivade 9y ago

    There are still some commits under review. I would wait until the tracking issue is closed.
12. 72.▲
    by agnivade 9y ago

    Great stuff !
13. 73.▲
    by agnivade 9y ago

    > but is it garbage-collected? Nope.
14. 74.▲
    by agnivade 9y ago

    > For example, why do unused variables and imports, a style issue, cause a compiler error? Here's why - https://golang.org/doc/faq#unused_variables_and_imports
15. 75.▲
    by agnivade 9y ago

    > My data is being collected? So? I have had this exact same response from so many of my friends. I find myself hard to explain in a manner that is non-technical. Is there a nice explanation that I can say when someone tells this to me n
16. 76.▲
    by agnivade 9y ago

    She does mention that with bundlers, users will still use the ES module syntax.
17. 77.▲
    by agnivade 9y ago

    Your #1 issue is mentioned clearly in the documentation. Mentioning here verbatim - > The http Client and Transport guarantee that Body is always non-nil, even on responses without a body or responses with a zero-length body. It is the c
18. 78.▲
    by agnivade 9y ago

    Thanks for this ! Question - Why did you choose C99 and not C11 as the standard ?
19. 79.▲
    by agnivade 9y ago

    Not all heroes wear capes.
20. 80.▲
    by agnivade 9y ago

    > MariaDB has a hard limit of using one index per table in a single query. Wait, seriously ? What is the rationale behind something like this ?
21. 81.▲
    by agnivade 9y ago

    > We also observed that the GC stalls on that cluster dropped from 2.5% to 0.3%, which was a 10X reduction! Umm .. shouldn't the stalls go to 0, because now you have moved to C++ ? Or is this the time it takes for the manual garbage
22. 82.▲
    by agnivade 9y ago

    Don't forget protocol buffers !
23. 83.▲
    by agnivade 9y ago

    Go programmers are called gophers. Nothing to do with the gopher protocol.
24. 84.▲
    by agnivade 9y ago

    Question to OP - Did your team check out NATS ( https://nats.io/ ) ? What are your thoughts on that ?
25. 85.▲
    by agnivade 9y ago

    Thanks. Good points. I won't be rolling out my own crypto of course. I like to use existing known parts. But add some slight improvements of my own. Customizations to my use-case. It's a layered defense approach against attackers.
26. 86.▲
    by agnivade 9y ago

    Sure. Check these out - https://articles.mercola.com/sites/articles/archive/2016/05/... http://www.primalbody-primalmind.com/protein-how-much-is-too...
27. 87.▲
    by agnivade 9y ago

    Not even a single mention of the risks of increasing mTor signalling due to extra protein. You would be well advised to keep that in mind.
28. 88.▲
    by agnivade 9y ago

    So your only argument is that if someone quits, the secrets will spill out ? I am a big fan of security by obscurity actually. I mean, by announcing to the whole world how you store your secrets, you are telling all the hackers in the world
29. 89.▲
    by agnivade 9y ago

    There are no benchmarks yet - https://www.reddit.com/r/golang/comments/7twccr/upcoming_rel...
30. 90.▲
    by agnivade 9y ago

    Looks like HN loves to shit on Gitlab. I will chime in with my experience. As a small startup, we have been using gitlab.com with a private CI server for over a year now. The UI performance has _most definitely_ improved. And their deployme