I care. Also it's a potential legal issue for any given project if there's a registered trademark involved.

Plus first result for "rx rust" lead me to https://github.com/ReactiveX/RxRust

> Also it's a potential legal issue for any given project if there's a registered trademark involved.

At some point we will have to generate random strings for the name of our projects because all the "good" (or even "bad") ones are taken. :P

Already a thing: https://namelix.com/app/?keywords=poop+scoop

Highlights for a "poop+scoop" related startup include: Flingo, Trash.ly, Fastpoop, Stinkere, Guunk, and Spoop

I'm surprised it didn't come up with Scoopr.

>probably "rx rust pixel"

https://www.google.com/search?q=rx+rust+pixel&oq=rx+rust

Let's keep in mind that this is an end user application for pixel artwork. You and I might care that it's Rust. End Users will not. It could be written in Malbolge or BF for all an end user cares about.

Namespace collision is gonna be a pain for end users and newcomers, possibly depressing discovery, which is our point.

Why would you image an author would not care that their page "suck on mobile". If they are posting/sharing their stuff, they more than likely want people to consume (and spread/reshare it). Both being poor experience on mobile and non-discoverably, hard to search for impact that.

i'm sure the author cares. what i'm not sure about is that the author isn't aware and that "hey your site fails on mobile" is of much use to them.

I can easily imagine an author who rarely uses their own mobile page except to make sure that it works at all; or who knows it's not great, but doesn't realize just how annoying it is; or even who has never looked at their site on mobile, ever.