Next.js: Too many open issues to be taken seriously by enterprise

Created on 30 Oct 2017  路  13Comments  路  Source: vercel/next.js

Hello, big fan of Next.

But-- there are too many issues open for any big company to adapt to Next.

Can we close some of the issues? Also, can we close some of the PR's as well--limiting to around 15 open PR's max?

Yours truly,

Indrek

Most helpful comment

Personally I think is the opposite, a lot of issues means a lot of people using it or interested in a project. Check VSCode, they have more than 5000 issues, GH even show +5000 instead of the real amount!

image

All 13 comments

I also think we have many issues open but if you check they are more about doubts or feature requests than bugs.

Wow that was quick!

Yep indeed, everything is fine and I'm not blaming anyone. But imo it's kinda bad press to see this many open issues. This was the first thing popped in my mind when scanning the repo.

Some of these are more than a year old. https://github.com/zeit/next.js/issues?page=10&q=is%3Aissue+is%3Aopen

Indrek

Personally I think is the opposite, a lot of issues means a lot of people using it or interested in a project. Check VSCode, they have more than 5000 issues, GH even show +5000 instead of the real amount!

image

Fair point. 馃憤

I think this NextJS is too cool and advanced for Enterprise

@wesharehoodies Consider how active these issues and PRs are though.. (make sure you're "watch"ing the repo)

Also, many of the issues are feature requests, and many are "help me with this please", which are much more positive that bug reports.

we close some of the PR's as well--limiting to around 15 open PR's max?

It's not that simple. All open PRs are either things we still have to look into or things we have to work on to improve / expand 馃槃

But-- there are too many issues open for any big company to adapt to Next.

Like @sergiodxa mentioned most projects have at least 3 times more issues at this scale (almost 19K stars). Also note that github issues are an endless lifecycle which can't be tamed. There will always be issues popping up 馃槃. Most are feature requests like @mattbrunetti said.

I do agree that we should do a run through all issues to see if they're still relevant.

there are too many issues open for any big company to adapt to Next.

To expand on this. On the contrary to what you're saying we're seeing great adoption across many different types of companies, from startups to large enterprises. People are even creating ecommerce experiences using Next 馃挴

Some examples:

npm - https://www.npmjs.com/search?q=next
Open Collective - https://opencollective.com
Netflix - https://jobs.netflix.com
Scale API - https://scaleapi.com
Avocode - https://avocode.com/
Institchu - https://www.institchu.com/design/shirt
Nike - tba
Deliveroo - tba

A while ago, before the v2 release, I made a list in this issue: https://github.com/zeit/next.js/issues/1458

In light of closing issues, feel free to close this one if your question is answered 馃槃 馃檶

Anyone else enjoying the irony of this issue? 馃ぃ

Alright, fair ball play. Love you guys :heart:

Just joining to the conversion.

I think measuring the project by the number of open issues is hard (when deciding good or bad). In our case, we have a higher number of open issues because of the following reasons.

  • This is the only discussion forum other than Slack
  • We also manage issues for examples

Next.js is very crucial for us since we use it for our web app and for our Desktop client.

So, we are seriously serious about Next.js for sure :)

@wesharehoodies 鉂わ笍

This thread has been automatically locked because it has not had recent activity. Please open a new issue for related bugs and link to relevant comments in this thread.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

DvirSh picture DvirSh  路  3Comments

renatorib picture renatorib  路  3Comments

ghost picture ghost  路  3Comments

jesselee34 picture jesselee34  路  3Comments

knipferrc picture knipferrc  路  3Comments