enricoros
Frankly surprising and welcome to see loosening CCP-sensitive topics between model versions.
Show HN: Big-AGI 2 – Spent a year obsessing over AI for thinking
https://github.com/enricoros/big-AGI/releases/tag/v2.0.0
Hey HN, Enrico here. Some of you might remember Big-AGI from early chat days. The response here pushed me to quit my job and go all-in. Spent the last year rebuilding it properly (mostly hand-written) instead of shipping fast.This is the tool I couldn't find: the AI you use to decide what to build, and why, before going to Claude Code or Cursor.Even though the hype is on AI that 'does' things...
Show HN: Beam – Find Better Answers with Multi-Model AI Reasoning
https://big-agi.com/blog/beam-multi-model-ai-reasoning
HN, first things first: one year ago you make me believe in my opensource AI project, and I'm forever grateful[1].I am back with Beam - a technique to use diverse LLMs to generate responses, and Merge them - all within a snappy UX. I am no researcher, so you'll find a dark-mode blog, and not a light-mode PDF on arxiv :) Blog, open code, and live hosted demo, all published.You can use Beam early...
Crisp or too critical?
1. Documentation: lacking, inadequate, outdated
2. Code quality: simple, awkward, suboptimal
3. Production readiness: experimental, unreliable, limited
4. Monetization: unclear, risky, potentially detrimental to open-source
5. Community support: misinformation, poor communication, fragmented
6. Ecosystem: competing alternatives, redundancy, unclear positioning
7. Business model: potential rug-pull, VC-funded, uncertain sustainability
8. Developer experience: poor ergonomics, type erasure, confusing
9. Performance: slow, afterthought, poor observability
10. Maintenance: unpatched bugs, slow response to issues, dependency on contributors