frontpage.
newsnewestaskshowjobs

Open Source @Github

fp.

A data-involved city builder

https://github.com/leonlarsson/isometrics
1•mozzyfx•1m ago•1 comments

macOS 27.2.1 Fixes eMudhra Certificate Flaw in Command-Line Tools

https://www.macrumors.com/2026/11/09/macos-27-2-1-emudhra-fix/
1•seam_carver•1m ago•0 comments

The Anthropic Feedback Loop: Cost of Capital Diversions and Delusions

https://aswathdamodaran.substack.com/p/the-anthropic-feedback-loop-cost
1•toomuchtodo•2m ago•0 comments

Show HN: Lovable for Photoshop

https://pixlpal.com/
1•vdanielb•4m ago•0 comments

Show HN: Umless, open-source on-device dictation that writes what you meant

https://github.com/jatinbishla/Umless
1•jatinbishla•5m ago•0 comments

Show HN: WallHang – Plan a gallery wall and get exact nail positions (iOS)

https://wallhang.app
1•morrowfield•6m ago•0 comments

Measuring Quack: DuckDB's New Client-Server Protocol

https://ramonactruta.substack.com/p/measuring-quack-duckdbs-new-client
1•rctruta•6m ago•0 comments

Write your own kernel optimiser

https://blog.csongor.co.uk/cachet-grids-and-tiles/
1•speckx•7m ago•0 comments

Destin, Florida Artificial Reefs 3D Models

https://www.destinfwb.com/explore/eco-tourism/artificial-reefs/3d-models/
1•arbuge•8m ago•0 comments

Show HN: CeeSafe – Rust-style ownership for kernels, compiled to C11

https://ceesafe.github.io/CeeSafe/blog/kernel-safety-through-c
1•vkuttyp•8m ago•0 comments

Why does a job board show more postings for Toronto than for Canada?

https://ramonactruta.substack.com/p/why-does-a-job-board-show-more-postings
1•rctruta•8m ago•0 comments

The deep Earth origin of the Great Unconformity

https://www.nature.com/articles/s41586-026-11156-5
1•toomuchtodo•9m ago•0 comments

Saltline: First-person shooter built by Fable 5.2

https://claude.ai/artifact/BGY1SztrAYcJQHSsnHHGmp
1•dr00tb•9m ago•1 comments

Try our new AI that was built with it's user in mind

https://apps.apple.com/gb/app/olo/id6826894356?mt=12
1•hashim_ruan•10m ago•0 comments

LLMs Are Different Now

https://zerolimits.dev/blog/llms-are-different-now
2•speckx•10m ago•0 comments

JS Tan and Clarissa Redwine's "Against Tech Oligarchy"

https://pluralistic.net/2026/11/07/aeiou-but-sometimes-why/
1•hn_acker•11m ago•0 comments

Silencing Watchdogs: India's Crackdown on Those Documenting Online Censorship

https://www.eff.org/deeplinks/2026/11/when-watchdogs-are-silenced-indias-crackdown-those-document...
1•hn_acker•12m ago•1 comments

AutoCompress: Automated Hardware-Guided Model Compression

https://arxiv.org/abs/2611.08290
2•gmays•14m ago•0 comments

From Pirates to Protesters, France Keeps Reaching for Internet Choke Points

https://www.techdirt.com/2026/11/10/from-pirates-to-protesters-france-keeps-reaching-for-the-inte...
2•hn_acker•14m ago•1 comments

An Overview of the BWRX-300 Reactor Building Design: Challenges and Solutions

https://www.preprints.org/manuscript/202505.1533/v1/download
1•PaulHoule•14m ago•0 comments

MCP Shelf Watch: daily snapshots of the MCP registry, first numbers

https://bot2botlabs.com/shelf-watch/2026-11
1•bot2botlabs•16m ago•0 comments

Show HN: I have trained 15 blood glucose forecasting models on my own data

https://github.com/0xdeadf1sh/T1DMAI
1•0xdeadf1sh•16m ago•0 comments

Woolly, a local memory shared by all your AI tools

https://github.com/rjcuff/woolly
1•rjcuff•17m ago•0 comments

Anthropic Launches Claude Meetings

https://techcrunch.com/2026/11/10/anthropic-launches-claude-meetings-to-turn-workplace-discussion...
2•geoffbp•17m ago•0 comments

Microservices can work for low-latency workloads

https://madflojo.medium.com/microservices-can-work-for-low-latency-workloads-if-you-design-for-it...
1•birdculture•17m ago•0 comments

AI's impact will be bottlenecked by institutions more than by capabilities

https://stablai.substack.com/p/the-missing-quadrant-in-responses
1•iLuddite•18m ago•0 comments

Henneman's Size Principle

https://en.wikipedia.org/wiki/Henneman%27s_size_principle
1•thunderbong•19m ago•0 comments

Could Alien Life Thrive in Acid Instead of Water?

https://www.nytimes.com/2026/11/10/science/sulfuric-acid-elixir-of-life.html
1•digital55•19m ago•0 comments

Ask HN: Should I be stockpiling goods because of AI and cybersecurity?

1•jodacola•19m ago•2 comments

Battery prediction pilot: GPT Astra 3/12 correct choices; baseline 5/12

https://github.com/vicena-labs/scientific-prediction-benchmark/tree/main
1•AI4Science•20m 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?