Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
sethvargo
searching Neon…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
10 ms
·
1.
▲
Resourcely raises $8M seed round
(techcrunch.com)
3 points
by
sethvargo
4y ago
|
2 comments
2.
▲
Perforce acquires Puppet
(techcrunch.com)
2 points
by
sethvargo
4y ago
|
1 comments
3.
▲
by
sethvargo
5y ago
This is awesome - congratulations to the team on this raise. Very well-deserved :)
4.
▲
by
sethvargo
5y ago
The context was introduced by the commenter. The original post does not use contexts. In general, there's a pretty common set of patterns in which multiple goroutines are writing data to different channels, and you need to ensure the d
5.
▲
by
sethvargo
5y ago
Also, this isn't semantically correct. In order to ensure that `conditionaA` is _always_ preferred over `conditionB`, you must also check if `conditionA` has received a value inside of `conditionB`: select { case a := <-co
6.
▲
by
sethvargo
5y ago
Right, which is noted in the post. That verbosity is, well, verbose. I generally need this in 20% of things I write.
7.
▲
by
sethvargo
5y ago
It really doesn't though. It handles the case where the context might have expired or be cancelled, but there's still a race when entering the select between the ctx.Done() and reading from thingCh. You may end up processing one a
8.
▲
by
sethvargo
5y ago
How would you fix that code?
9.
▲
Freenode Power to the People on Blockchain?
(freenode.net)
8 points
by
sethvargo
5y ago
|
6 comments
10.
▲
Service Discovery for Google Cloud Run
(ahmet.im)
2 points
by
sethvargo
5y ago
|
0 comments
11.
▲
by
sethvargo
6y ago
Thanks, I'll take this feedback back to the team. Disclaimer: I work for Google Cloud.
12.
▲
by
sethvargo
6y ago
Yup - I can confirm that's the source. Disclaimer: I work for Google Cloud.
13.
▲
BigQuery Omni – multi-cloud data analytics
(cloud.google.com)
1 points
by
sethvargo
6y ago
|
0 comments
14.
▲
Auralite: A privacy-first social network
(auralite.io)
3 points
by
sethvargo
6y ago
|
0 comments
15.
▲
by
sethvargo
6y ago
The author of this paper alerted Google on June 11, 7:35 AM EST, less than 6 hours ago. While we recognize this is a rapidly-evolving space, a few hours is not in line with responsible disclosure[1] timelines. While we're still prepari
16.
▲
by
sethvargo
6y ago
There's quite a few resources. Liz and I did a video series https://www.youtube.com/watch?v=uTEL8Ff1Zvk and blog series: https://cloud.google.com/blog/products/gcp/sre-vs-devops-com... .
17.
▲
by
sethvargo
6y ago
> Can anybody speak to the expertise of the authors on security? I think a cursory LinkedIn or social media search for any of the title authors or chapter authors will demonstrate their credentials. There were many people involved in thi
18.
▲
by
sethvargo
6y ago
I don't think I can talk about that, sorry.
19.
▲
by
sethvargo
6y ago
I'll flag the HTML pages with the team. I'm honestly not sure. I know we're able to offer epub and mobi this time, something not previously possible with the other books. I haven't looked at those other resources, but I&
20.
▲
by
sethvargo
6y ago
Thanks for the feedback. This is a known issue that another user flagged this morning. The team is pursuing a fix. The content-type on the file is incorrect :/. In the meantime, you can open it in a browser and email it to yourself. No
21.
▲
by
sethvargo
6y ago
This is correct. This is the third book in our SRE series. It's reliability through the lens of security. Disclaimer: I work for Google
22.
▲
by
sethvargo
6y ago
Great question. As an O'Reilly author myself, I can tell you that we have no control over the animal selected. There's a fun animal selection process, but the publisher's decide. Disclaimer - I work for Google and worked on t
23.
▲
by
sethvargo
6y ago
Hey everyone - Seth from Google here. Thank you for all the positive comments about the book. I'll be around to answer any questions you might have. As noted, the book can be downloaded for free in digital formats. PDF: https:/&#
24.
▲
by
sethvargo
7y ago
This feedback is super valuable - thank you for sharing. I'll be sure to relay it to the product team.
25.
▲
by
sethvargo
7y ago
Thank you for the feedback. I'll relay this to the product team. I feel your frustration and, unfortunately, I do not have much to offer beyond my promise to relay this feedback and the items I've expressed in other responses.
26.
▲
by
sethvargo
7y ago
> Would your team consider tweaking the pricing as I mentioned, with the goal of helping early stage startups choose GCP? To be clear, it's not my team. I'm relaying feedback, but I can't make any guarantees or promises. A
27.
▲
by
sethvargo
7y ago
> They probably don't pay you enough. Can confirm :) > ...we do already pay for resources that are provisioned by our K8S clusters Customers are charged for worker nodes, but until this point, the control plane ("master"
28.
▲
by
sethvargo
7y ago
Can you help me understand how these changes would be _more_ than EKS?
29.
▲
by
sethvargo
7y ago
Correct, but the control plane nodes _were_ free and had no SLA. This changes that. [edit: spelling]
30.
▲
by
sethvargo
7y ago
As also a security person (:wave:), you can use dedicated node pools and workload identity to isolate workloads in the same cluster.
More ›