[midrus]

To me this is just the conflict of interest just kicking in. Next is not built as rails, Django, Vue, etc... Next is a part of their business.

Don't believe it? Just look at the telemetry "feature". Try to disable it...something that should be just a config in next.config.js is a convoluted trap which will only disable it on your machine and you need to remember to disable it everywhere, etc...

As with Facebook (well, not that bad, but still...).Next isn't free.

[randomchars]

https://nextjs.org/telemetry

What's the catch here? You can opt out if set an environment variable. You can surely do that on CI as well, if that's your concern.

[midrus]

The catch is that this is intentionally made inconvenient. If it were a config setting I could just put it there,commit, and forget about it.

By making me setting an environment variable you are forcing me to remember to set it up in my infrastructure, on each environment, on each developer laptop, for each project independently, and if my project is open source, good luck with any user remembering/caring to set the env var.

And this is pretty intentional so that people forget or just don't care to disable it.

That's the catch.

https://github.com/vercel/next.js/issues/8851

[randomchars]

Next supports loading env variables from files, and as far as I can see, telemetry respects this. Add this line to a `.env` file, and it's done.