HackerTrans
TopNewTrendsCommentsPastAskShowJobs

jkachmar

no profile record

comments

jkachmar
·قبل 12 يومًا·discuss
it was not (solely) about slaves; this was debated in Congress during the process of drafting the amendment and resoundingly put down by contemporary legislators.

from Justice Jackson’s concurring opinion:

> Senator Edgar Cowan, for example, argued that German immigrants’ children born in Pennsylvania should be citizens, but Chinese immigrants’ children should not—because Germans and Chinese were different. In response, Senator Trumbull emphasized that the law he had drafted drew no such distinctions. Undeterred, Senator Cowan would warn again—this time during debates on the Fourteenth Amendment—that the Citizenship Clause would let Chinese immigrants “overrun” California and “double or treble the population” of that State. Senator John Conness of California, where anti-Chinese sentiment was arguably most pronounced, responded that “the children begotten of Chinese parents in California . . . shall be citizens.” In fact, he said, the Civil Rights Act had already declared “that the children of all parentage whatever . . . should be regarded and treated as citizens of the United States.” No Senator rose to agree with Senator Cowan or dispute what Senator Conness had said. And no Senator said what the principal dissent says today: that the text at issue conferred citizenship only on freed Blacks and those in analogous situations.

- - -

further down, Justice Jackson cites the most forthright example of how blisteringly ahistorical the Republican party’s arguments are on this topic:

> During the ratification debates, Senator Cowan took aim at the Roma people too, characterizing them as undeserving of birthright citizenship because they “wander[ed] in gangs,” “infest[ed] society,” and “impos[ed] upon the simple and weak everywhere.” And again, Senator Conness dismissed Senator Cowan’s prejudices: “The only invasion of Pennsylvania within my recollection was an invasion very much worse and more disastrous to the State, and more to be feared and more feared, than that of Gypsies. It was an invasion of rebels [at Gettysburg].”
jkachmar
·قبل شهرين·discuss
not speaking in any official capacity, but: we great internal training material courtesy of some very thoughtful folks, and ultimately one hopes that most of the code is going to be pretty straightforward wherever possible.
jkachmar
·قبل سنتين·discuss
reposting my comment from another time this discussion came up:

"Cosmopolitan has basically always felt like the interesting sort of technical loophole that makes for a fun blog post which is almost guaranteed to make it to the front page of HN (or similar) purely based in ingenuity & dedication to the bit.

as a piece of foundational technology, in the way that `libc` necessarily is, it seems primarily useful for fun toys and small personal projects.

with that context, it always feels a little strange to see it presented as a serious alternative to something like `glibc`, `musl`, or `msvcrt`; it’s a very cute hack, but if i were to find it in something i seriously depend on i think i’d be a little taken aback."
jkachmar
·قبل 6 سنوات·discuss
Lots of people like to believe this but it really, really isn’t true.

Los Angeles and New York City have a substantially larger cultural footprint than other cities.

Even though the variety of food, music, etc. is growing quickly elsewhere, it’s really not the same.
jkachmar
·قبل 6 سنوات·discuss
A WAI `Application` is defined as the following type alias:

  type Application =
    Request ->
    (Response -> IO ResponseReceived) ->
    IO ResponseReceived
...which is to say that WAI applications are “just” functions that accept an incoming request and a callback that turns that request into a response object (which may emit side effects), and which return a respond object (which may emit side effects).

This leads to a very nice definition for middleware as the following type alias:

  type Middleware =
    Application ->
    Application
...which says that any WAI middleware is just a function that turns one application into another.

This means that WAI applications have a nice and easy to understand top-level interface, and that complex chains of WAI middleware can be built up by chaining smaller middlewares together.

The potential benefit here (over other language frameworks) is that the “grammar” being used to describe applications and middleware is the same “grammar” that’s used in most other Haskell applications (i.e. function composition). Ideally, this should make it more easily understandable to a Haskell practitioner who might not be intimately familiar with the framework at first glance.
jkachmar
·قبل 6 سنوات·discuss
I like Haskell, I write Haskell at my day job (and did so at my previous day job), and I help maintain some of the community build infrastructure so I’m familiar with a large-ish graph of the Haskell ecosystem and how things fit together.[0]

I don’t really think Haskell is _meaningfully_ superior than other languages at the things that OP is talking about.

Refactoring Haskell _in the small_[1] is much nicer than many other languages, I don’t disagree on that point. Despite this, Haskell applications are _just as susceptible_ to the failures of software architecture that bind components of software together as other languages are.

In some cases I would even suggest that combining two Haskell applications can be _more_ fraught than in other languages, as the language community doesn’t have much in the way of agreed-upon design patterns that provide common idioms that can be used to enmesh them cleanly.

[0] I’m mostly belaboring these points to establish that I’m not talking out of my ass, and that I’ve at least got some practical experience to back up my points.

[1] This is to say when one refractors individual functions collections of interlocking abstraction