Historically, the list of architectures that public github action runners make available has been quite limited. Having an alpine runner to surface unsupported commands would be a huge win.
That being said, it's very useful as a plugin dev to have this test suite while working on a WSL2/Ubuntu so that I don't need to run a full CI build every time
yep! PAM is "Pluggable Authentication Module" which sits between applications and the auth method, so you can put anything there. LDAP and ActiveDirectory are fairly common ones
Yey! 2.4 finalized another crucial feature that didn't make it into the changelog or release notes - the --insecure-no-tls flag for operating behind a proxy with SSL termination (such as with a load balancer in AWS)
Arm-chair opinion, but there are - just that chimpanzees/humans are a particularly bad example 'cause it happened so long ago. Once you have a common ancestor species split off into different species those species, by definition, can't share mutations between each other. Separately, chimpanzees and humans are "different", not necessarily better than each other. I don't know enough about the evolutionary history to say why but superficially they're better at tree-living and we're better at Savannah-hunting. Two different environments, so sharing mutations probably wouldn't help much.
"But with code that recurses or calls
other methods that are implemented in Ruby (better said: Carbon input
language). From obvious reasons the mentioned improvment factor will
go down to zero when spending all the time in builtins; (long running
builtins, not Fixnum#+; but this effect begins with it). One may say
snippets that do no work are producing larger speed improvments; but
this is also the kind of code one calls object oriented; i.e. many
levels of indirection, abstraction ....."
Two issues with this paragraph:
1) "Carbon input language" makes me think that I can't use the full breadth of Ruby. If I can't use the full breadth of Ruby it's not a Ruby VM.
2) I'm not really grokking the "snippets that do no work" portion, but given that Ruby (or at least the Rails/Sinatra flavors) are all about interdependent, highly-OO flavored code what audience is this VM targeting?
An additional point is - what if I have another CI gem that conflicts with capistrano-harrow but not capistrano?
What if capistrano-harrow introduces a security vulnerability that I'm not prepared for because I don't pay attention to a gem I'm not using?
I get that the maintainers want to promote their paid services, but this feels awful on multiple fronts. If capistrano is too expensive to maintain on your own, address that problem don't drag the Rails community kicking and screaming.
This is usually a fair point to make, but you're pointing at neither the flaws in the underlying case study nor the weakness in generalizing Utah to a wider area. That's not really fair, especially since parent comment is providing data.
How would that be different from the way CSS currently functions, where if B is parsed later than A and references the same selector, B's behavior overwrites?
Most implementations I've read lean towards it being similar to a negative tax (there are other possible implementations out there). So if you file $0 income, you get a $10,000 credit/refund. If you make $200,000 income, you pay $20,000 in taxes.
So taxes on the top brackets pay for basic income on the lowest brackets, with the understanding that the impact isn't changing much for most people because we already have a progressive tax system and this is just a simpler/more efficient way to distribute.
The second half (or third third?) of that quote states:
> And just as critically, do you step back and stop leading, do you let someone else? Because what’s critical to be an effective leader in this environment is you have to be willing to relinquish power.
Which I think is what the author is trying to focus on. Traditional leadership would be making the decisions and taking risks because it's expected and people are asking you "Hey, what do we do?". Emergent leadership would then be making decisions and taking risks because it needs to happen or equally importantly acknowledging that someone else is more capable of doing so. I would bet that in the interview process they'd focus on the story and trying to determine how you make the decision to either ignore the chain of command or otherwise exert influence on it.
Like you said, that definitely selects more for storytelling skills than leadership skills, but in absence of other more accurate metrics I think that's still better than looking for "President of Chess Club" on a resume.
Unrelated, I'd love to read those narratives. While I can't speak for the community, I feel interviewing is a very hard thing to get right and knowing more about how other people do it AND experience it is important to getting better. Nothing < anecdotes < more anecdotes < data?
Historically, the list of architectures that public github action runners make available has been quite limited. Having an alpine runner to surface unsupported commands would be a huge win.
That being said, it's very useful as a plugin dev to have this test suite while working on a WSL2/Ubuntu so that I don't need to run a full CI build every time