Skip to content
View redbar0n's full-sized avatar

Block or report redbar0n

Block user

Prevent this user from interacting with your repositories and sending you notifications. Learn more about blocking users.

You must be logged in to block users.

Content in all repositories owned by your account will be closed.
Maximum 250 characters. Please don’t include any personal information such as legal names or email addresses. Markdown is supported. This note will only be visible to you.
Report abuse

Contact GitHub support about this user’s behavior. Learn more about reporting abuse.

Report abuse

Pinned Loading

  1. Some ecosystem contributions Some ecosystem contributions
    1
    ### Some of my ecosystem contributions
    2
    
                  
    3
    Oct 2026 -
    4
    I helped design how the [One.js]([url](https://onestack.dev/)) framework handles searchParams. One is a framework that unifies React + React Native, so you can build crossplatform apps from a single codebase without code duplication or needing multiple frameworks (like Next + Expo).
    5
    https://github.com/onejs/one/issues/1039
  2. react_architecture_with_simple_decen... react_architecture_with_simple_decentralized_stores_and_explicit_rendering.md
    1
    ### A new front-end architecture for React apps, with simple decentralized stores and explicit rendering control.
    2
    
                  
    3
    This is an idea that I devised through working with AI through many revisions.
    4
    
                  
    5
    As an experiment (worked out together with Gemini AI), this should be a practical and very performant realization of the [Functional Core, Imperative Shell](https://www.destroyallsoftware.com/screencasts/catalog/functional-core-imperative-shell) (FCIS) architecture for a TypeScript front-end in React:
  3. Nearly fully sound type system in Ty... Nearly fully sound type system in TypeScript
    1
    ## How to get TypeScript as close as possible to a fully sound static type system?
    2
    
                  
    3
    Like in ReScript, PureScript, OCaml, Elm etc.
    4
    
                  
    5
    To get more sound type inference. To avoid type errors slipping through to production in spite of the type checking.
  4. Functional Core, Imperative Shell (F... Functional Core, Imperative Shell (FCIS) in a TypeScript back-end
    1
    ### FCIS architecture in a TypeScript/JavaScript backend
    2
    
                  
    3
    I worked with Grok AI through many revisions to devise how exactly a FCIS architecture could look in a TypeScript/JavaScript backend. It is similar to the Onion architecture, but more pure (no mocks). This is the result of that work.
    4
    
                  
    5
    ---
  5. reactjs.org reactjs.org Public

    Forked from reactjs/react.dev

    The React documentation website

    JavaScript

  6. The MVC-widget - Through refactoring... The MVC-widget - Through refactoring boilerplate out from an XState example
    1
    # What if you could have vertically sliced MVC-widgets, that looked something like this?
    2
    
                  
    3
    Using React and XState.
    4
    
                  
    5
    ```jsx