Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
chrsig
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
9 ms
·
61.
▲
by
chrsig
2y ago
> I just don't reply to greetings coming from people I know aren't looking to talk to me to ask me how I've been. Yep, it's in there with "please use the public channel rather than DMs". Some nettiquite, ple
62.
▲
by
chrsig
2y ago
Sure, and the commenter's PO didn't specify how to get him a webpage. All very reasonable, see?
63.
▲
by
chrsig
2y ago
the "which ones are deployed where" bit is nice. if you're managing a lot of repos and deployments, yeah, that kind of thing can get really messy. i don't care how it's presented, via webpage or cli tool or whateve
64.
▲
by
chrsig
2y ago
> A new product owner came in last year and wanted to "automate everything". They wanted a web page where builds, branches, commits, and more were all on one page that showed exactly which commit was deployed where, by whom, et
65.
▲
by
chrsig
2y ago
I wouldn't consider my career being in process automation, but I feel like you just described my approach to managing new product development on top of existing machinery while ensuring no breakage of what exists.
66.
▲
by
chrsig
2y ago
Some people have taken the extra time and not gotten it in return, or otherwise been met with negative consequences for helping people. Bad experiences when trying to be benevolent really take a tole on some people.
67.
▲
by
chrsig
2y ago
Fair enough. Sigh. I can't help but wonder if the initial blowblack didn't cause some amount of oppositional defiance. or if the FSF just can't operate without him or the inverse. Kind of his life's work. Not excusing
68.
▲
by
chrsig
2y ago
I think the problem is looking at ND as an excuse rather than a reason to change intervention strategies. Like...yeah, he had a problematic position. He got corrected and someone explained to him the problem and he reversed his position[0]
69.
▲
by
chrsig
2y ago
In a lot of cases, the macos man pages leave a lot to be desired, or don't come up in a google search. I know I'm personally not in the habit of remembering apropros exists, so I can imagine that the first step to manpage discove
70.
▲
by
chrsig
2y ago
Servers have to limit header size as well, since content-length isn't available. Without a bounded header size the client can just send indefinitely. Also just impossible to read, and url encoding is full of parser alignment issues.
71.
▲
by
chrsig
2y ago
definitely laugh! life's too short, you'll never get out alive :)
72.
▲
by
chrsig
2y ago
Exactly. Gotta be happy you got a response at all!
73.
▲
by
chrsig
2y ago
ok, I found a commit in 2005, coming about because linuxthreads was interfering with the SIGUSR1 signal. It looks like they wound up making it platform specific, so BSDs and unix like operating systems might still use SIGUSR1. https:/
74.
▲
by
chrsig
2y ago
y'know...what really is an error, anyway?
75.
▲
by
chrsig
2y ago
No clue what the decision making process was. There's a bug report for httpd dating back to 2011[0]. The nginx mailling list also has a grumpy person contemporary with that[1]. My guess is someone thought "httpd is a server runnin
76.
▲
by
chrsig
2y ago
My favorite signal surprise was running nginx and/or httpd in the foreground and wondering why on earth it quit whenver i resized the window. Turns out, they use SIGWINCH (which is sent on WINdow CHange) for graceful shutdown. It'
77.
▲
by
chrsig
2y ago
i think it is still tracing, it's just a matter of identifying possible roots versus actual roots and constraints that fall out from that.
78.
▲
by
chrsig
2y ago
It took me a bit to hunt down, but it was part of the go 1.4 release in 2014. the release notes[0] at the time stated > The implementation of interface values has been modified. In earlier releases, the interface contained a word that wa
79.
▲
by
chrsig
2y ago
It was a bit of a bummer when go switched from the conservative gc to a precise gc. One of the implications was that they needed to change how interface types were represented. They had a nice little optimization for word-sized values to
80.
▲
by
chrsig
2y ago
It's definitely cool, and and accomplishment. I think it's a bit strange to compare it to "no cgo overhead" though I say that because it's an interpreter rather than a jit, and doesn't have nearly as many pers
81.
▲
by
chrsig
2y ago
"new" is subjective -- I'll catch up with the times eventually, I'm sure :) but yeah, I've had to write said script due to needing to compile in proprietary modules. It's just a bit of CI glue, pretty straight
82.
▲
by
chrsig
2y ago
You know, for most projects, I'd think that'd be pretty...bad. Given that nginx only recently got dynamic module support, I'm curious how many people are out there having grown to build it from source, letting them switch up
83.
▲
by
chrsig
2y ago
Learning any language more or less starts with learning a subset of it. Asking a new hire to "learn awk" vs "learn perl" have two very different time investments attached to them. Tasking someone with "learning a su
84.
▲
by
chrsig
2y ago
awk is also a much smaller language than perl, so it's generally less effort to teach, learn, and read.
85.
▲
by
chrsig
2y ago
...who let's a cat in their data center!? and where did the mouse go!?
86.
▲
by
chrsig
2y ago
Flesh?
87.
▲
by
chrsig
2y ago
I mean, I wish that didn't need to be said, but after the whole submarine-controlled-by-an-xbox-going-to-the-titantic thing, who am I to say what bucket of bolts people might jump into entirely on their own accord
88.
▲
by
chrsig
2y ago
> Rule 8: Controlling for a causal descendant (partially) controls for the ancestor perhaps this is a quaint or wildly off base question, but an honest one, please forgive any ignorance: Isn't this essentiallydefining the partial de
89.
▲
by
chrsig
2y ago
"reasonable" is doing a lot of heavy lifting in that post. I haven't examined the input/outputs -- just calling it out as an inherently subjective thing that warrants some further definition.
90.
▲
by
chrsig
2y ago
You know, after watching enough stargate, I'm fairly convinced we probably shouldn't do that.
More ›