The forks could just change their name, so they're more easily found. For example mRemote got pretty much abandoned, so mRemoteNG got created.
Or people give forks better names. For example, I've forked some dotnet6 project, and called the fork {project}-dotnet8 - then when people look thought the fork list on github, it's not 20 forks all with the same name
It's not even the "quality of the project" like suggested in this thread. It's the quality of the commit messages (meta-data, documentation)
That's like someone who paints for a hobby, and shows their paints off on the internet, and people would post stuff like "Well cool painting, but you didn't really explain what kind of paint you've used, who your inspirations were" etc etc
When I'm building Open Source stuff as a hobby for things that are useful to me, and also dump them on Github - because it's a good backup system - I don't really care whether people might go through the commit history as means to figure out how I've build it
Well "Device based" is even more broad, haha. If you're also including iOS and Android.
Then you'd be looking at a cross-platform developing lanuage, like Flutter, React Native, Xamarin etc.
So the question is, what is the goal for your GUI? Is this a personal project where you just want to have a GUI for a specific system? (Windows / iOS system) - Or something published that you want people to be able to use on all devices?
It's been a while since I did something like this, but I think you can do it though Google Play Install Referrer API.
I assume you'd have a "Download App" button on the landing page, then you'd append a userId to the download url.
I think this explains it: https://developers.google.com/analytics/devguides/collection/android/v4/campaigns
Now as for the “Java bad”, I’m kind of guilty of it too. I very much dislike how academia is obsessed with UML diagrams.
I'm kind of guilty of that too - in mindset - I just don't go around and shitpost about Java.
My dislike for Java also came from academia, since I had to use it in school. Though my main problem was just the general tool chain of Java. Like we had to use Eclipse or NetBeans. And then we had to write stuff in "JavaBeans" When instead of a normal "Person" class, you'd have to have a "PersonBean" and everything was so weird. And all the packages and references would constantly break or be missing, both in the project and even in the IDE itself...
After moving to C# and using Visual Studio, NetBeans just feels like you're trying to build a house with a rock instead of hammer, on an already crooked foundation.
Though that was a long time ago. I assume things have improved. But I never really had any reason to go back to Java
When you said "GUI Programming" What kind of GUI are you talking about? A web-based GUI or a desktop-based GUI?
Web-based the go to framework is generally React or Angular.
If you're talking about Desktop based, you probably want to stick with the language that you're also building the logic in. Like you could use another language like C# and write a front-end in Avalonia, but then you'd have to interlop from C# to Python.
You could also pick a language that's supported by Electron, then you'd basically be doing Web-Development but for desktop.
Well Lemmy is Rust - Plus Lemmy is already an alternative for Reddit, so all the "normies" are still on Reddit - So Lemmy itself is already a bit of a niche sample size.
Rust developers are already known (/memed) to be elitist about Rust - and "Java is Bad" is also just the general consensus among developers, especially ones using more niche languages
There's a user made OpenAPI spec: https://github.com/MV-GH/lemmy_openapi_spec - You probably mean that one
I've had similar issues as you mentioned that the dev did fix - but yea, Typescript has less precision than Rust (the source) or the openapi spec. And the Typescript client is build for Lemmy-JS and not build an example for other language client libraries...
Though the OpenAPI Documents in C# and Java are based on reflection of the source itself, and Rust doesn't have Reflection like that... So it's probably difficult for them to add without manually maintaining the OpenAPI specs
About 4 ~ 12 a day, though roughly about 50 ~ 60 hours a week.
A 4 hour day would be if I have some problem that I know has a good implementation, but I just can't figure out how to do it. Then it's better to just stop and do something unrelated.
Though then once the problem is solved and all the puzzle pieces fall together - and I can just work on implementing it, and refactoring it into a good solution - I can continue working on it without caring about the time.
But I don't have a lot of days where at the end of the day I'm like "Yess, I'm finally done working, now I can start doing something fun!" - The working itself is already fun, so that creates a different "Working vs Not Working/Having Fun" dynamic
23 and Me are technically correct in that it’s customer behaviour that caused the issue.
Maybe I don't really understand what happened, but it sounds like 2 different things happened:
The hackers initially got access to around 14,000 accounts using previously compromised login credentials, but they then used a feature of 23andMe to gain access to almost half of the company’s user base, or about 7 million accounts
14k accounts were compromised due to poor passwords and password re-use -
And then they got access to 7 million accounts. Where did that 7 million account breach come from? Were those 7 million connections of the 14k or something? Because I don't think your connections can see many in-dept details
PaaS takes away your flexibility: [...] sometimes, you also want to use the compute to run cron jobs, run background jobs, or host a small service. With PaaS, you don’t have the flexibility to do so. [...]
I don't really agree with that. I'm using AWS for that, and for my "small cron jobs" I simply create a lambda for them. Then you can create a CRON rule in Event Bridge and schedule the lambda to start whenever you need
If you have a C# project that I can help with, as you mentioned, would be cool. I don't have that much experience with Rust, besides getting the Lemmy backend to compile.
I have experience working on the Lemmy APIs; I was trying to make my own front-end lol: https://blamm.it (Because mlmym requires a running Go Backend Proxy, to proxy requests between the Front-end -> Go Backend -> Lemmy Backend) - (which could easily be running maliciously, since you can't verify the hosted Go Backend isn't modified to log requests or something) - (And it's slow)
Hosting wise I have loads of experience with AWS... though not sure where you're hosting