ecjhdnc2025

You may already know, but Slant 3D (print farm) do _some_ of this with Etsy and Shopify, and have an API for further integrations.

(I am working on a product myself, but it would likely have assembly needs beyond what Slant 3D do, and at any rate I am not in the USA)

Milk is not a loss leader: they aren’t losing money on it to get you to spend elsewhere.

It’s profitable for supermarkets.

(They definitely do manipulate milk prices to get consumers to shop with them rather than competitors, and sometimes they artificially lower the prices. But they don’t ever do this at their own expense. They do it by forcing farmers to supply below the true cost of production. Because dairy farmers can’t just sell some of their milk. Essentially as soon as a dairy farmer can’t get a buyer for the totality of their product they are out of business. It’s remarkably precarious. So most are pressured into selling below cost for long periods of time.)

Supermarkets might be using it to get customers deeper into the store but milk is also heavy, awkward, refrigerated, and shorter shelf life, which means they are always going to put it closest to the back of the store.

It does exist, it just doesn't get linked in the page. Click on the media item, your URL bar has changed.

> Another point that Patreon isn't really emphasizing here that seems relevant to any conversations about "fairness" is that Apple's fees on Patreon subscriptions in-app are now higher than Patreon's fees.

Unfortunately this is in the nature of suppliers and retailers.

Supermarkets make more profit on a litre of milk than farmers. Way way way more. Because they know farmers in practice have to sell _all_ their milk, not just some of it.

And what Apple really has, and knows it, is the only supermarket on the main road out of iBorough. And there are no corner shops.

It does have that feel, but it's decidedly cramped compared to, say, the VT100's font, or even that of the VT52, which are both a bit closer to the "server" heritage they are alluding to.

Many other "code page 437" (console graphics fonts) do much better than this for readability at base line-height.

Oh I am not saying it should be.

The problem is that to resolve the readability issues many people seem to be observing on that page you need to set it to 1.1 or 1.2 (try it!)

But that will break the console pseudographics.

Part of the problem with this font appears to be large, space-filling (yes, squareness is another way to put it) glyphs, when if they had a bit more of a difference between the cap height and the ascender height the full-height pseudo graphical glyph stuff would still work without the textual characters feeling so cramped.

At least, I think that is right. I know just about this stuff to be wrong in important ways.

Either way there must be a solution to this; it feels like a missed opportunity.

The line spacing is way too tight (this is line-spacing: 1).

Obviously that is beneficial for ASCII-art (smaller vertical gaps), but plain text would benefit from at least 1.1 and maybe 1.2.

I am not a typographer but the cap height of this font (I think it's the cap height) appears quite large, when perhaps it would be better to have a slightly smaller cap height so the ASCII-art features would work well at line-height 1.0 without the letters feeling so vertically cramped.

Basically, slightly less-tall letters.

But as I say, not an expert.

It used to be that all-lower-case brought to mind bell hooks, ee cummings, kd lang…

Now it’s a signifier for e/acc narcissism and grift.

> You are a senior full-stack developer, one of those rare 10x devs

I am not disputing that this improves answer quality, but it does make me despair that it does.

All the relations: this is a bit excessive.

But before CTEs this sort of thing had regular use with recursive tree structures, in caching hierarchies. You'd make use of whatever SQL options you had to concatenate a group of IDs into a comma-separated string.

e.g. all the parent nodes of a given node in the hierarchy, and even (selectively) for caching all the descendent node IDs of enclosures. Though there are better ways to do this for trees that could be truly arbitrarily deep.

I would argue for this, I guess, except that "forced me to write all my code with AI" is obvious misrepresentation. It doesn't sit well with me except as representative of the same over-egged hype that surrounded the Apple Vision Pro.

Hm. Says "hand" not arm.

I don't want to second guess whether there were other undisclosed injuries but the image does show someone who could possibly have carried on typing without the use of his right thumb? Like I did for this paragraph. (Albeit perhaps it would be more comfortable using a split keyboard for more comfortable right arm position? And probably after a few days of rest)

Or perhaps with left hand only, using sticky keys? Like I did with this paragraph.

OK so code is a bit more effort, and particularly Rust or PHP would not be as fun. Python is a bit more one-hand friendly. (Quiet at the back!)

But still. _Something_ was forced here, but it wasn't the use of AI. I'm thinking more the marketing.

That's great :-)

I don't think it is "clutching at straws" for a bar to want glasses that break less frequently, causing fewer safety concerns, and to be prepared to pay the extra, but whatever.