frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

AI has made it 'close to impossible' to assess university coursework

https://www.theguardian.com/education/2026/nov/11/ai-close-to-impossible-assess-university-course...
1•chrisjj•1m ago•0 comments

I made an AI harness / orchestrator that *actually* gives you decent limits

https://scoutcode.dev
2•gentra•3m ago•1 comments

Myflames – Database Diagnostics and Management for MySQL, MariaDB, Readyset

https://myflames.io/
1•vgrippa•7m ago•0 comments

Should we fear Q-Day how to think calmly about invisible risks

https://qday.forum/quantum/should-we-fear-q-day-how-to-think-calmly-about-invisible-risks/
1•quantaful•7m ago•0 comments

Tools for exploring the souls of large language models

https://oshea00.github.io/posts/tinygpt-visualizer/
1•r00tanon•8m ago•1 comments

AUX-2 – No device left behind

https://www.home-assistant.io/connect/aux-2/
1•XiS•10m ago•0 comments

Huawei details how Kirin 9050 runs a 30B-parameter model on device

https://technode.com/2026/11/11/huawei-details-how-kirin-9050-runs-a-30-billion-parameter-model-o...
2•yogthos•10m ago•0 comments

ISP router UI sucks – make your own

https://www.rossng.eu/posts/2026-11-01-fyxel/
1•speckx•10m ago•0 comments

Own Everything and Be Happy, Ep. 1 – DIY Router Guide

https://gamersnexus.net/features/own-everything-be-happy-ep-1-diy-router-guide
1•DeepLogin•11m ago•0 comments

Ring Drone Cam

https://ring.com/products/drone-cam
1•micahswitzer•12m ago•1 comments

Type 0.73: Earth on the Kardashev scale, and why AI is short of wire

https://oliverdb.ai/blog/type-0-73.html
1•pnr-consulting•14m ago•0 comments

Scottish and NI Schools evacuated under cyber threat

https://www.walesonline.co.uk/news/uk-news/uk-schools-evacuated-after-hundreds-34895300
2•nephihaha•14m ago•0 comments

Show HN: Friday, Claude Code, Codex and Cursor as one team (open source)

https://github.com/splashxmoon/friday
1•arunjdass•16m ago•0 comments

Show HN: Play SNES games while Claude is working

https://github.com/LaurentiuGabriel/retro-break
1•bitheap_tech•17m ago•0 comments

Visualising Sorting Algorithms: Python's timsort (2009)

https://corte.si/posts/code/timsort/
1•cortesi•17m ago•0 comments

The Rise of the Overprepared Concertgoer

https://www.pastemagazine.com/music/concert-culture/the-rise-of-the-overprepared-concertgoer
1•bookofjoe•19m ago•0 comments

New York Launches Nation's First State AI Testing Program

https://www.politico.com/news/2026/11/10/new-york-hochul-first-state-ai-testing-program-01157713
1•pseudolus•20m ago•0 comments

Lovable for Python

https://flet.dev/studio/
1•appveyor•21m ago•0 comments

Show HN: Disband – a stem separator with an API, down to the drum kit

https://disband.io/
1•f1nniboy•24m ago•0 comments

Trump admin loses fight to spy on random journalists' LinkedIn DMs

https://arstechnica.com/tech-policy/2026/11/trump-admin-loses-fight-to-spy-on-random-journalists-...
9•pseudolus•25m ago•0 comments

Ask HN: Any money in verification of company calling?

1•a_lifters_life•25m ago•0 comments

I built an AI agent and the cloud it runs on. Alone

https://ianberdin.com/
1•ianberdin•26m ago•0 comments

Just Don't Say "Just"

https://nickbusey.com/article/2026-11-11-just-dont-say-just/
2•NickBusey•26m ago•0 comments

Emacs in the Age of Magic

https://commandlinesystems.com/magic.txt
8•ggcr•27m ago•1 comments

Wysiwyg Editors Are Too Expensive, So I Built My Own

https://ilikekillnerds.com/2026/10/31/wysiwyg-editors-are-too-expensive-so-i-built-my-own/
1•speckx•28m ago•1 comments

Why putting a giant mirror in space could be a bad idea

https://www.skyatnightmagazine.com/news/reflect-orbital-giant-mirror-in-space
1•latexr•29m ago•1 comments

Axiomitisation of Scienctific Notations for Programming Languages

https://sm2n.ca/articles/typeclasses-vs-modules/
1•efren6•29m ago•0 comments

