bvrmn

If you can't limit stuck chunks you can't limit fixed stack. And vice versa. It's quite simple.

Then fixed stack also is not possible for such cases.

Obviously chunk size is larger than class of objects to allocate.

Dynamic stacks with linked granular chunks? It consumes even less memory.

It's bad analogy. webauthn is quite far from just a protocol to verify keys.

> Ask any SOTA agent to identify a specific type of "janky crap"

It's always total hallucinations. It could only see local minor issues.

It happily starts to introduce fake abstractions and other junior level "refactoring" making it even worse.

Am I missing something but tag in git says nothing about actual deploy. It's at most a deploy attempt. What's wrong with CD which tracks actual deploys and records which commits are deployed and all related info like who and where?

The point is libraries are agnostic. You as a library user provide io transport and loop implementation which supports/not supports cancelation. And you as as library user handle cancelation.

> Libraries swallowing cancelled() or libraries lying that they support cancelled.

For me former is obviously worse.

The most frustrating part about it for me it's Andrew's argument: just write correct code. I have C at home.

I think the craze was about "purity" of mustache as presentation-only template engine. Apparently you need some level of logic to be useful.

Yey! Let's speedup project downfall to crap abyss even more!

You either care about project and do reviews. Or yolo vibe code. This middle ground has little sense.

Oh boy. There were (and are) hordes of enterprises requiring us to support SAML and were quite amazed to know Entra and all big auth providers perfectly support OIDC.

Ahah. In my days SOAP libraries were kinda shitty up to the point I had to write my own to handle "non-standard" (actually very standard) WSDL definitions. SOAP consumption in one lang was okeish, especially Java or .NET. But interop — oh boy. The biggest issue were services exposing SOAP interface based on code-first approach, when you write some declarative code with annotations and library transforms it into WSDL and proxy endpoints.

Oh gosh. I could only imagine how many apps in chain crafts and parses soap envelopes with adhoc code with mandatory info loss.

You could take any pills and have any fantasies in your small coding corner. But saying very strong word "better" has very distinctive aftertaste.

> could we throw the definition into context and tell the LLM to avoid it?

Every IMPORTANT RULE WHICH MUST BE FOLLOWED STRICTLY to not to do something from my AGENTS.md and skills are violated without any hesitation from LLM. Glorified autocomplete doesn't work this way. Positive rules are more stable on this regard.

Did your clanker reach 40k CLOC?

Without tailwind LLMs tend to use inline random colors, random sizes and radiuses. Project becomes an unmaintainable design soup really fast. Even with tailwind first priority is to define dark/light theme with semantic colors. After it's a smooth sail (sort of, routing, forms, state ownership and persistent url state are still an alien concept for clankers).

I'm quite versed in CSS but tailwind has convenient abstractions on top. It's like "why you need C if you have assembler". I don't remember when I wrote raw CSS last time. Even global styles I tend to express via @apply.

Hm it's interesting perspective. The paper adds sorting into the mix. Like sorting moves cells and thus prone to issues with references. For me sorting always moves values in cells and I even can't imagine how you could sort formulas. It doesn't make sense.

ArrayList is a very generic (pun not intended) structure and could be stretched quite freely in any direction with useful property of owning underlying slice. Like readonly preallocated ArrayList is a thing.

Examples don't show much more composability comparing to SQL. Even more Prela is heavily based on tuples and has same operation semantics as SQL.

Shameless plug: https://github.com/baverman/sqlbind-t

Since pipewire landed in arch all my issues with sound magically vanished. It's a really great piece of software. Maybe it's even worth to change the distro.

It's funny I'm currently creating a TUI. A mutt like mail client. I didn't have any second though to consider GUI for the project because it's so ridiculous.

It's inherently cross-platform (msys under windows). It allows to copy any part of UI. It doesn't require dependencies other than curses.

Shameless plug (link to the repo) of your extension :)

People nowdays have no shame and completely forget the art of plug.

It's by LLMs definition, duh. You are dummy charmed by "reasoning".

it's quite interesting scoring and conclusions. For me Gemini renders are definitely top outliers for all combinations.

Demo works quite strangely. For example "how to use typescript with createContext" show only typescript entries on top. Similarity search failed.

Nice one. gcc/clang are smart enough to get .ok condition statically. I'm very curios how complex an expression could be.