> 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.
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.
Is this really true? Maybe it just makes sense to put high demand refrigerated products in the refrigerated room near the loading dock where the refrigerated trailer is unloaded?
Yeah, I hear people repeat that a lot, but it doesn't entirely align with my experience. A lot of the grocery stores I shop at (mostly Kroger and other national chains,) have a cooler right up front with the most popular dairy/refrigerated items for the people that are just there to pick those up.
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.
line spacing beyond minimal ought not be an attribute of a font. I can see a "recommended" line spacing for some type of "vertical as well as horizontal beauty", but drives me nuts when choosing a font also chooses scads of whitespace.
I like to squeeze a lot of info on a page, why do other people get to say "no". Sure, space out your wedding invitation, I can deal, but on the daily text on my screen, that should be up to me.
I do prefer "typewriter" fonts that are more squoze horizontally, this one seems to have loosened the ol belt a little, maybe for more "squareness".
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.
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.
It's called crytyping, and it's a common tactic used by flatterers and sycophants on the internet to evoke the humble defenselessness of a Tumblr post when advocating for something ridiculous. Sam Altman has been wearing the style like it's casual Friday year-round, and now everyone else thinks it's the only way to distinguish themselves from AI.
And honestly, this guy needs it. What the fuck kind of tone can you even use to make something this stupid sound realistic:
this model is such an enormous leap in capabilities it's becoming impossible to make the model safe. if you had this particular model unlocked, you could easily disrupt the world on an unprecedented scale.
Like c'mon dude, shut up. We've been laughing at OpenAI's stupid ass since "sparks of AGI" hit Arxiv, this stuff is so unnecessary and repeats the character assassination that constantly undermines their releases. Show me proof, have this new Strawberry model rewrite your tweet in a compelling or believable manner, or I'm not even going to give you the time of day.
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.
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.
You're missing something but it's actually easy to get confused about.
GPIO: general purpose input/output. A pin that can be used by the main CPU core(s) to interrogate the outside world.
PIO: programmable input-output. A small, I/O dedicated state-machine that can be custom-programmed in a minimal assembly language to handle I/O tasks/simple protocols/state management, over GPIO/I2C/SPI etc., without taxing the primary CPU.
Some microcontrollers have basic features a little similar, but it's something the RP series is taking a lot more seriously than most. The RP2040 has eight of these PIO state machines; the RP2350 has 12.
There are some astonishing examples of what these things can do. But basically think of these as delegated GPIO/SPI/I2C etc. co-processors that can blaze away at high speeds on I/O tasks without needing the main cores until something "high-level" occurs.
Makes sense. I’ve worked a lot with multipurpose gpio that can also be configured as spi or i2c but this is another step beyond that. Thanks to everyone for this!
Broken glasses in bars, for example, have a lot more impacts than just waste.
Broken glass has to be cleaned up, causes injuries, even causes lost product in some situations.
I was in a cocktail bar once with three friends who ordered us the same chilled cocktail, served there day in, day out, and as the cocktails were poured into the glasses, three of the four glasses broke. Plink, plink, plink.
Glasses too hot, cocktail too cold, some other handling problem. Who knows. But tougher glass might not have done that.
A friend used to work in a student bar as a bartender. Broken glass was legitimately a safety issue. Drunken people can cut themselves quite creatively, including severed sinews.
Ironically, most of his patrons were medical students.
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.
(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)