Because time is relative —— year for a 50 y/o is 1/50th of their life; a year for a 5 y/o is 1/5th of their life.

To be fair, Spotify was a slop factory long before LLMs started doing it

The bigger problem is that it doesn't help you learn the correct finger positions

the subscriptions all have limits. when you hit the limit you again start paying per token.

occam's razor explanation: more tokens = more $.

models are incentivized by their makers to burn through as many tokens as they possibly can, so long as the customer doesn't cancel.

This is actually nonsense. More tokens means more capacity subscription and expense. Anthropic has enjoyed a high premium per million tokens because the quality per token was unusually high. Now it’s unusually low. This drives down the margin people will be willing to pay for the same number of tokens while driving up their capacity utilization. The economics are even worse for subscriptions.

Opus models have degraded rapidly since March, with each release being considerably less useful and considerably more verbose. The language is no so weirdly florid it’s difficult to understand, and its logical conclusions are almost always suspect. It goes off on clearly bizarre snipe hunts to the point it feels like I’m using a gpt 3 model at times. It’ll announce that it’s about to embark on building something then just return control to the user and wait. You can also tell perceptibly when they’re reducing model quality to load shed - it becomes stupider and stupider to the point you’re better off dumping state and switching to codex or just turning in for the day and hoping they secured more capacity tomorrow.

It’s an absolute race to the bottom with Anthropic on virtually every level. I’ve rarely seen a company so rapidly accumulate good will in the developer community as they did around 4.6 in December and January. By March, it was inconceivable to use anything else. 4.8 was a bit of a wake up call to not put all your harness eggs in one basket. 5 is straight up time to cancel territory.

I actually manually set my model back to the older versions to get anything serious done. More and more I use codex for anything non trivial.

This isn’t about avarice by the provide trying to get more tokens and more utilization. They’ve over subscribed for capacity as it is. If they can produce better quality for less tokens they can charge a higher margin and will be paid if, which is a better economic strategy overall. This is something else. I suspect it’s actually the opposite, they’re finding ways to cut capacity demand in ways that leads to worse behavior that leads to more capacity demands, worse output, worse quality, and worse margins, worse, worse, worse.

Just as I never saw a company accumulate such positive developer good will so fast, I’ve never seen one squander it so fast too.

The irony of championing accessibility using low-contrast simulated VGA text...

Where do you see the low contrast?

The linked article has a fairly light gray background with white text. I can read it, but the low contrast is just tiresome.

According to the WCAG Contrast Checker website, the contrast satisfies all the WCAG visibility criteria.

https://contrastchecker.com/?c=ffffff&b=444444

I hate low contrast more than most.

Setting browser. display. use_document_colors or browser.display.document_color_use to 0 fixes things.

It does break some stuff, like voting buttons on hn. Im happy with the tradeoff.

Also the notion that the sides of the pages flash as you scroll due to simulating that old Macintosh monochrome monitor dithering effect. My eyes.

Isn't that because you (and me!) have screens with slow response times for pixel color change though?

Designing for less than ideal screens is a part of accessibility.

Agree. My vision is not even that bad and yet I literally had to squint and hold my phone very close to be able to read this page.

When I first was reading this I thought that the author was deliberately using a shitty font to make the point that obfuscated fonts are hard to read.

I’ve tried using this as a self hosted instance and it’s been a little rough around the edges with Hermes.

I'd say better to not call it Cloudflare in that case

The idea is actually supposed to be that Cloudflare OS is Cloudflare's internal instance, but when you deploy it for your own company, you call it "<your company> OS".

The product name and logo are configurable in the admin settings.

Yeah it's a little cheesy. Sorry.

Easily switching between models. Re: the local read/edit case, it's a bit more seamless than opening in a separate editor.

That's about it.