PS edit: this isn’t glib. I’m genuinely curious why, who and how this choice was made.
If you're intelligent enough to use screen, surely you're intelligent enough to understand the difference between a terminal app and an app that shares your screen.
Again, the number of people who this impacts is so small that it's hardly significant. Sure, here on HN I'm sure it seems that everyone is confused, but we're hardly a representative sample here.
> has trademark problems
Honestly I don't buy this. When you trademark something, you do so in a very specific manner, and I think Screen's market is specific enough as to defend a trademark in the screen sharing/collaboration segment _should they even choose to trademark the name_, which they can easily choose not to do.
Also, no one in our private beta ever raised this concern.
Screen just switched to public beta today, and the idea is for us to get feedback on issues we may not have seen before. This is a great example of such an issue! And as I’ve said elsewhere, if this continues to be an issue, we will change it. It’s not in our interest to have customer confusion either.
You support Linux (well!), I’m surprised your beta testers didn’t say anything. That’s an interesting problem —I wonder what other blind spots like this can be avoided.
Admittedly, we only had a handful of Linux users in our private beta, but still, none of them mentioned the GNU tool.
Just today I was recommending (GNU) screen to a coworker to address transient outages with a remote connection. It would get pretty annoying to constantly clarify which screen I mean, as they are both used in the same circumstances.
Don't get me wrong, I've got lots of colleagues who use various other editors, like vs code - but... This isn't just a case of pre-existing software with a similar name - combined with ssh, gnu screen is arguably superior for pair bugfixing in production, for example (multiple ppl can ssh into the same server).
I get that this is "like gnu screen, but for xorg/Wayland - and without any support for resuming remote sessions" - just sounds like an odd pitch - as you say you especially want to target Linux support...