Huawei releases MACaQ, its internal quantizer for local inference

https://github.com/huawei-csl/MACaQ
6•thefox96•29m ago•0 comments

I Am Dr. Jekyll and Mr. Hyde about AI

https://chollinger.com/blog/2026/11/i-am-dr-jekyll-and-mr-hyde-about-ai/
1•otter-in-a-suit•31m ago•0 comments

Show HN: A screen recording CLI for your coding agent (Mac)

https://github.com/notoriousbfg/reel-cli
1•trwhite•31m ago•0 comments
Open in hackernews

LLMs Are Great, but They're Not Everything

4•procha•1y ago
Three years after ChatGPT’s release, LLMs are in everything—demos, strategies, and visions of AGI. But from my observer’s perspective, the assumptions we’re making about what LLMs can do seem to be drifting from architectural reality.

LLMs are amazing at unstructured information—synthesizing, summarizing, reasoning loosely across large corpora. But they are not built for deterministic workflows or structured multi-step logic. And many of today’s most hyped AI use cases are sold exactly like that.

Architecture Matters

We often conflate different AI paradigms:

    LLMs (Transformers): Predict token sequences based on context. Great with language, poor with state, goal-tracking, or structured tool execution.

    Symbolic AI / State Machines: Rigid logic, excellent for workflows—bad at fuzziness or ambiguity.

    Reinforcement Learning (RL): Optimizes behavior over time via feedback, good for planning and adaptation, harder to scale and train.
Each of these has a domain. The confusion arises when we treat one as universally applicable. Right now, we’re pushing LLMs into business-critical automation roles where deterministic control matters—and they often struggle.

Agentic Frameworks: A Workaround, Not a Solution

Agentic frameworks have become popular: LLMs coordinating with other LLMs in roles like planner, executor, supervisor. But in many cases, this is just masking a core limitation: tool calling and orchestration are brittle. When a single agent struggles to choose correctly from 5 tools, giving 10 tools to 2 agents doesn’t solve the problem it just moves the bottleneck.

Supervising a growing number of agents becomes exponentially harder, especially without persistent memory or shared state. At some point, these setups feel less like robust systems and more like committee members hallucinating their way through vague job descriptions.

The Demo Trap

A lot of what gets shown in product demos—“AI agents booking travel, updating CRMs, diagnosing errors”—doesn’t hold up in production. Tools get misused, calls fail, edge cases break flows. The issue isn’t that LLMs are bad it’s that language prediction is not a process engine.

If even humans struggle to execute complex logic reliably, expecting LLMs to replace structured automation is not vision it’s optimism bias.

On the Silence of Those Who Know Better

What’s most puzzling is the silence of those who could say this clearly: the lab founders, the highly respected researchers, the already-rich executives. These are people who know that LLMs aren’t general agents. They have nothing to lose by telling the truth and everything to gain by being remembered as honest stewards.

Instead, they mostly play along. The AGI narrative rolls forward. Caution is reframed as doubt. Realistic planning becomes an obstacle to growth.

I get it, markets, momentum, investor expectations. But still: it’s hard not to feel that something more ethical and lasting is being passed over in favor of short-term shine.

A Final Thought

I might be wrong—but it’s hard to ignore the widening gap between what LLMs are and what C-level execs and investors want them to be. Engineering teams are under pressure to deliver the Hollywood dream, but that dream often doesn’t materialize. Meanwhile, sunk costs pile up, and the clock keeps ticking. This isn’t pessimism it’s recognizing that hype has gravity, and reality has limits. I’d love to be proven wrong and happily jump on the beautiful AI hype train if it ever truly arrives.

Comments

designorbit•1y ago
Love this perspective. You nailed the core issue: LLMs ≠ process engines. And agentic frameworks stacking roles often end up masking fragility instead of fixing it.

One thing I’ve been exploring is this middle ground—what if we stop treating LLMs as process executors, and instead make them contextual participants powered by structured, external memory + state layers?

I’m building Recallio as a plug-and-play memory API exactly for this gap: letting agents/apps access persistent, scoped memory without duct-taping vector DBs and custom orchestration every time.

Totally agree the dream won’t materialize through token prediction alone—but maybe it does if we reconnect LLMs with better state + memory infra.

Have you seen teams blending external memory/state successfully in production? Or are most still trapped inside the prompt+vector loop?

dpao001•1y ago
What is your opinion on Manus. Is it closing in on AGI or is it as you suggest a sticking plaster waiting to break?