nfirvine

Hello! I'm nfi-hashicorp from https://github.com/actions/setup-go/issues/395 :)

My 2c given that that issue has sat in TODO for several years with no movement is that the maintainers probably aren't going to be pursuing too many big swings like that.

End of the day, implementing an efficient GOCACHE with github's cache primitives is untenable for the general case IMO. It works by shipping around big tarballs, and when your cache actually needs fine grained access to thousands of usually tiny files, only a few of which change, you're likely gonna spend more time on transfer and unpacking than you gain with cache hits.

The other thing is, as mentioned elsewhere, it's really hard to measure cache perf at a granular enough level, and aggregate that across jobs, so I'm willing to bet most people don't (outside of this very good post!) and are going off of vibes or napkin math and don't realize they're wasting time caching garbage.

Castle Adventure? https://archive.org/details/msdos_Castle_Adventure_1984

That's how I learned to spell the word "necklace"

I switched to Firefox for a week and wanted to kill myself. Basically, extensions still aren't forced to behave. As soon as you install a non-e10s extension, it disables e10s entirely, and then you're in the bad old days of single-process train wreck.

LastPass specifically seems like it has a bug where it locks the UI (beachball) while it populates login fields, and if you've got a lot of passwords (which we do), it'll take several seconds to unlock. Basically unusable.

I know these sound like LastPass problems, but the browser needs to sandbox these sketchy things better. I believe that getting from here to there is a really tough ecosystem problem, and while I appreciate Mozilla's philosophy on the open web, Chrome is simply better.

How is this different/better than Gmail's address+spammer@gmail.com?

I've been doing a little interviewing at my company, hiring engineers. I tend to avoid the pop quiz questions because I, having been asked them in interviews before, can't imagine they're that valuable, and, considering our field has plenty of introverts and autism spectrum-types, it's probably not representative of their abilities in a real work environment.

HOWEVER. One candidate had a PhD and was very agreeable, had lots of experience in other companies in our field. So I skipped the programming test, since I figured a PhD with loads of experience must be able to code...

A colleague of mine saw the candidate as they were leaving and ducked. I asked them why. "Well, I personally lead to them getting fired a few jobs ago." Turns out Colleague worked very closely with Candidate and Candidate can't code worth shit: Colleague ended up personally redoing a ton of Candidate's botched work, Boss noticed Colleague working way late for no good reason, and after several chances, had to let Candidate go since they couldn't do their job.

Anyway, I've come to the conclusion that I need to ask in-depth technical problems, but I'll phrase it like this: "I'd like you to describe an A* path-finding algorithm the best way you can (pseudocode, diagrams, assembly, whatever). I'm not looking for a 'correct' answer, or syntax or class diagrams. I want to watch how you solve problems of which you only have a vague knowledge. If you'd like to refer to some resource, feel free to ask, and I'll tell you if I know, or I'll find out."

I suspect this is the point of the technical question, but it's hard to tell what interviewers actually want.

"Novices to the language have a tendency to overuse channels." "The explicit instruction to [new] Go programmers is that they should avoid channels... [is] false." -- Isn't this a contradiction?

Ad. Written by marketing.

"Do not perform table alter commands. Table alter commands introduce locks and downtimes. Instead, use live migrations."

You know what avoids alter? Going schemaless.

The groups studied all live and are genetically from within 20 degrees latitude (S). USA is from 30--50 deg N, and genetically probably higher. I would be willing to bet that higher temperatures and longer days tend to make your sleep shorter.

"due to Third Party Doctrine, users forfeit their legal right to privacy by merely making it possible for sysadmins to access their information. This means the sysadmins can legally share users' information and passwords with additional third parties, and the NSA can legally spy on it all, without any need for a warrant or probable cause."

This sounds super fishy to me; feels like a misinterpretation made through tin-foil lenses. Citation please?

How is this not functionally equivalent to TLS client-side certificates? Yes, I understand that there's a UX problem, but CBCrypt has to solve that in addition to the crypto problem.

Also, C#? What is this, a Silverlight applet? :P