mwkaufma

Warming up to LLMS... explicitly _after_ full branch-coverage and fuzzing.

Didn't expect their branding to lift from Tim Heidecker's Dootle Dots, but here we are.

(has played sim city thousands of times since 1993) "I got this."

No I don't. I believe landlords grab any excuse to price gouge. You're tilting at a strawman.

Edit 1: We agree rent is a problem, we disagree that your LVT "one weird trick" is effective, and I'm hostile to the trojan-horse-end-of-income-tax which gets this stuff on HN in the first place.

Edit 2: you'll win more hearts without the patronizing/smug rhetoric.

Freely choose to pass.

Evidence is presented suggesting landlords don't lower rent when costs go down, and a hand-wavy claim is made by-symmetry that they won't raise rents when costs go up. It's nonsense, there's nothing to rebut.

Buried in the middle, a whole section on "won't landlords just pass costs into tenants" passed over with the weakest deflections. This is willful naivety.

Magical thinking intensifies.

Bootlicking apologia for a bad boss.

Dems' are a center-right party.

Pretty milquetoast analysis which I'm sure ruffles the feathers of all the landlords in the peanut gallery on this site, but what's really objectionable is the periodic terrible AI-generated images.

Ctrl-F "marx" -- 0 results.

"Advisory Group"

   Importantly, the group will not be responsible for advising us on how to pace our internal progress on mathematics.

"The attack surface wasn't big _enough_"

If it's one of those two it's not fully undefined behavior it's just implementation defined. UB can do anything.

The good uses cases for trivial infinite loops is a vanishingly small subset of infinite loops.

When your "app store" is just a chatbot role-playing being an app store.

Speculating about future technological risks is at least more fun than acknowledging immediate systemic financial risks.

If you add "fits in a register" to your list of correctness requirements, then it's no-go even if the source has less cognitive overhead.

Three days late homie

So, next-token predictors

Question isn't how can a function closure be represented anywhere, but how it can be represented in a way that can be aliased by a vanilla C function-pointer, which is a more specific and challenging question.

The lady doth protest about the lady doth protesting too much, too much.

Complexity measures the worst-case, not the amortized case. If you want to report proportional cycles for more fine-grained per-feedback, fine, report proportional-cycles, but that's not Big-O, so don't use that notation.

need to represent the "captured-variables"/closure

You've introduced an idiosyncratic definition of "worst-case" that nobody else uses to redefine proportional cycle-counting as "complexity", so yeah, I guess in your novel terminology that makes sense, but it isn't consistent with any CS textbook.

Every O(n) is O(1) if n = 1. Complexity measures worst-case by-definition, not all cases.

Isn't O(n - k) or O(len(l1) + len(l2)) just O(n)? Instead of blurring the line between complexity-analysis and cycle-counting, just print both the complexity and the est proportional cycle-count as separate measures.

Awkward prose of GenAI.

I know it's not just for the branded inverted asterisk, but is it just for the branded inverted asterisk?