Re:Rx – Extensible pixel editor implemented in Rust, inspire...
by johnisgood on Monday September 30, 2019 @11:27AM
(#21116353)
> 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
Re:Rx – Extensible pixel editor implemented in Rust, inspire...
by nonconvergent on Monday September 30, 2019 @12:48PM
(#21117261)
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
Re:Rx – Extensible pixel editor implemented in Rust, inspire...
by Waterluvian on Monday September 30, 2019 @01:33PM
(#21117723)
I'm surprised it didn't come up with Scoopr.
Re:Rx – Extensible pixel editor implemented in Rust, inspire...
by mlevental on Monday September 30, 2019 @10:56AM
(#21116006)
>probably "rx rust pixel"
Re:Rx – Extensible pixel editor implemented in Rust, inspire...
by nonconvergent on Monday September 30, 2019 @12:55PM
(#21117328)
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.
Plus first result for "rx rust" lead me to https://github.com/ReactiveX/RxRust