Only if they have a 100% tax rate, which I doubt.

The GNU project emerged from academics, which don’t get paid for their software in general, they get paid for writing papers about it. So, they want to stop all commercial use of their software.

The Rust project emerged from the startup culture, where everything is just a stepping stone to eventually get sold in some kind of software project to get rich. So, being able to use the software in a commercial setting is essential.

I think prototypes are fine to answer specific questions. However, I think it’s often the case that management doesn’t understand what a prototype is and thinks that this is just the alpha release of the real product.

Rule of thumb: if you don’t throw away all of the code after having answered that question you were writing it for, it’s not a prototype.

For prototyping, if you don’t already know Rust, it’s probably not worth it.

When you really know Rust it’s IMO easier to write a web server in Rust than node, but there is a long road to getting to that level.

Well, CLI tools fall under that category, and they’re not exactly rare to be written in Rust these days.

My most recent one had to use tokio anyways due to a library crate that used it (rtnetlink). Luckily, I don’t mind that at all.

https://github.com/fish-shell/fish-shell

For Linux, here is the spec: https://specifications.freedesktop.org/basedir-spec/basedir-spec-0.6.html

macOS has the NSSearchPathForDirectoriesInDomains API.

For Windows, there’s also an API for that, but I don’t know it offhand.

I’m fairly hesitant to call something that doesn’t sell anything a “store”.

Yeah, I didn’t refer to those. Google’s and Microsoft’s store have the same issue probably, though.

Here’s the explanation: https://www.fsf.org/news/2010-05-app-store-compliance

The GPL is also incompatible with modern appstores, which makes them less valuable. I personally don’t touch anything GPL for work, only for hobby projects.