React Oxide

Dev tools

code editor

SHOW HN2021

React Oxide

open source ReactJS code editor with tabs, files & webDAV.

github.com

#code editor#react#monaco editor#webdav#browser ide

38points
17comments
#1,013of 2,533 in 2021
Top 40%of 2021 by points

How HN took it

RoastedHalf or more of the comments are critical

0 positive, 3 neutral or asking, 1 mixed, 4 critical, out of 8 comments about the project. Thread score -0.35.

Design: 0 for, 3 againstDocs: 0 for, 1 against

The thread, comment by comment

Each row is a top-level comment and its replies, in HN's order. Select a cell to open that comment on HN.

positive neutral or mixed critical about another commenter or something else the maker

What HN said

What people liked

  • Event-driven state approach praised as simple and workable for small apps

    From 1 comment
    • So far eventemitter has resulted only in simplicity and no race conditions. Perhaps that's because it's a small application.
      andrewstuart on HN
  • Useful review tips on typed emitters and React context

    From 1 comment
    • The EventEmitter pattern seems interesting! I can't say I've wrapped my head around it enough to weigh the benefits and drawbacks. I would point out a few things after a quick…
      brianshaler on HN

Objections

  • Event emitter state coordination can cause race conditions and lost state as UI grows

    From 2 comments
    • The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data…
      lf-non on HN
    • It seems (OP correct me if I'm wrong) that it uses actual browser events, which are asynchronous (where normally Redux messages are sent and reacted-to synchronously). This…
      brundolf on HN
  • No error handling or tests in the project

    From 1 comment
    • > There's no error handling at all right now - if any file operation fails then there's no information given, it just goes splat. > There's no tests - and I'm not writing any - I…
      jmnicolas on HN
  • Dislike of building the approach on React

    From 1 comment
    • Reading your about your style, I can't help but wonder what's the point of using react. You clearly don't like it (and neither do I). Is it purely because nobody seems to care…
      beebeepka on HN

Requests

  • Try MobX, Redux-style state or Effector instead

    From 3 comments
    • The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data…
      lf-non on HN
    • Have you ever used mobx?
      leetrout on HN
    • Seconding MobX; it elegantly solves most of the issues with events (both maintainability and performance) while also being more ergonomic/concise. I can't praise it enough.
      brundolf on HN
  • Use typed emitters and React context for better typing

    From 1 comment
    • The EventEmitter pattern seems interesting! I can't say I've wrapped my head around it enough to weigh the benefits and drawbacks. I would point out a few things after a quick…
      brianshaler on HN

Questions

  • How does this differ from Redux and dispatch/reducer architecture

    From 1 comment
    • > The React code is written in a style I call "Event driven React" How does this differ conceptually from Redux and the general dispatch/reducer architecture? would be interested…
      have_faith on HN
  • What are the drawbacks of the event-driven approach

    From 1 comment
    • Hi folks this is React Oxide. It's a minimal code editor that runs in a browser. MIT licensed, code at: https://github.com/bootrino/reactoxide I wrote React Oxide because I…
      andrewstuart on HN

Alternatives named

  • MobX

    From 2 comments
    • Have you ever used mobx?
      leetrout on HN
    • Seconding MobX; it elegantly solves most of the issues with events (both maintainability and performance) while also being more ergonomic/concise. I can't praise it enough.
      brundolf on HN
  • Redux

    From 2 comments
    • The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data…
      lf-non on HN
    • > The React code is written in a style I call "Event driven React" How does this differ conceptually from Redux and the general dispatch/reducer architecture? would be interested…
      have_faith on HN
  • Effector

    From 1 comment
    • The issue with using eventemitter for state coordination is that when the UI grows into complexity you run into race conditions where some component isn't showing the right data…
      lf-non on HN
  • Vue

    From 2 comments
    • Reading your about your style, I can't help but wonder what's the point of using react. You clearly don't like it (and neither do I). Is it purely because nobody seems to care…
      beebeepka on HN
    • Vue supports observables. So you can have observables that shared across components (for simple use cases). For more involved scenarios, it is possible to libraries like Vuex…
      lf-non on HN
  • Svelte

    From 1 comment
    • Funny, I came here to insist that you guys try Svelte. They took the best parts of Vue and React, made them so much better, and baked reactivity and state management into…
      FractalHQ on HN

Category, keywords, summaries and labels on this page were made by AI (Thread Reader v2) and not checked by hand. Each point links to the comments it came from.

Add a badge to your READMEShown on HackerShow
[![Shown on HackerShow](https://hackershow.org/badge.svg)](https://hackershow.org/show/28702006)