Post An4FJB7fFABsTsjnSS by kly@fosstodon.org
 (DIR) More posts by kly@fosstodon.org
 (DIR) Post #An4FJB7fFABsTsjnSS by kly@fosstodon.org
       2024-10-16T13:57:56Z
       
       0 likes, 0 repeats
       
       Having the name of the programming language as an easily identifiable part of the application or project name is a big red flag.
       
 (DIR) Post #An4FJCU2BTg8hYDAxs by wolf480pl@mstdn.io
       2024-10-16T14:23:26Z
       
       0 likes, 0 repeats
       
       @kly hmn so likelibkafka-client-javaIs ok, since the project name is "kafka" and this is only part of itBut likeejabberdis a red flag because it's main selling point appers to be that unlike the original jabberd, it's written in erlang?
       
 (DIR) Post #An4FJDNgqYCLUAFciO by kly@fosstodon.org
       2024-10-16T14:46:19Z
       
       0 likes, 0 repeats
       
       @wolf480pl Kinda? I'm not claiming an absolute rule here. But stuff like "gopass" (of which there are TWO "unrelated" projects), where the only selling point is "it's compatible with pass, but written in go" (same selling point for both implementations) has me worried. Makes me think the point was to write something in a a specific language, not actually improve anything.
       
 (DIR) Post #An4FJEIlQLqsLAxCfw by wolf480pl@mstdn.io
       2024-10-16T14:57:57Z
       
       1 likes, 0 repeats
       
       @kly I think sometimes there are legit reasons to want sth written in a particular language, eg:- it's a library- the old language was obnoxious to deploy (eg. php, python with dependencies)- a certain runtime only allows this specific language (eg. JS in web browsers, PHP on a traditional web hosting)- the old project was stuck with irresolvable issues due to language limitations
       
 (DIR) Post #An4FJGyfTWYkdiZhGi by wolf480pl@mstdn.io
       2024-10-16T14:58:22Z
       
       0 likes, 0 repeats
       
       @kly but yeah definitely a warning sign to look into