4 ms·

> Not to mention when the devs themselves get bored with tool X they've created and jump to creating some newer tool Y, dropping the whole community... Given t

by hk__2 9y ago

> Not to mention when the devs themselves get bored with tool X they've created and jump to creating some newer tool Y, dropping the whole community... Given that you don’t pay for the product I don’t see anything wrong here. People work on what they want then change if they’re bored; you can’t do anything about that but pay them to continue supporting the tool you decided to use.

brucephillips 9y ago
> you can’t do anything about that You can. You can encourage developers to contribute to a single project, rather than create fragmentation, which is exactly what's happening in this forum.
- hk__2 9y ago
  Yes, you can. But you can’t force them if they don’t want it.
  - brucephillips 9y ago
    K. Who's forcing anyone?
    - hk__2 9y ago
      Nobody’s forcing anyone but a lot of people including the parent comment complain when someone doesn’t want to work for free on the tool they use. Encourage people if you want, but don’t complain if they don’t listen.
      - brucephillips 9y ago
        By all means, do. People complain about things that make their lives worse, especially when it's avoidable, as it is in this case. There's nothing wrong with that.
- ricardobeat 9y ago
  Webpack doesn't seem to have a shortage of contributions. What is your real concern?
  - brucephillips 9y ago
    1) A fragmentation of targets for complementary products. Any tool that must integrate with bundlers now has one more target. 2) A fragmentation of development efforts across competing projects. Webpack has many contributors, but they'd have 1 more if the author of Parcel built parallelism into Webpack instead of a new bundler.
pbreit 9y ago
You can encourage them to instead work on improvements to existing tools.
coldtea 9y ago
>Given that you don’t pay for the product I don’t see anything wrong here Things might not be wrong and still be a problem. E.g. your neighbor practicing tuba (badly) during the whole day, in perfectly legal hours... In fact someone can gift stuff with the best intentions, and still cause a problem.

by hk__2 9y ago

brucephillips 9y ago

> you can’t do anything about that You can. You can encourage developers to contribute to a single project, rather than create fragmentation, which is exactly what's happening in this forum.

hk__2 9y ago
Yes, you can. But you can’t force them if they don’t want it.
- brucephillips 9y ago
  K. Who's forcing anyone?
  - hk__2 9y ago
    Nobody’s forcing anyone but a lot of people including the parent comment complain when someone doesn’t want to work for free on the tool they use. Encourage people if you want, but don’t complain if they don’t listen.
    - brucephillips 9y ago
      By all means, do. People complain about things that make their lives worse, especially when it's avoidable, as it is in this case. There's nothing wrong with that.
ricardobeat 9y ago
Webpack doesn't seem to have a shortage of contributions. What is your real concern?
- brucephillips 9y ago
  1) A fragmentation of targets for complementary products. Any tool that must integrate with bundlers now has one more target. 2) A fragmentation of development efforts across competing projects. Webpack has many contributors, but they'd have 1 more if the author of Parcel built parallelism into Webpack instead of a new bundler.

pbreit 9y ago

You can encourage them to instead work on improvements to existing tools.

coldtea 9y ago

>Given that you don’t pay for the product I don’t see anything wrong here Things might not be wrong and still be a problem. E.g. your neighbor practicing tuba (badly) during the whole day, in perfectly legal hours... In fact someone can gift stuff with the best intentions, and still cause a problem.