Reginaldo

@JustDeezGuy FP is indeed great at that, but is there really a “pure FP” somewhere? I mean, if your program is 100% pure, it never does anything real, never affects the real world, never runs effects basically? state can never be reduced to zero, it exists at the boundaries at least

Pure FP is about “reducing the state a developer has to hold in their head” to 0.

@unclebobmartin More readable than java tbh Lisp is the ultimate language

This is what codex believes would be the best language for _IT_ to program in. Here's hello world. (module example/hello (imports) (export main) (fn main (params) (returns String) (effects ()) (requires true) (ensures true) "Hello, world!")) I had it write a compiler for this language that runs on the JVM. It emits byte code. Note the hint of DBC. Note also the lispy syntax. This is what _IT_ said it wanted when I told it that humans didn't need to read it.

@TylerAlterman Most things are good except politics, and at this point I think this is everywhere, the world is a nice place to live

Why isn’t it common knowledge that Brazilians have the Mandate of Heaven? They’re clearly having a better time than the rest of us. They should teach us how to live

What happens when engineering and music blend together? Something awesome regibyte.github.io/music-theory-e… What started as a curiosity project, now available as a complete music theory exploration playground. Free and open source for everyone! Learn interactively at your own pace!

I am a sucker for a good mediapipe demo Like yeah, people don't always want to have their hands in the air for Minority Report-style UIs but this is just so cool

When I created Claude Code as a side project back in September 2024, I had no idea it would grow to be what it is today. It is humbling to see how Claude Code has become a core dev tool for so many engineers, how enthusiastic the community is, and how people are using it for all sorts of things from coding, to devops, to research, to non-technical use cases. This technology is alien and magical, and it makes it so much easier for people to build and create. Increasingly, code is no longer the bottleneck. A year ago, Claude struggled to generate bash commands without escaping issues. It worked for seconds or minutes at a time. We saw early signs that it may become broadly useful for coding one day. Fast forward to today. In the last thirty days, I landed 259 PRs -- 497 commits, 40k lines added, 38k lines removed. Every single line was written by Claude Code + Opus 4.5. Claude consistently runs for minutes, hours, and days at a time (using Stop hooks). Software engineering is changing, and we are entering a new period in coding history. And we're still just getting started..

Small unoffical update on TanStack Table: After not being able to dedicate as much time in 2025 to TanStack Table, I'm at least ending the year having mostly figured out some hard problems. It's going to be a challenge to actually organize and ship everything in 2026, but I'm much more hopeful that it will actually happen compared to how I felt a month ago. Without diving into the details too much yet, V9 should have much better state management with TanStack Store (similar to TanStack Form patterns), be compatible with the React Compiler, have much better tree-shaking, use much less memory when there are lots of rows, have a type-safe plugin system where you can much more easily extend TanStack Table with your own custom features, and have new Devtools and debugging options that are much more useful. Talk is cheap until it ships and you're actually able to try it, but I'm really hoping that this will be a solid foundation for years to come for this project.

@KevinVanCott You’re a legend Kevin! Many thanks from all of us 🙏🏼

@jacobmparis The true problem is people putting all the behavior of their system inside react, when in reality it should only concern itself with rendering the view. Thats where we lost it

A huge reason useEffect is a red flag in react is because it allows code like this > On A, set B. When B changes, do C when what you really need is > On A, set B and do C 🚩when you see a useEffect, make sure it’s not introducing this problem

I hope someone finds value in this, for my game it was the key to a successful delivery Not the tech, the idea, the library just helps you see more clearly what the idea is about

github.com/RegiByte/braid… Braided react let's you define and control your system completely independent of the react lifecycle, you decide when and how to stop, you compose freely without any opinions imposed upon your architecture

I've made a library! While working at a very important client project, a lan-first multiplayer game, there was a lot of websockets, webrtc and recovery routines needed for the game to work React kept killing my things, so my system had to outlive it github.com/RegiByte/braid…

@jherr Imagine if claude could really learn and remember the learnings afterwards, a dream come true! Right now we have to manually manage and store context that we want them to remember later, would be nice if learning and remembering (per user) was a thing

Claude made a mistake last night. It admitted the mistake with grace and we moved on in our conversation. And I'm ok with that, and I think most of us our. AI "experts" makes mistakes. All experts makes mistakes, including human ones. Something to think about the next time you hold humans to a different standard than AIs. Making mistakes is natural. It's part of the learning process. Experts wouldn't be "experts" if they hadn't made a lot of mistakes. Stop putting folks on a pedastal and expecting experts to be perfect. Experts are just folks that have made more mistakes than you have in a particular area and have been smart enough to learn from those mistakes, and from others.

@theodorvaryag @examachine It's fine, this is just a friendly conversation between fellow devs, your post is great!

@RegiByte @examachine can you guys have the lisp esl slapfight somewhere not in my reply notifications

The year is 1996. You are Sun Microsystems. You're announcing the first JIT compiler for the Java Platform. The year is 1984. You are L. Peter Deutsch and Allan M. Schiffman. You're extending prior art on JIT compilation for Smalltalk. You publish the paper “Efficient Implementation of the Smalltalk-80 System.” It's the 70s, you're Danny Bobrow, Warren Teitelman, Ron Kaplan, and Larry Masinter working on Interlisp. You design & implement an IDE-style Lisp with block compilation and on-demand compilation it just keeps going back to eval, McCarthy, and Steve Russell's hand-coded eval for the IBM 704.

@examachine @theodorvaryag Alright, have a great rest of your day sir!

@RegiByte @theodorvaryag JVM is not acceptable to me. I am not a "web developer". I reject JVM.

@examachine @theodorvaryag Nice! Lisp is indeed a great language with a general purpose fit, Clojure just improves upon what was already there, it doesn't sacrifice anything

@RegiByte @theodorvaryag x.com/i/grok/share/V…

@examachine @theodorvaryag You don't agree? or do you not know clojure?

@RegiByte @theodorvaryag WHAT