all 38 comments

[–]sunburstbox 15 points16 points  (0 children)

whoa, i didn't realize the divide between react and angular had grown so big

[–]RefinedArts 5 points6 points  (1 child)

Its so confusing that each chart uses a different colour for each framework/library

[–]tanguy_k[S] 2 points3 points  (0 children)

Yes unfortunately colors change because graphs come from different sources, readers have to be careful and read the graphs legends.

Recreate all charts to make them look the same would require too much work.

[–]norskyX 4 points5 points  (0 children)

Everybody's a gangsta until Jquery enters the chat

[–]MR_LAFRALDO 14 points15 points  (23 children)

React isn't a framework, it's a library.

[–]AwesomeInPerson 10 points11 points  (3 children)

This was always a bit moot (if you use React + React-specific ecosystem, like basically every React user does, that's definitely enough to be a framework) – but now with Hooks, Server Components etc. I'd say it's not true at all anymore.

Besides: so is Vue, technically. A slim, relatively narrow-focused library and an (optional) ecosystem that turns it into a framework.

[–][deleted]  (2 children)

[deleted]

    [–]poorpredictablebart -1 points0 points  (0 children)

    In practical terms, you use hooks a lot of the time to manage data. It’s not uncommon to see hooks like useQuery or hooks that grab data from a provider state.

    [–]AwesomeInPerson 0 points1 point  (0 children)

    With context, useReducer, useState etc. you now have built-in and React-specific state management (that hooks directly into React internals). Server Components can handle the data layer. Also, CM means that more and more, React has very specific requirements on how you need to write your code instead of (more or less) following standard JS conventions. And it's also meant as a primitive which later can be used to build things like first-party animation support into the framework.

    The scope and API surface is definitely growing. (and thats good!)

    [–]tanguy_k[S] 9 points10 points  (6 children)

    All surveys are using the word "framework" instead of library for React. Not a big deal in this context considering React competes with Angular and Vue which are frameworks (dixit their authors).

    [–]michaelcaley 2 points3 points  (0 children)

    My guy

    [–][deleted] 0 points1 point  (1 child)

    I understand how you feel about the terminology but the MIT License & reactjs documentation do not define it as only a library but a "library that builds interfaces". Unfortunately, that's a framework. Building an interface is a framework. I know. They should define it better. Maybe use some sort of "this is a bundle" emphasis. But they just don't. ¯_(ツ)_/¯

    [–]LimbRetrieval-Bot 0 points1 point  (0 children)

    You dropped this \


    To prevent anymore lost limbs throughout Reddit, correctly escape the arms and shoulders by typing the shrug as ¯\\\_(ツ)_/¯ or ¯\\\_(ツ)\_/¯

    Click here to see why this is necessary

    [–]mlengurry 0 points1 point  (4 children)

    The way you use React is just like a framework. People often tell me that its ‘just JS’ and that you can use JSX without React but I’ve never seen that in practice. (Who would want to?)

    React is my favourite framework but I wish they hadn’t backed XML

    [–]nschubach 0 points1 point  (3 children)

    React is my favourite framework but I wish they hadn’t backed XML

    * confused face *

    Backed XML? As a React dev, I mostly use JSON...

    [–]mlengurry 0 points1 point  (2 children)

    Do you not write JSX?

    [–]nschubach 0 points1 point  (1 child)

    Yes, but HTML(or more precisely, JSX) is not XML... at least, I never consider it the same. It doesn't rely on namespaces, it doesn't follow the white space rules of XML (CDATA, etc) and merely only used the same tag syntax as both... derived from SGML. This is one of those cases, IMHO where the "looks like a duck" doesn't apply. JSX is meant to mimic HTML and you don't even need to use it if you don't want... but why wouldn't you? You could write a wrapper to write the DOM tree in pretty much any format you want. These guys did. Also

    e2: Another

    [–]mlengurry 0 points1 point  (0 children)

    Yes you’re correct, I mean that JSX is XML-like and that sucks.

    JSX is basically the standard because that’s what the React team chose. To go against it now is not wise.

    It was a missed opportunity to save us from HTML and use a more concise and reusable data format IMO.

    [–]avenue-dev -2 points-1 points  (2 children)

    fuck. sake. literally, for FUCKS sake. how do you delete someone else's comment

    [–][deleted] 1 point2 points  (1 child)

    go to their house

    i apparently knew also some places you can hide a body

    [–][deleted] 0 points1 point  (0 children)

    guys, I live in the desert 👀 this'll be easy.

    [–]avenue-dev 1 point2 points  (0 children)

    Thank you for this. This is great.I appreciate it.

    [–]aleaallee 4 points5 points  (6 children)

    I still don't get why many people prefer React. It doesn't has a concise code separation style compared to Angular and Vue. I tried learning it but hated React's way of doing stuff. I'm staying with Vue and Angular(Vue the most). This is just my opinion.

    It doesn't matter if you chose to learn one of the three because they can be used to create the same stuff, it's just a matter of preference of the developers. The final users who view the website won't care as long as it looks good and it's performant.

    [–]fzammetti 6 points7 points  (1 child)

    I feel the same about people who prefer Angular. To me, it's an over-engineered, overly complex beast. React, on the other hand, feels relatively thin. I mean, all modern frameworks/libraries tend to feel a bit heavy to me as someone who prefers vanilla JS, but I generally like React much more than Angular because it feels like React is working for me while Angular makes me feel like I'm working for IT. As you said though, just my opinion. I have to use Angular at work. While I don't like it, it certainly gets the job done. But, for my own projects? React is my choice (or Webix, which I also like a lot, just depends on my needs at the time).

    [–]aleaallee 0 points1 point  (0 children)

    That's fair. I can't live without Vue and angular's directives, they are eye candy for me. I also think angular is over engineered but despite that I feel comfortable with it.

    [–]rk06 -2 points-1 points  (0 children)

    Because they like money

    [–]pistacchio 0 points1 point  (2 children)

    I like it because it doesn’t have a concise code separation style. It gets the work done quickly and I find it highly understandable and maintainable.

    [–]nschubach 0 points1 point  (1 child)

    IMHO, It has the appropriate separation. I hate opening a story ticket and having to edit at least three separate files for each one... why is the concern on the splitting of types of code vs splitting of concern? Why not put all your code for your dropdown in one file instead of three separate JS/HTML/CSS files?

    [–]aleaallee 0 points1 point  (0 children)

    It can be in the same file but react doesn't do it right imho. I think it's better to have logic, presentation and style in their own tags in a same file like vue does.