nzeid

FWIW I get the most hilarious spam and strangest scanners from Netherlands.

This post so perfectly captures the tragedy of how the term AI has lost its meaning to LLMs.

Same here, but for _several_ electronics. Every advantage that Amazon has over other retailers is mooted by bootlegging. Being forced to authenticate or return products regularly is a major pain in the ass.

Held what? A majority of those companies evaporated. You'd have to cut your losses and reinvest.

I have so much to share on this topic. Will keep it short.

ROCm promises a 30-50% prompt processing speedup. This is REALLY important for my workflow so I've been trying to get this shit to work for months. But no release before v10 worked well enough with any engine for it to matter.

The llama.cpp release binaries for ROCm (10) FINALLY work on gfx1501 and its relatives (with the correct shell variables), but the prompt processing boost doesn't materialize and the token generation speed decreases.

There continues to be a chronic problem across all engines with the ROCm integration for UMA devices. The good news is that some improvements have been made to that end for Vulkan, so more recent llama.cpp Vulkan binaries are now faster.

> A good framework can maybe cache some of this with the opcode cache, and apcu. Saving some milliseconds.

This framing is confusing because OPcache has for the past 15 years taken care of exactly this bootstrapping you're worried about. In a competing share-nothing setup you merely come in at a tie for performance (barring first run of `require`). I do not see 10-50ms latencies in any of my deploys which is why I'm skeptical.

That said, the big sell of your project for me might be memory management - less memory means more workers which is always a good thing if it comes at no cost to latency.

Don't worry, I'm not coming down hard on said person. The thread is about a GrapheneOS bulletin, whose members are well-documented contributers to AOSP.

> php-fpm re-bootstraps the framework on every request (10–50ms)

What is the setup/benchmark that caused you to see this?

The phrasing of your first question is ironic given GrapheneOS has upstreamed a ton of their security hardening.

You're probably asking if they're able contribute anymore?

Reminds me of Notion and old Basecamp.

This is a very easy sell for me because everything these days is doing the infuriating gray text on gray background.

FWIW, from the OP website:

> Neobrutalism is a mix of regular brutalism in web design and more modern typography, illustration, and animation standards. Neobrutalism refuses the usual components of UX-UI design and embraces uncomfortable design elements, and it is more fearless to use distinctive color palettes.

Talk about sour grapes. Muse remains ridiculously popular and I will bet my bank account that there are more Muse fans than slop enthusiasts.

I see comments that this overlap between Qwen and GPT is due to rogue training or post hoc training. Did it occur to anyone that maybe the two sets of models were trained directly on the same solutions to the researchers' benchmark?

Definitely stinks of LLM phrasing, metering, and punctuation. But I'd say the ideas are the author's alone and they do cut through.

The edit is dead on and this is the very first thing that crossed my mind.

Bad managers hollow out companies. It's quite devastating.

The blog implies that CF's core business is suffering because of added investment in what the author describes as AI. See their useEffect bug as an example.

EDIT: To be clear, my employer still uses CF and I don't see any evidence that it's gotten worse.

This is definitely as opinionated as an opinion piece can go. Worth mentioning I don't use CF anywhere or care about it... but my employer does.

I can really only remember one catastrophic outage. It involved some part of CF that had no redundancy, and the incident was followed by a pretty whiny blog about a data center.

That's pretty much it. There were other minor outages but I'm not aware that it affected business.

Despite the disclaimer I think the author should explain precisely how "AI product mindset" or whatever is actually translating to bad outcomes.

Worth noting that there's no security in a system that abusively collects your data. That goes for children as well.

This post is inaccurate at its face but for those who are curious, Canada's GDP is in the low trillions of USD and its growth stagnated (but remained positive) the past several months.

By contrast, several US states like Vermont and Alaska have GDP in the double digit billions, while others like South Dakota and Nebraska shrunk.

This is a bit of a strawman. The parent comment wasn't suggesting that the inherent defects magically disappear nor was it suggesting that local inference today is sufficient for all tasks.

At the heart of it, self-hosting liberates your use cases from all the horribly opaque configuration, shadow prompting, etc. And local models are only getting better and more diverse every month.

I didn't read the Ramp article but this reads like a post hoc fallacy. Companies with 2x revenue have money to spend on AI. Companies with 1.15x revenue don't.

Forgive my ignorance... Usage limits reset for 100% of customers at the same instant?

Was there a disadvantage to using HAProxy + multiple PGBouncer instances?

Which is why test generation has to be carefully guided as well, and this is something at which I've incidentally been fast. Ultimately it's a constant battle between LLM handholding and doing things yourself.

Yep.

I do not have the burnout but I certainly operate similarly to the author. I continue to be unable to establish a workflow where allowing the LLM to generate code that I review is faster than writing the code myself. Literally the only two ways out of this dilemma is to blindly trust what was generated or to generate an uncharacteristically exhaustive suite of unit tests to validate every possible scenario. I just write the business logic myself and have the LLM do a lot of the rest. Boilerplate falls into the latter as well.

Taken out of context, you're right. But the parent comment couldn't buy these books even if they wanted to. I'd say there's a consensus that the primary motivation for piracy is hurdles to access having nothing to do with payment.

> Recent ideas suggest that little red dots could be black holes cocooned in thick gas, possibly representing a completely new type of object called a black hole star, in which the tight shroud of gas emits light like a stellar atmosphere.

Just be sure to name the members of Soundgarden on the paper.

> After this minor hiccup, the experience with MSI was actually quite pleasant. They prepared a patch for the vulnerability within two days of me reporting it and told me which MSI Center release it was to be bundled with, and when they planned to release the new version.

Was NOT expecting a happy ending.

I don't know if the part of MSI Center with the pipe vulnerability is automatically installed on desktops but this is the terribly written software that you need to turn off all the obnoxious lights on your MB and DRAM.

I'm old-man-yelling-at-the-clouds here. Everyone just uses Cloudflare, which is not a bad thing by itself. But do they _have_ to? Is managing your own edge really that terrifying?