This type of canned response doesn't sit well with me. Keep us posted when you're out of beta and those things are removed, do you have a timeline for that?
you need to realise is that if you don't do this "by tomorrow", the momentum will be lost and no HN'er will ever use your product, because they will forever associate it with tracking
This is already being brought up in multiple slack networks I'm on, with the general consensus being that these decisions make the company impossible to trust.
terminals are used by sysadmins/software developers/hackers
HN the most important resource in this category
their product has the hotspot
they should be fixing the telemetry ASAP (i'd suggest - before next release) or else their product will be forgotten for a while and next time it comes up everyone will be sceptical to upvote again
There are 1000s of developers who use the terminal for simple things like running dev workflows - git checkout, build, edit code, send a PR, etc. It seems wrap is trying automate things here to help these developers.
Just because there are plenty of bash wizards who don't like this, it doesn't mean this isn't useful.
There are still plenty of users who swear by Vim / Emacs. I've been a software engineer for 10 years at a FAANG and never use Vim to write code.
rust's rustup planned to add telemetry - they had a config for it (but never ended up doing so). It still affected me and how I viewed the program. These things stick around. I think they are safely without telemetry now (but they "obviously" ping home to look for updates).
You really should take people's advice in beta. Get rid of telemetry before tomorrow. If you don't this terminal will likely fail. It might be too late already.
