I think a thin layer on notmuch would get you pretty close without so much infrastructure.
On the web scraping side, scrapling seems to pretty much just work. There hasn't been a website yet it won't load in some mode--even Google SERP.
2,500 karma · joined August 22, 2018
I think a thin layer on notmuch would get you pretty close without so much infrastructure.
On the web scraping side, scrapling seems to pretty much just work. There hasn't been a website yet it won't load in some mode--even Google SERP.
Maybe if latency can be improved _and_ it can run local inside the vehicle.
Imo a feature. I can handle the creativity and out-of-box thinking just fine. I want the model to do the grunt work but be smart enough to do the grunt work correctly.
Sent Opus 5.5 an example that used go context.WithTimeout and it tried to tell me that was wrong and I should pass timeouts as ints before finally admitting the docs it cited didn't say to use ints and that's a ridiculous design in go anyway (it was trying to claim that was codebase convention--passing ints...)
Anthropic commonly gates behind feature flags that require telemetry until they're "promoted" and defaulted on.
A little bit annoying you can't manually control the flags without telemetry but I think the title is a bit click bait.
Off to a _great_ start...
Also interesting this somewhat mirrors my recent experience with Opus 5--too much effort and it starts looking for things to do and invents requirements that never existed
Yeah, I just checked the page >can connect their server to the Internet with Argo Tunnel for free
Terraform has worked decently well especially since there's a few random settings here and there that aren't exposed anywhere in the UI (facepalm)
Loading https://gitlab.com/gitlab-org/gitlab is showing 14 API calls so presumably significantly more DB queries for a public page
https://gitlab.com/gitlab-org/gitlab
Makes 12 graphql API calls and 2 /api/v4 calls... So you get like 4 pages per hour unauth?
Sometimes I also want a smaller version for when I don't need that performance but don't want multiple implementations of storage backends
Edit: before someone says NVMe, highly available across 3 fault domains
Getting it to work reliably is quite the feat. AI coding is a much lower bar when there's (ideally) still a human expert that can set it straight when it goes awry.
I also think some of these debates get hung up on what's possible and ignore what's feasible and practical.
I forgot how awful using Opus 5 directly is.
Same thing as Cliff Notes imo. In every other area of manufacturering and tech I can use a machine to build a new machine that competes with the original machine. Should Milwaukee be able to prevent DeWalt from using their drill to make a competing drill? Should Jetbrains ban Eclipse contributors from using their IDE?
It randomly decided going from no explicit partition key which would randomly add to a Kafka partition to partioning key company was the right solution.
In fact, that was fairly counterproductive since this codebase dumps events to the topic per company so you'd get a lumpy distribution where only one partition is ever active at once (starving other consumers)
The fact it decided it should add this without prompting was a bit shocking and I'll probably try to make it explicitly clear in the context not to "do random shit that wasn't asked for"
Maybe that's not what the authors of the policy intended but that's how it reads imo
That said, these frontier models are still astronomically huge.
As AI bans go, this one doesn't seem too stringent if you disclose AI and actually check what it's doing.
I imagine if set some constraints you could get index size down quite a bit but I still suspect it'd be hard keeping up with content churn.
Edit: Looks like enwiki bz2 is coming in around 46Gi which isn't too bad considering the amount of content it contains.
I imagine it'd take quite a bit of shape for the index and be hard to keep it up to date unless you restrict what it indexes.