Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Vue.js is Wikimedia Foundation's future JavaScript framework

lists.wikimedia.org

Post reply on HN
Print view View original

31–40 of 204 posts

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#31

Post by mosdl »

ggregoire wrote: post #21
ferdowsi wrote: post #4

Congratulations to the Vue team, this is definitely a big win for them. Reading through the RFC is really interesting. They specifically call out the dependency on Facebook as effectively being React's Single Point of Failure, citing their negative experiences with HHVM. And for all of the love that people give React's big shifts (like hooks), the RFC specifically counts this against them, given that best practices h…

Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I've been using React on a daily basis for 5 years). Oh boy I was wrong. Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially wh…

props propagation was indeed horrible, but you can use context to avoid that (or use other stores).

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#32

Post by paulddraper »

qmmmur wrote: post #26

Not even a consideration of svelte?

Svelte is very new (a year and half of meaningful adoption).

React, Angular, Vue.js are the most popular, in that order.

I hate to say might=right, but for a project like Wikimedia, choosing a mature, popular framework is important.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#33

Post by ggregoire »

flowerlad wrote: post #24
ggregoire wrote: post #21

Earlier quoted context omitted.

Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I've been using React on a daily basis for 5 years). Oh boy I was wrong. Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially wh…

> you had to wrap your components into x number of HOCs to inject the props your component needed, risking props collision, making it really hard to debug... What kind of application are you developing? Do you have complex UI? Or just lots and lots of pages where you reuse components a lot?

The kind of app that has 60k LOC, dozen of pages, makes 15 fetches per page (e.g. a report with 5 charts and 3 series per chart), reuse data between pages to avoid remaking the same fetches, have 1 or 2 forms synchronized between every page (like dates and selects filters), save the filters into the URL query params to be able to share the report and restore it when you open/refresh the app, and so on.

You end up with code like this at the bottom of your files

    myCustomHOC1(
      myCustomHOC2(
        withRouter(
          reduxForm({ form: 'filters', initialValues, destroyOnUnmount: false })(
            connect(mapStateToProps, mapActionsToProps)(MyComponent)
          )
        )
      )
    )
Although it's probably not that common anymore (as OC said, practices changed), it was a common pattern a few years ago.

In the new project I started last week, I'm using only hooks/context and a few libraries like react-router (useHistory, useParams), react-query (useQuery, useMutation), react-hooks-form (useForm)… and it has been a breath of fresh air. react-query is definitely another "big shift", it completely changed the way I used to think about fetching data and centralize it. It's very good, I highly recommend to try it.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#34

Post by ricardobeat »

ggregoire wrote: post #21
ferdowsi wrote: post #4

Congratulations to the Vue team, this is definitely a big win for them. Reading through the RFC is really interesting. They specifically call out the dependency on Facebook as effectively being React's Single Point of Failure, citing their negative experiences with HHVM. And for all of the love that people give React's big shifts (like hooks), the RFC specifically counts this against them, given that best practices h…

Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I've been using React on a daily basis for 5 years). Oh boy I was wrong. Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially wh…

I've been through two large-scale projects now where we went 100% into hooks, and after a couple years the excitement has faded and I often wonder if it was worth it. It seems to end up making code even more complex than before, even though components look simpler on the surface. Not enough to go back to classes, but doesn't feel as good as those first steps. I absolutely hate the manual dependency tracking and having every single thing be wrapped in a useX() method to avoid unnecessary updates.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#35

Post by nanagojo »

ggregoire wrote: post #21
ferdowsi wrote: post #4

Congratulations to the Vue team, this is definitely a big win for them. Reading through the RFC is really interesting. They specifically call out the dependency on Facebook as effectively being React's Single Point of Failure, citing their negative experiences with HHVM. And for all of the love that people give React's big shifts (like hooks), the RFC specifically counts this against them, given that best practices h…

Although I understand what you saying about big shifts and kinda shared your opinion, specially about hooks, I started a new project from scratch last week and decided to give hooks a try (and, for reference, I've been using React on a daily basis for 5 years). Oh boy I was wrong. Hooks are way more easier and intuitive than what I thought. It makes code so much more readable and easier to reason about. Especially wh…

IMO it is good that the React team was open into investigating different paradigms. It's a good thing and you rarely see this with other big projects.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#37

Post by avaldes »

paulddraper wrote: post #32
qmmmur wrote: post #26

Not even a consideration of svelte?

Svelte is very new (a year and half of meaningful adoption). React, Angular, Vue.js are the most popular, in that order. I hate to say might=right, but for a project like Wikimedia, choosing a mature, popular framework is important.

What happened to emberjs? It was poised to become the next big thing after react and angular and suddenly nobody talks about it anymore.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#38

Post by avaldes »

codefreakxff wrote: post #20
huuggjkkkk wrote: post #17

Good luck getting any libraries working. Good luck using graphql. Good luck getting the tooling stable. Good luck getting a PR on the main code base done. Vue in production is a minefield of nightmares. Rather have Facebook as a single point of failure than some random dude who has other things that consume his interest.

Are you trolling? I’ve used Vue in a couple of projects and honestly have no idea what you are talking about. Feel free to expand on your statements. Otherwise this message doesn’t fit in hn

The shift to Vue3 and a new paradigm (composition API) left the community in a state of confusion of where/how/when to migrate. The old paradigm is still supported but more like a legacy layer than the way to go. It reminds me of the python 2-3 schism.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#39

Post by finiteseries »

avaldes wrote: post #37
paulddraper wrote: post #32

Earlier quoted context omitted.

Svelte is very new (a year and half of meaningful adoption). React, Angular, Vue.js are the most popular, in that order. I hate to say might=right, but for a project like Wikimedia, choosing a mature, popular framework is important.

What happened to emberjs? It was poised to become the next big thing after react and angular and suddenly nobody talks about it anymore.

It’s still around a bit.

It was a hulking, omakase, MVC? based framework at a time when the oppo was Angular 2.0 & Backbone.js and people still used Bower, then React threw everything on its head in favor of component libraries while NPM came into the mix.

They eventually refactored in components and I think repackaged everything for the new js fe ecosystem, but the battle was already lost.

Re: Vue.js is Wikimedia Foundation's future JavaScript framework

#40

Post by lifthrasiir »

qmmmur wrote: post #26

Not even a consideration of svelte?

It was considered [1]:

> Svelte, Inferno, and Preact are aggressively optimized for performance but have much smaller communities of users (Preact suffers from this issue to a lesser extent, but only as long as it maintains a very high level of compatibility with mainstream React, which may not be the case forever).

[1] https://phabricator.wikimedia.org/T241180

Post reply on HN