Advertisement
Advertisement
β‘ Community Insights
Discussion Sentiment
100% Positive
Analyzed from 381 words in the discussion.
Trending Topics
#same#behaviors#logic#neuromorphic#paper#works#bricken#computational#instead#quantities
Discussion Sentiment
Analyzed from 381 words in the discussion.
Trending Topics
Discussion (9 Comments)Read Original on HackerNews
"...demonstrates its capabilities through worked examples" - The hell it does, your "examples" are three lines long. If you're going to compare it with LLMs, then have it do something LLM-ish. Or hell, the MNIST number recognition task would be better than the "hey look i modeled a flip-flop in my funny language" example.
Am I being harsh? Yes, I am. The author is claiming that they have a system that can automatically generate code for "quantum" and "spintronic" computers, yet offers zero proof of that.
The difference is what you're constraining. Bricken works with containment and distinction. UCE works with conserved quantities β closer to physics than logic. You define constraints over those quantities, and computational behaviors like memory, oscillation, and logic gating fall out of satisfying them simultaneously.
The other big difference is the output. UCE doesn't produce a proof or a reduction β it produces a state-transition graph that compiles directly to hardware. Same rules, different substrates. That's what the Embodiment Mapper layer does.