lol

lol , 9 days ago (edited 9 days ago)

What? App developers are scientists now?

It does indeed sound like a typical misleading PR statement, made intentionally vague by not specifying who “we” is even supposed to refer to exactly in this context. But to be fair, although it is kind of implied, it doesn’t explicitly claim that those scientists are actively working on Proton as software developers (or anything really).

I know this originally came from CERN, but I find it hard to believe those same folks are working on this now.

As far as I can tell only two of the three founders that “met at CERN” (the about page doesn’t say they worked there as scientists) still work at the company: the CEO Andy Yen and Jason Stockman who does apparently work on the UI and websites, although I’m not sure if the latter is actually a “scientist”. The last co-founder Wei Sun worked at CERN as a student, but left the company already back in 2014.

lol , 14 days ago (edited 14 days ago)

I think the name is badly chosen. If it becomes more popular, it will likely be confused by many with youtube-dl, which is already commonly abbreviated as yt-dl or just ytdl (the official website used to be yt-dl.org and can now be found at ytdl-org.github.io/youtube-dl). This makes it unnecessarily difficult to find the project itself and potentially helpful related resources using a web search.

Why not use a more descriptive name like e.g. yt-dlp-wrapper or yt-dlp-simple instead? Unlike plain ytdl, a name like that would even give prospective users a hint about what to expect without needing to read any explanations as to how exactly your project differs from youtube-dl/yt-dl and yt-dlp.

lol , 14 days ago

I think when you rename a project on GitHub, all links to the old repository (including issues, wiki etc.) will be redirected to the new name, so it shouldn’t cause any issues, if that’s what you’re worried about.

IMHO, keeping the executable name as it is doesn’t make much sense, especially if you’re going to rename everything else and the plan is to alias it anyway.

I’m always annoyed when I install some-cli-tool and then have to go on a hunt because the binary isn’t also called some-cli-tool, but sc-t or something. I’d be doubly annoyed if sc-t was actually a wrapper for scd-t and both of them now lived in my PATH, meaning I’d now have to always remember which cryptic name is the one I actually want.