I rolled the same thing in Go months ago as I am sure at least another 1000 people have in their own way.

Would genuinely be interested to see it. link? The graph traversal approach seems underexplored compared to pure vector search.

Just like Mickey Rooney's span of being the top box office draw from 1939-1940. :)

https://www.youtube.com/watch?v=-UDQfFtiOk4

From all the articles I see about him I feel like he's constantly paying money to get in the news / social media.

You’re absolutely kidding yourself if you genuinely believe that.

Happy to chat internally if you want, feel free to reach out.

I see a lot of people swearing by one model, but without trying others. I see a lot of opinions based on a snapshot of tooling from ~January, when for example Claude Code was exceptional, but that don't appear to have been updated. In blind tests the models appear to be much closer than some folks would have you believe.

I’ll admit it swings back and forth on a six month cycle or so; however, cost-to-output matters.

Also, for niche use-cases there are clear winners.

Google models are well known for being quite terse and efficient on cost – reasonably low pricing for what they are and reasonably low token use for what they achieve.

But as I said do reach out if you are actually a googler, as my points are really about the internal tech which I am pretty positive about.

Why content like this doesn’t supersede the AI content, I will never know. Thanks for sharing :)

AI, as we have today, struggles to produce long, data-dense article.

"on HN" was what I mentally added to that comment.

I'd rather see articles like this know when the latest OpenAI release was and well it can draw a pelican.

Precisely; Go is by no means perfect, but if you want to throw away its security efforts, by all means use goblin.run

I’ll take vibe shooting myself in the foot over lying to myself any day.

I cannot fathom why anyone would want this.

It is mostly indicative of another underlying issue, like glibc versions or so. But this also leads to weird situations with reproducibility for QE/error reporting. One of the reasons I also hated some distro wanting to devendor and use distro dependencies. This all makes it harder to have a consistent support matrix.

SPY is an ETF and SPX is an index. The distinction is material.

/ES does not trade between 5pm and 6pm ET. SPX options aren't marked until 8:15 PM ET.

It's more plausible that large caps see MWF, then MTWHF possibly.

Thanks.

T+0 all-year-round trading is good in many ways bad in others —like losing the real investor liquidity spawning window at 09:30 EST as opposed to pure market making.

Quarterly earnings were already a bad fit for many businesses so I agree with the measure to do away with them in principle. Someone proposed real-time and I think that would be a net positive if not very feasible. Yearly is a good compromise.

Companies that are not profitable YoY usually have a story so they probably can avoid having to rob Peter to pay Paul.

Then again, maybe everyone adapts and yearlies turn into the next quarterlies.

Good additional info. I used a shortcut I figured most people would understand without getting into the weeds.

It would appear that person and OP are one in the same.

Damn. I missed that. But yeah OP didn't take it well when people poked hole into his proposed API.

But regardless of API ergonomics, I would love to have UUID v4 and v7 in the stdlib.

maybe the OP is trying but failing to drum up support for his unergonomic api proposal

Cool utility! I would be remiss if I didn’t mention synctest [1] which is quite excellent for not only async time testing but also catching subtle concurrency bugs.

[1] https://go.dev/blog/synctest

Did anyone else click in excitedly after misreading ‘Vllm’ as ‘LLVM?’