9
msdsk
41d

As a vue fan who has to work with react - I don't understand the appeal of the latter. Everything seems just pointlessly dotted with boilerplate, grossly over-engineered (if that's what I should call solutions like the react approach to CSS-in-JS) but at the same time very clunky.

Honestly, the only convincing point for using React that I've heard is about it being backed by Facebook - but, on the other hand, After having to work with some facebook IT solutions and knowing the shit they could pull with their APIs and stuff, I wouldn't count it as too big of an upside.

Why didn't you switch from react to vue?

Comments
  • 0
    The fact that it’s backed by FB is enough. If you were FB people would sit in a long line for a chance to suck on every one of your shits.
  • 2
    Until a clear winner emerges, I'm aiming to stay as far away from all frontend frameworks as possible.
  • 1
    I use both, and to me, React has two advantages over Vue
    - error messages are clearer. Most of the time, it explains what is wrong in the console, and a simple google search is solving absolutely everything
    - React uses less magic to compile (I don't use CRA), so the behavior is more understandable

    Plus it's backed by Facebook, which is important because FB has consistency, unlike Google

    the only weakness to me is the lack of guidelines about what you should do and don't.
  • 0
    Agree, besides the cli helps to keep things standardized. But again react is a library so I guess it’s not comparable on that point.
  • 1
    As an engineer on Angular, I just look down from Olympus and sip my lemonade in amusement.
  • 1
    I agree--the lack of a standard way to do CSS in React results in lots of weird solutions. However, it's hard for me to go back to Vue because I love the simplicity and TypeScript-friendliness that JSX and React (respectively) provide. Vue has it's own kind of bloat--tons of features that allow you to compose components together in ways that violate "props down state up" and a huge API of mostly overcomplicated stuff that starts with "$".
  • 0
    @SortOfTested I'm planning to go to Valhalla anyway
  • 0
    With modern browsers, if you need any of these piles you are doing something wrong.
  • 2
    You guys keep worshiping your idols and false gods. When you grow weary of them just say the word and I'll be here to guide you toward the path of enlightenment.
  • 1
    @M1sf3t they ain't ready for it man
  • 0
    @AleCx04 yea that would seem to be the case for a lot of people. I think I blew someones mind yesterday when I cloned a table search they were trying to implement with less code than what they had usin jquery.
  • 2
    @RobbieGM There isn't a standard way because we do not do css in js. We do id-s and classes. The css is written once, compiled once by the browser and never altered. We can fucking read attributes in CSS. We have zero reason to write css in JS. Jesus Fucking Christ, why do people always find a way to absolutely rape the system and make the pipelines do a loopty-loop? Why?
  • 0
    @Lor-inc css in js or js in css? I can never keep them straight
  • 1
    @SortOfTested bruh angular is yuck
  • 2
    VUEVUE WOO
  • 0
    @M1sf3t the word!
  • 0
    @M1sf3t I am proud to say that I made a project with JS-in-CSS
  • 0
  • 0
    @lopu
    Lol. Vue is an angular 1 clone.
  • 0
    @Lor-inc I'm guessing you can do something with the content property but lol
  • 0
    @SortOfTested oh interesting
  • 0
    @msdsk no idea what that even means. I wasn't exaggerating, the only time i mix the two is when I need to swap a class or style, which consists me typing class={ variable } or style={ `prop: ${variable}`} directly in my html.
  • 0
    @lopu I don't think content can be actual full-featured HTML. It would have pretty fucking terrible consequences if you could assign DOM children to any element with css.
  • 0
    @Lor-inc

    @M1sf3t

    I made an SCSS system with documentation in the SCSS files themselves - I would parse the comments in a static page generator that would automatically turn the entire file into a neat documentation website. It might be sketchy but it works really well.
Add Comment