Why we moved from Angular 2 to Vue.js and why we didn’t choose React

Post by mercer » Sat, Sep 02, 2017, 8:12 AM UTC

erokar wrote: post #30

che_shirecat wrote: post #20

Earlier quoted context omitted.

> It should take no more than 20 minutes to learn JSX. it should, but in practicality, for most front-end devs especially junior ones, it's not. Moving Angular 1 devs to Vue gets actual work going 3-4 times (anecdotal experience) quicker than with React. For most smaller shops/startups Vue is almost always a better idea - it's much easier finding devs (especially remote/<100k comp ones) with previous Angular 1 experi…

You are probably right that Angular 1.x devs will ramp up a bit faster in Vue than React. Angular and Vue both add template syntax to HTML, which will be more familiar to Angular devs. However, I do not think initial ramp up time should matter that much, at least not for long running projects. More important questions are: How will the project scale? How easy will it be to maintain? > React is overengineering for mos…

Post by emodendroket » Sat, Sep 02, 2017, 11:19 AM UTC

keymone wrote: post #135

emodendroket wrote: post #125

Earlier quoted context omitted.

OK, but I don't agree. I think it is valuable to separate your template and behaviors associated with it for exactly the same reasons.

it is valuable to separate, but why is it valuable to force a different syntactic layer, often with heavy constrains on what logic can be expressed which inevitably leaks back into various helpers implemented in the layer you've just separated yourself from? why is it not better to separate using mechanics native to your language?

Post by Shorel » Sat, Sep 02, 2017, 2:19 PM UTC

AlfeG wrote: post #137

jinder wrote: post #15

"We invested in a beta product and then shock horror - it changes before it's released. Let's blame the framework on that poor choice." "We were unable to learn how to use TypeScript properly, so let's abandon gradual typing and suffer a net loss in productivity over the longer term."

We actually implemented quite a big project with Vue/Typescript. Half year later we removed all ts code in favor of plan js.

Post by root_axis » Sat, Sep 02, 2017, 3:52 PM UTC

dwaltrip wrote: post #138

root_axis wrote: post #103

Earlier quoted context omitted.

> I personally don't see any difference with doing a loop in JSX and doing a loop in HTML using special tag attributes. Don't do that. Perform loops outside of the final template. People get confused because they don't remember that JSX is just a tree of nested React.createElement function calls, so they decide that they should mix looping logic into a block of JSX because that's what they'd do in PHP even though you…

Do you have any specific reasons for why `items.map` should not be inside a jsx tag? Your comment doesn't make it clear why you think this.

    const MyComponent = function MyComponent(props) {
        return React.createElement(
            "div",
            null,
            React.createElement(
                "h1",
                null,
                "List of items"
            ),
           React.createElement("br", null),
           props.itemData.map(function (itemData) {
               return React.createElement(Item, { data: itemData });
           });
        );
    };

Post by dwaltrip » Sat, Sep 02, 2017, 6:11 PM UTC

root_axis wrote: post #147

dwaltrip wrote: post #138

Earlier quoted context omitted.

Do you have any specific reasons for why `items.map` should not be inside a jsx tag? Your comment doesn't make it clear why you think this.

> People get confused because they don't remember that JSX is just a tree of nested React.createElement function calls, so they decide that they should mix looping logic into a block of JSX because that's what they'd do in PHP even though you'd obviously not do that when looking at raw code. Basically what I'm saying is, if you were just writing React.createElement function calls, it'd be more obvious that the items.…