GithubHelp home page GithubHelp logo

Bug: clicking a material ui button with preact signals present crashes react with Uncaught Error: Should have a queue. This is likely a bug in React. Please file an issue. about react HOT 2 CLOSED

insberr avatar insberr commented on June 24, 2024 1
Bug: clicking a material ui button with preact signals present crashes react with Uncaught Error: Should have a queue. This is likely a bug in React. Please file an issue.

from react.

Comments (2)

gaearon avatar gaearon commented on June 24, 2024 161

In addition to overriding React's public API, Preact Signals works by taking React internals and patching them while relying on fragile assumptions about how they work. This library is an entirely unsupported way to use React. The only reason it isn't constantly breaking is that we haven't done stable releases recently.

If React was a piece of hardware, this is exactly the kind of thing that voids the warranty. We can't help with debugging issues here, and we don't consider them bugs because so much has been meddled with.

If you have a repro case that doesn't rely on Preact Signals, we'd like to have a look. Thanks.

from react.

benemmaofficial avatar benemmaofficial commented on June 24, 2024 126

At least they got State Mangement right. Instead of talking about how they meddled with the ergonomics of React, isn't it better to learn from what they have done, to find a way to officially support Signals.

Its just more linear and feels natural to work with. I almost wonder why the core team had to make initial state management a pain with things like the reducer pattern which introduces a whole bunch of of issues.

If react where a design canvas on a scale of 10 it would be ranked very poorly. Ranking react at (2) would be very modest.

We all look at Signals and think useState, useReducer, useSelector, Actions, Dispatchs etc... are state management primitives the react core team designed to sound smart.

They are inefficient, long, hard, unnatural and just outright unpleasant to work with a concept like Signals completely render all those concepts redundant.

Lastly the preact team may have patched a few bits and pieces to make Signals work for the most part but at least they made State Management digestible.

And I suggest React does the same.

TLDR: The only reason we use JS is because of React and the only reason we use React is because of meta frameworks like NEXTJS
& REMIX.

I speak for most or all react developers.
Cheers!

from react.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.