3 ms·

I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.

by ergo14 9y ago

baybal2 9y ago
I like it, a mirror opposite of extreme "designed by committee" practices of big co. funded frameworks. I feel purposefulness of Vue's design. There are no gigatons of features and behaviors which make you scratch your head and think "why it is there to begin with" like why Ang2 insists on using observer objects for HTTP responses, or why Ang1 had a such an extensive buildover around its component zoo to do just "new mySerice", or reasons for React's component rendering order peculiarities, or logic behind their choice of syntax. Vue is very bare bones thing. It provides no reactive layer over complex object with non-primitive content. Lack of native support for maps or sets from ES6 is inconvenient a bit, but it is not hard to provide a function wrapper around any logic that uses them. I usually keep all business logic outside of Vue's instance and only wire though its inputs and outputs. What I lack in all common frameworks is the ability to play smoothly with really complex DOM manipulations, like swapping prototypes of a DOM elements and mergings. Trying to do something like complex drag and drop logic usually means doing a lot of "do it within DOM element, or do it within framework's element" thinking
- wooptoo 9y ago
  ES6 actually supports both Sets and Maps: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
  - baybal2 9y ago
    I mean Vue does not work well with them. If you set a data value to be a Map, vue will not be able to track changes to it
- ergo14 9y ago
  I'm not talking about the API design, I'm more worried what happens if Evan dies, or just loses interest in it. Bus factor of 1.
  - deleted 9y ago
    [deleted]
  - fencepost 9y ago
    There may or may not be a large number of people who have the same kind of grasp of the codebase, but because it's so much a single person project it's probably more viable for someone to fork it to a new maintained project in case of disaster.
  - super-serial 9y ago
    What happened to jQuery when John Resig focused on other things? I'm actually hoping Vue.js builds everything needed for a Reactive minimalist framework and then development slows down similar to the speed of jQuery. I think people are sick of frameworks doing overhauls of their entire codebases every major version release.

I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.

by ergo14 9y ago

I like Vue, but one thing that worries me is that 99% of commits are being made by a single person.

I like it, a mirror opposite of extreme "designed by committee" practices of big co. funded frameworks. I feel purposefulness of Vue's design. There are no gigatons of features and behaviors which make you scratch your head and think "why it is there to begin with" like why Ang2 insists on using observer objects for HTTP responses, or why Ang1 had a such an extensive buildover around its component zoo to do just "new mySerice", or reasons for React's component rendering order peculiarities, or logic behind their choice of syntax. Vue is very bare bones thing. It provides no reactive layer over complex object with non-primitive content. Lack of native support for maps or sets from ES6 is inconvenient a bit, but it is not hard to provide a function wrapper around any logic that uses them. I usually keep all business logic outside of Vue's instance and only wire though its inputs and outputs. What I lack in all common frameworks is the ability to play smoothly with really complex DOM manipulations, like swapping prototypes of a DOM elements and mergings. Trying to do something like complex drag and drop logic usually means doing a lot of "do it within DOM element, or do it within framework's element" thinking

wooptoo 9y ago
ES6 actually supports both Sets and Maps: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Set https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe... https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Map https://developer.mozilla.org/en-US/docs/Web/JavaScript/Refe...
- baybal2 9y ago
  I mean Vue does not work well with them. If you set a data value to be a Map, vue will not be able to track changes to it
ergo14 9y ago
I'm not talking about the API design, I'm more worried what happens if Evan dies, or just loses interest in it. Bus factor of 1.
- deleted 9y ago
  [deleted]
- fencepost 9y ago
  There may or may not be a large number of people who have the same kind of grasp of the codebase, but because it's so much a single person project it's probably more viable for someone to fork it to a new maintained project in case of disaster.
- super-serial 9y ago
  What happened to jQuery when John Resig focused on other things? I'm actually hoping Vue.js builds everything needed for a Reactive minimalist framework and then development slows down similar to the speed of jQuery. I think people are sick of frameworks doing overhauls of their entire codebases every major version release.