7
Comments
  • 3
    Yep. Got to wonder why would anyone even use React.
  • 2
    @DanijelH woh woh woh there 🤣
  • 3
    @dUcKtYpEd Not trying to start a flame war just commenting in peace 😆
  • 2
    @DanijelH my favs still react then react then vue but vue is also what I do my job entirely in so it can’t be my fav haha.
  • 5
    @DanijelH yOu WoNnA St4rT a WaR mATe?
  • 2
    vuejs is ok but still react is my <3
  • 2
    @monmadmatt saaaaaaame then angular
  • 1
    *a silent $(Jquery) enters the room*
  • 0
    @DanijelH because some people prefer the syntax and it has huge community backing?
    Vue is great but I dont find it easier. Especially with the introduction of react hooks. Also I prefer jsx over the vue dsl
  • 1
    React hooks steal the show
  • 0
    React hooks is a solution for another problem react created for itself. Cmon guys, React has a ton of problems. Not even mentioning that it's only a single library and all other things like routing and store is not created and maintained by Facebook and when you combine all that together you get Frankensteins monster. @dUcKtYpEd @musician
  • 0
    @musician Also JSX is nothing more than PHP. Facebook was initially created on some version of PHP and I understand why Facebook created React to mix Code and HTML like in PHP but we all now what kind of a mess that can create. There's a reason a lot of people does not like PHP.
  • 1
    @DanijelH vue also mixes code with html. Its just a different syntax.

    Why are the vue guys always so preachy? I rarely see react devs hating on vue. Just use what works for you but stop trying to convert everyone to ''your" framework.
    I worked with angular vue and react. In the end they all do the same thing. Its just a different approach.
  • 1
    When I’m writing react, I feel like I’m truly writing my front end with JavaScript. When I’m using vue, I feel like I’m writing just html again with vues syntax, following vues class syntax. I do like that vue has routing and vuex built in though. Makes it easier to spin up on
  • 0
    @musician It does not. That is not "mixing code", that is adding custom additional HTML tags and is not in any way similar. You can see people adding dynamic "data-{something}" tags with for instance jQuery and that is a valid HTML.
  • 0
    @dUcKtYpEd If it works 4 you then great but no designer can help you in that state since many agencies deal with HTML and CSS.

    Did I mention React performance issues and all the unnecessary renderings without "shouldComponentUpdate" or "pureComponent". All of that Vue solves out of the box. I have 101 problem with React. It's a living mess.
  • 1
    There’s a wrong way and right way to write react. If all of your logic is in your jdx then it’s going to be hard to read. just like with php, abstract your logic and utilize jdx for simple conditional renderings. And ya I realize purely html/css shops might struggle with jdx. My suggestion would be to work with competent shop that understands the most widely used JavaScript framework around.
  • 0
    @dUcKtYpEd Gr8 example and another problem!

    Web shops usually have a ton of filters and guess what, React does not have 2way binding. My god, if you have 20 filters you have to write 20 on change methods and have to maintain them. I'm not even gonna say what that looks like when they also depend on one another. All I want to do is bind my filters to my state and React can't even do that.

    I am telling you, there's problems on any side of it. React was created as a helper library and now it's something it shouldn't be.

    I am glad you like it and if it works for you then gr8 but I found that that Vue out of the box solves a loot of problems React has.
  • 1
    @DanijelH I work with vue for my job ever day. It’s ok and it’s easy to understand but I don’t necessarily enjoy using it. Maybe that’s because I have to use it at work haha. The last time I used react was 6 months ago though and I’m pretty sure I utilized two way binding all across my app
  • 0
    @dUcKtYpEd Maybe that's the case yeah :D ..give it a chance xD
  • 0
    @DanijelH
    Reacts performance is fine. In real world scenarios all 3 frameworks perform pretty much the same. Huge companies use it for big projects.
    If yours is slow your code probably sucks.

    You can use and love vue without shitting on everything else ;)
    In a few year we all be using something else anyway
  • 0
    @musician My friend, not shitting, just giving away facts. Yes, all perform similar but the big difference is that you have to put a lot of effort in React for it to be performant. That's the difference and that's what I wrote.
  • 0
    @DanijelH I don’t complain about anything that takes extra effort when it comes to framework. I can get my POC out the door with phps laravel prob 3x quicker then with .NET but then ya know I’m dealing with allllll php when C# with .Net historically scales miraculously with an outrageously large base behind it. Both good tools. One takes longer to implement. Not a bad thing. React is a lot higher in popularity and usage. Maybe we should start with answering why that is
  • 0
    And I actually take back my compliment about vuex. It’s been a living hell with our app and there is no straight way to test asynchronous actions. The guy that writes the tests is a fuckin silo. Accessing a getter looks like
    this.$store.getters[“getFirstName”]
  • 0
    @dUcKtYpEd I agree with you, React is more popular even with all that bs about licensing that went down. I hate Facebook because of that. I believe main reason for this is because Vue gained its popularity from version 2+. React is here much longer.
  • 0
    @DanijelH maybe so. Too add to that, I find it highly impressive how popular and large of a base angular has after making such a large and ugly rewrite from 1 to 2. Thank god it’s easy to use now and quite sexy of a framework but man that 2 was a beast to tackle
Your Job Suck?
Get a Better Job
Add Comment