HN user

mdarens

44 karma
Posts0
Comments29
View on HN
No posts found.

check out the branch. if the changes are that risky, the web ui for your repository host is not suitable for reviewing them.

the rest of your issues sound architectural.

if changes are breaking contracts in calling code, that heavily implies that type declarations are not in use, or enumerable values which drive conditional behavior are mistyped as a primitive supertype.

if unit tests are not catching things, that implies the unit tests are asserting trivial things, being written after the implementation to just make cases that pass based on it, or are mocking modules they don't need to. outside of pathological cases the only thing you should be mocking is i/o, and even then that is the textbook use for dependency injection.

One of the most exciting features of Zig, but am I correct that this doesn’t apply to types themselves like comptime generics in Zig? I find that to be one of the most powerful ideas: type level mappings that have the same syntax as the runtime code where you can just set an iteration limit. This would be a great way to get around the “too large union” problem in TS, for example.

this is almost in "not even wrong" territory, but for the fact that autotrophs are definitionally the entry point for abiotic energy into edible calories for animals, and the observation that the largest terrestrial megafauna are herbivorous.

bamboo is not calorie dense to humans, because we've lost the ability to digest most of it, but pecans are absolutely more calorie dense than even fatty beef.

all else being equal, an ideal carbohydrate source is more calorically dense than an equivalent ideal lean protein source due to the balance in the thermic effect of food between the two. most mammals outside the obligate carnivores are really well optimized for getting calories from plants— this is why we have amylase in our saliva.

This isn't really meant to replace such things an environment where you have a rendering engine that supports CSS— I think demoing it on the page is more for showing off how portable it is with WASM. Off the top of my head, a few uses for this:

- Mapping components or structured document data with something like MDX or slate on to Clay components to render in different contexts outside the browser reasonably closely to what shows up in a browser preview, for example content for HUDs, in-world display panels or documents in games, or batch rendering printed documents

- Layout for UI where something like Electron or React Native would be overkill, or isn't supported

He's not insisting that people already familiar with functional programming concepts not use the terminology they have historically used, he's using concrete metaphors as a teaching strategy.

I was facing consistent multi-hour outages during the workday and looked into business internet options with my ISP (Cox) and from what I could gather they _did't even offer_ any plans with an SLA in my market.

Anecdotally, I remember multiple instances of coworkers walking out in the middle of a shift when I worked as a cook in a chain restaurant due to the combination of high stress (including abuse from customers and management) and low wages.

I also prefer hooks. They give you the flexibility of mixins with a better composition story. And reusing hooks in my experience is more like a lightweight OOP style, compared to the somewhat clunky FP ceremony of higher order components, as the API makes it feel like I'm passing around instances of little state objects. The refactoring flow is also dead simple. I prototype behavior inline at the top of a render function, then just cut all that out to a reusable hook which I can then choose to move to props or context above the now dumb component, and factor out into smaller hooks as I wish. Slicing the behavioral model of a component up to jam into the class lifecycle methods was painful to me in comparison. The static analysis tooling also finds and allows auto-fixing of scores of dumb mistakes that used to catch me at runtime when using classes or HOCs. My experience with hooks actually got me more interested in learning ReasonML & Elm!

clinton's slashing of the welfare state is a matter of degree, not the only instance of purported beneficiaries losing benefits. medicare part d doesn't allow the government to negotiate prices and thus functions more as a subsidy for the pharmaceutical industry than people for whom it is ostensibly intended to prescription access. lots of games can be played with budgets (such as block grants, one notorious example being the 1981 repeal of the mental health systems act) so the raw dollars of entitlement spending can grow without representing a true shift in resources. when cost of living (eg rents, healthcare) outpaces spending, all while units of public housing are destroyed without being replaced, and the terms of occupation have grown ever more stringent (for example, requiring maintenance come out of tenants' rent while lowering the maximum eligible income for tenants), the mere dollar amount of spending becomes a less definitive measure, i think.

the welfare state expanded dramatically after the new deal, but that reversed with the turn toward austerity in the late 70s. "the government" is an overly broad way of speaking about this, as it places budgeting for defense contracts & bailing out finance capital, or monetary policy geared toward preventing the labor market from getting tight (as opposed to full employment) under the same umbrella as tanf & snap.

can be circumvented by binding the header row & the styles to the same data, but gets complicated when you have cells in the header or body which span rows or columns, or have row-scoped headers.

this may seem like a coherent view of history if you view it as a series of decisions made by great men based solely on their personal beliefs, as opposed to protracted contests over resources & power by organized groups, like the radical abolitionists who waged a generational liberation struggle on every front to force concessions from the institutions of the day.

in 1861 more than 1/10th of what would later become the army of northern virginia owned slaves— 1 in 12 enlisted men and over half of the officers.

"only" 1 in 20 white southerners in the confederacy personally owned slaves on paper, but this is like making an org chart of the institution of slavery & only counting senior management.

if you look at the 1860 us census & expand the analysis to slave owning households of the confederacy, the rate was closer to 1 in 3.

seeing as how veganism is not the default choice in most of the industrialized world, this is a misleading frame. it's also incorrect that it's more efficient to "eat animals" to produce muscle if we're being pedantic (as a vegetarian, however, this is not a meaningless distinction to me)— amino acids in dairy & eggs have a measurably higher bioavailability than those in meat, whether ranked by the PDCAAS or DIAAS https://web.archive.org/web/20151010170125/http://www.idf-is....

This is an interesting (made up) definition of totalitarianism. When I buy fair trade beans from the local coffee shop so I can feel better about my yuppie lifestyle, is my resulting denial of business to Folgers totalitarian?

They don't fade away in Chrome because he's using a pseudo-element in the form of content: attr(title). Gecko supports transitions on generated content and WebKit does not.

Also, looking at the ::selection example, it should mentioned that it's not safe to group vendor prefixes in the selector portion of a declaration block, as, unlike with properties, the whole block will be skipped if an unrecognized selector is encountered by a UA's CSS parser.