The right to demand a blood test or other mechanism of having the state own the burden of proof might be inconvenient but it's integral to a fairly operating system, just like the right to demand a lawyer or representation.

- REST (mentioned, but what kind of REST? Rails style REST? Just plain http resource endpoints? - GraphQL (mentioned) - gRPC - SOAP - JSON-RPC - Thrift - CGI (ok not really in the same category as the above) - Some weird adhoc thing someone created at 3am for "efficiency"

I'm actually fine with most languages deferring to their respective communities, maybe building on core libs like https://www.erlang.org/docs/17/apps/inets/http_client to handle the transport layer.

As an aside, funnily enough you can get JVM <-> BEAM interop via https://www.erlang.org/doc/apps/jinterface/jinterface_users_... I don't necessarily recommend it but it's possible

But in reality if you're using hotwire you can get away with almost no JavaScript at all comparatively. That's why stimulus is in vanilla js generally, it's meant for sprinkling behavior onto the dom vs controlling the dom.

So if you don't have a js framework that needs to control the whole Dom and doesn't need a gigantic optimization step or tree shaking or typescript or whatever, you can get away with a whole lot less than it you embraced those frameworks that _do_ want to own the dom wholesale.

How would you do this? You'd either

1. Create N pull requests then merge all of them together into a big PR that would get merged into mainline at once 2. Do the same thing but do a bit of octopus merging since git merge can take multiple branches as arguments. Since most source control strategies are locked down, this isn't usually something that I can tell my juniors to do

The point of breaking things down like this is to minimize reviewer context. With bigger PRs there's a human tendency to try and hold the whole thing in your head at once, even if parts of the pull request are independent from others.

  sig ->(_: MyData) { }
  def self.example(my_data)
    ...
  end

Personally having written ruby/rails/c#/etc and having been on a dev productivity team myself, I say: lean into the weird shit and make a dsl for this since that's what it wants to be anyways. People will always complain, especially with ruby/rails.

Not everyone has impeccable brushing habits and reducing cavities is a net benefit to public health like sanitation departments. I would be more interested to see a source as to why you think there's no benefit to fluorinated water when there are studies that are a quick search away for fluorinated water.

The quote is: - neat - plausible - wrong

"Just get rid of the cancer" is - neat because it sounds obvious and tidy - plausible because we can and do cut out cancer - wrong because it ignores the nuance that cutting into a patient's body can have massive impacts on long term health. It can also be wrong because certain cancers have no tumor sites.

As an aside, instead of an auto incrementing build number I'd suggest the git sha since it's: 1. Already there and points to a specific version of the code in the repo 2. Globally unique 3. Can assist with reproducible builds (i.e. 6afed54 was acting weird, let's build it locally and take a look) 4. Gives you an easy diff target to dump "release notes". Just diff to the previous and dump the merge commit messages.

Been a bit but I do believe that dotnet does this exact behavior. Sounds like gunicorn needs a pr to mimic, if they want to replicate this.

https://github.com/dotnet/runtime/issues/8485

I apologize, that was a knee jerk reaction because I've never seen the assertion that 2+2=4 is racist before, only that math can be used inaccurately (purposefully or by accident) in racial contexts. I was a bit taken aback by the assertion and should have engaged differently.

> Funny how you build up a straw man. I never claimed any of that.

This isn't a straw man, I'm not building up some contrived argument here; the original comment was that "2+2=4 is racist" is a rallying cry for [some not insignificant number of math teachers].

> For example the Wall Street Journal. And hundreds of similar articles.

I did find this Opinion while googling, and read the parent Op-Ed (https://www.wsj.com/articles/california-leftists-try-to-canc...) and then followed through to the framework but I just don't see anything about the manual they were talking about in that Op-Ed in the works cited (seems like all references to the manual have since been removed). So I dug up the wayback machine on the page to see the context in which they were using the "A Pathway to Equitable Math Instruction" manual.

> A Pathway to Equitable Math Instruction (https://equitablemath.org/) is an integrated approach to mathematics that centers Black, Latinx, and linguistically diverse students in grades 6–8, addresses barriers to mathematics equity, and aligns instruction to grade-level priority standards. The Pathway offers guidance and resources for immediate use in planning their curriculum, while also offering opportunities for ongoing self-reflection as they seek to develop an anti-racist mathematics practice. The toolkit “strides” (above) serve as multiple on-ramps for educators as they navigate the individual and collective journey from equity to anti-racism. It is a collection of resources to help grades 6–8 Black, LatinX, and linguistically diverse students thrive in mathematics education.

Ok so generally seems like they're recommending the usage in primarily POC or mixed classrooms where the considerations for teaching might be a bit different due to a multitude of factors.

Now digging into the manual a bit, the titles are definitely inflammatory but the content is honestly fairly humdrum (quotes taken from the first chapter https://equitablemath.org/wp-content/uploads/sites/2/2020/11...)

• Teach rich, thoughtful, complex mathematics. • Teach rigorous mathematics, understanding that rigor is characterized as thorough, exhaustive, and interdisciplinary. • Use mistakes as opportunities for learning. • Recognize mistakes as miscommunicated knowledge. • Allow for engagement in productive struggle • Teach students of color about the career and financial opportunities in math and STEM fields. • Encourage them to disrupt the disproportionate push-out of people of color in those fields. • Invite leaders and innovators of color working in STEAM fields to meet your students. • Rely on teamwork and collaboration as much as possible. • Teach mathematics through project-based learning and other engaging approaches. • Provide multiple opportunities for students to learn from and teach each other. • Intentionally include mathematicians of color. • Expose students to mathematicians of color, particularly women of color and queer mathematicians of color, both through historical examples and by inviting community guest speakers. • Teach students of color about their mathematical legacy and ancestral connection and mastery of math. • Honor and acknowledge the mathematical knowledge of students of color, even if it shows up unconventionally. • Give rightful credit to the discovery of math concepts by mathematicians of color. Reclaim concepts attributed to white mathematicians that should be attributed to mathematicians of color.

Which all seems fairly reasonable here to my eyes. I will 100% agree with any assertions that the titles are very standoffish and even straight up accusatory but the content of the manual really seems like something good teachers should strive for. So to conclude I don't think that 2+2=4 is racist is really a rallying cry, the literature cited everywhere seems to talk mainly towards the teaching methodologies employed.

Source? This is such a wild claim it has to be made up. A cursory google search brings this article: https://www.edweek.org/teaching-learning/teaching-math-throu...

Which is distilled down to "teachers teach math in a way that is topical to the current environment, such as BLM protests which is really nothing new. You might disagree with it, sure, but to say that this is "the wokes" teaching 2+2=fish, that's frankly ridiculous.

In fact, the only thing I can find reporting on "2+2=racist" is this Washington Examiner article deriding a math teacher from NYC for her tweets (article here: https://www.washingtonexaminer.com/news/math-professor-claim...) which sounds _awful_ but it's a single person tweeting, and it seems to be in relation to using "math is pure and objective so it always must be neutral" as a defense for situations where data/statistics/algorithms presented show a clear bias. Which I think generally is an agreed upon phenomenon-- depending on the sampling and interpretation of the data, folks can come to _wildly_ different conclusions, especially if data was accidentally omitted.

Best example of this phenomenon is facial recognition software, which can perform very badly when deviating from the sample data. https://www.nist.gov/news-events/news/2019/12/nist-study-eva...

> For one-to-one matching, the team saw higher rates of false positives for Asian and African American faces relative to images of Caucasians. The differentials often ranged from a factor of 10 to 100 times, depending on the individual algorithm. False positives might present a security concern to the system owner, as they may allow access to impostors.

...

> However, a notable exception was for some algorithms developed in Asian countries. There was no such dramatic difference in false positives in one-to-one matching between Asian and Caucasian faces for algorithms developed in Asia. While Grother reiterated that the NIST study does not explore the relationship between cause and effect, one possible connection, and area for research, is the relationship between an algorithm’s performance and the data used to train it. “These results are an encouraging sign that more diverse training data may produce more equitable outcomes, should it be possible for developers to use such data,” he said.

All the other sources I found on google were either think tanks, facebook posts, or spam sites.

ETA: even in the most pessimistic reading of those tweets, I'm personally hard pressed to find that one person tweeting means that all math teachers everywhere are trying to take math down to "2+2=racist"

My otherhot take is to not use helm but rather something like jsonnet or even cue to generate your yaml. My preference is jsonnet because you can very easily make a nice OO interface for the yaml schemas with it. Helm's approach to templating makes for a bit of a mess to try and read, and the values.yml files _really_ leak the details.