4 ms·

Yeah, the most WTF thing I've seen React do is to mess with console.log by silencing them (WTF #1), which was particularly appalling since React did it only bec

Yeah, the most WTF thing I've seen React do is to mess with console.log by silencing them (WTF #1), which was particularly appalling since React did it only because it run the rendering twice under StrictMode (WTF #2), and only during development so you're not sure what the real behavior will be until you run it on production mode (WTF #3). Messing with the console is such a no-go that I'm appalled it even passed the drawing board, making the "React isn't a framework, it's a library" argument even more bonkers than it already is.

azangru 3y ago
Oh, I totally forgot how mad I am at React because, with the new hooks-based approach, it has removed the semantic of "do this side effect just once when a component mounts". Mounting a component is such a crucial part of the life cycle of any web component that I am amazed that the React team does not have a special way of handling this; or that with their new architecture they are not guaranteeing how many mount-unmount cycles a component will go through. This all makes me want to move on to web components; but of course now the project that I am a developer on is locked in React :-(