[GiorgioG]

React isn't a framework. In order to build an app, you have to cobble together a bunch of other libraries to use with it to build something meaningful.

As someone coming from an Angular shop, I started a new job a few months ago that uses React on the frontend. My main gripe so far is there is no one "way" to do X in a react-based app. For an enterprise with lots of developers, Angular seems like a better fit - unless you want to spend months coming up with standards. Angular has its own issues of course - it's much more rigid and has a steeper learning curve.

[lloydatkinson]

Are people still having this strawman argument over if react is a library or a framework? Would my argument have changed if I'd put "framework/library" in my comment? No.

[bryanrasmussen]

we need an onomatopoeic composite here, to stop the continuous arguments, maybe fribrary or lamework.

[recursive]

"lamework" feels like it perfectly captures my experience of writing react apps. I'd go with that one.

[bryanrasmussen]

I find React perfectly fine for writing SPAs, as long as what is being written is actually suited to being an SPA. Otherwise I find it as dreadful as any time you use a hammer to pound a screw in place.

[tomc1985]

"Framurary" is kind of fun. Though lamework also describes my experience with it

[Rafert]

Isn't that the gap the likes of Next.js are filling?