It's on my radar and I'm sure it's on a number of other people's as well. It just takes a little onboarding time like all good projects.
this post was submitted on 15 Jun 2023
177 points (100.0% liked)
Programming
423 readers
3 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
the ui is in inferno js
I haven't used Inferno but it looks similar to React. Is knowledge of React transferrable to Inferno or should I spent a bit of time learning Inferno specifically? I've got ~10 years React experience (started using it the same year it was open-sourced).
I haven't messed with it much, but they do offer a high-level diff list about midway down the home page: https://www.infernojs.org/
It's also on my "wishlist" for contribution. I'm learning Rust but didn't know what project to bring the skill to practice.
Finally some good distractions for my Saturdays!
Maybe that is the problem, rust, not a popular choice for web development.
The backend is rust! The frontend is typescript with a react-type framework. So feel free to pitch in on the frontend if you are familiar with TS!
Relax my friend, would you like some Mojito? You see that doesn't take rust out of the equation here (read again the op body text).
It's difficult problem to solve. Lemmy's stack is a bit unconventional. The rust backend is not idiomatic and the ui is based off a template of an isomorphic not-quite-react framework. Its not impossible, but it will take a while for alot of programmers come onboard.
That being said, there's more to it than writing code. Better bug reports, reproduction, updating docs and triaging/managing the issues is possibly more important than writing PRs. Don't be discouraged!
Would it make more sense to just go all in on API support for the main codebase and leave UI up to 3rd parties/separate project? Seems like that would be the ultimate anti Reddit at least
So the backend is coded in Rust? I've been learning the language but haven't actually used it outside of tutorials yet. I'm experienced in C++ and know how to program so I may look into it while I'm unemployed.
I crossposted to the Rust Lang community here on Lemmy as well.
It may be worth posting on some Rust forums too.
I will be working on this when I get cycles. Barring the issues already above, there are a lot of areas for optimizations, for instance how images are handled (i.e., they can be handled through object storage like Cloudflare R2 to decrease bandwidth/ram costs). Some is more dev-ops on how common instances are setup, others are code changes to make things more efficient.
Perhaps we should start a community or communication group for this?
The dev group is on matrix
Do you have a link?
I'm thinking that kbin might pick up speed since it's PHP, and the code base seems quite well organised.
Yeah, I'm looking to jump to Kbin when I can, but right now it looks like a lot of the instances are having major federation issues, which makes it a bit untenable.
What kind of issues?
Quite a few instances just aren't populating posts on other instances. I suspect this is due to ddos protections large instances have had to put in place during this high load period.
What about trying to contact rust devs from outside the fediverse/lemmy community? Maybe some of them don't know about the lemmy project, but they'll find it interesting and join the dev team.