@IbehOmodolor · X

schildep · GitHub

verified-3d-mesh-intersection Formally verified 3D mesh intersection - trust 93 lines of spec, not 1000+ lines of AI-written code

@Mike1754791 · X

@nielsenburm · X

@aehyok · X

昨天使用免费的 做了一个网页版的DotA小游戏，还真的挺逼真的，一下子让我回到了过去开黑的日子。 我上个帖子评论区影魔的记忆还是深刻，本来想找个Pis 影魔的视频，看到好几个但都有点模糊了，就来分享一个玩dota的宝子们，都爱听到的声音吧。。。。 如果你也想做个小游戏真的太简单了，而且现在还是免费的。昨天一口气让AI自己跑了89分钟，估计消耗的token不少，欢迎体验我的DotA小游戏。 我的DotA小游戏链接，欢迎畅玩：

chenglong-hn · HN

Data visualizations are the bridge between user and data. But building AI agents that can generate visualizations reliably can be very tricky: - simple chart specs can be reliable, but generated charts are often of low quality due to reliance on system defaults; - complex chart specs with explicit details can produce good-looking charts, but they are verbose and agents can struggle with reliability We figured out it is a limitation on the language issue (not just AI capability thing) -- current visualization languages are a bit too low-level for AI agents, requiring them to explicitly make visual decisions that are supposed to be handled by a good compiler. Flint is a visualization intermediate language to address this issue, allow AI agents to solve this last-mile human-agent interaction problem. It provides a simple semantic-type based specification, and contains a layout optimization engine that can produce good-looking charts (filled with derived low-level details) from simple

@Laharmckenzie · X

@polycontext · X

Context-aware localization for apps, games, and software.

@caseyyoshi · X

@adarshbytes · X

@ChrizBogota · X

A great demo of why in Financial Markets you have to use Grok, it's not affected by "training cut-off date" like the other models. is 100% run on Grok, (but mostly built with Claude).

@Galliard232634 · X

Come study with me on