Jellyfin
this post was submitted on 30 Jan 2024
69 points (100.0% liked)
Programmer Humor
35579 readers
184 users here now
Post funny things about programming here! (Or just rant about your favourite programming language.)
Rules:
- Posts must be relevant to programming, programmers, or computer science.
- No NSFW content.
- Jokes must be in good taste. No hate speech, bigotry, etc.
founded 5 years ago
MODERATORS
The unmaintained repo has a link in the readme pointing to the best fork
load more comments
(10 replies)
yo but tbh this gets old.
i just want my stuff to update without me having to find out a year later its unmantained and had a fork all along.
or having to watch the repositories of stuff i use for signs it might be unmantained.
libforknotifier when (or even how)?
load more comments
(5 replies)
Even better when someone forked it away from proprietary, closed-source, publicly-traded, for-profit, US-based, account-required, training-AI-on-your-code-then-selling-it-back-to-you Microsoft GitHub forge/social media network often with vendor lock-in to some other forge without all that BS.
load more comments
(8 replies)
Me with Liftoff :)
Is there a fork being maintained? I haven't seen one. Was just poking around for one yesterday.
Liftoff is no longer maintained right? So what's the fork?
gqview -> geeqie
Neolink
Hyperion -> HyperHDR
Slic3r -> PrusaSlicer -> SuperSlicer
Although I'd love to agree superslicer has sadly nowhere near the development power of prusa behind them - and feature parity is rarely given, basically any release of the two has "oh I want both of those!" (don't know if it's spelled correctly but arachnid mode for example was hyped to a point I checked back with prusa after a few months).
I just want to point it out in case people expect a "prusaslicer" but better in every regard :)
If this is the case, why doesnt superslicer upstream its changes to prusaslicer? :/
I can't answer that and it's a valid question in my opinion. If I had to guess I'd speculate about disagreements in code style, build pipeline or similar.
load more comments
(1 replies)
Oh yeah, I find that it's easier to get fine control of the outcome in SuperSlicer because it's less refined. User-friendly features are nice when you're getting started but a hindrance when you have more experience. I tried to use Cura awhile back and it felt like the Fisher-Price version of a slicer. SuperSlicer is probably less accessible overall, but it doesn't hide controls from me.
I will borrow The fisher-Price phrasing, thank you for that! Fully agree on the cura part.
Simplemobiletools --> Fossify is pretty epic
Do the Fossify versions already have new features? I'll still using Simple Mobile Tools from F-Droid, without ads, and am asking if it makes sense to download Fossify apps already
load more comments
(8 replies)
Gitea -> Forgejo, e.g.
I want to like Forgejo but the name is really terrible.
Is it "forj-joe"? Nah, that double-J sound is way too awkward.
Do you then merge the J sounds to make "forjo"? If so, why not just call it that?
Is it maybe "for-geh-joe"? That seems the most likely to me, but then that ignores the "build < forge" marketing on their website.
I know it's pretty inconsequential, but it feels weird using a tool that you don't even know how to pronounce the name of.
Yeah, like the other person mentioned, the origins of the word and its pronunciation are the very first thing in the FAQ on their website. It's pronounced more like for-jey-oh.
load more comments
(1 replies)
There is an official pronounce on the site. It comes from Esperanto anyway.
load more comments
(2 replies)
What happened to gitea?
afaik it got bought by some company and people fear that there will be anti-user changes like with all the other open source projects that were bought by a company in recent years.
Ah ok
load more comments
(3 replies)
Is that really the case? I selfhost gitea and am pretty happy with it.
They’re both pretty on par for the most part. If it’s too much of a hassle, there’s no real need to switch.
Now that Gitea is owned by a for-profit company, people are afraid that they’ll be making anti-user changes. This, Forgejo was born. It pulls from Gitea weekly, so it’s not missing anything. It’s also got some of its own features on top, but they’re currently pretty minor. Also, most of the features end up getting backported back to Gitea, so they’re mostly on par with each other. However, many features find themselves in Forgejo first, as they don’t have the copyright assignment for code that Gitea does. Additionally, security vulnerabilities tend to get fixed faster on Forgejo. They are working on federation plans, however, so we’ll see how that pans out.
Overall, there’s no downside of switching to Forgejo, and you’ll probably be protected if Gitea Ltd. makes some stupid decisions in the future. However, at the moment, there’s no immediate advantage to switching, so you can stick with Gitea if you’d like.
load more comments
(2 replies)
Gitea is still maintained though?
They got bought so people jumped ship, I haven’t heard anything bad personally
Yes as you say, I think they're still pretty fine, though I do prefer Codeberg as a hosted solution myself and in turn Forgejo, especially for their federation plans
load more comments
(3 replies)
Yeah Fogejo is amazing. Moved all my personal projects from GitLab to Codeberg recently. Wish I knew about it sooner
vi?
vim, or better yet, neovim
come to the 21st century, we have lua
and plugins, and syntax highlighting, and multi buffer/multi window support, and LSP support so you can Go to Definition like in an IDE, and wAY more normal mode commands than anyone could ever hope to memorize. also when you do cw it deletes the word immediately instead of putting a dollar sign at the end before purring you in insert mode, and regex substitutions highlights text in the buffer as you type so you can see what you're about to replace. it's really quite cool. if you're new to programming and/or feel like committing heresy you can even skin it to look and work like VS Code. people like to joke that we're slowly but surely becoming emacs and they're not entirely wrong.
but the important thing is the lua.
Used vim since the mid 90’s, but switched to emacs at some point. It was wonderful for many years, but neovim has come so far that I switched back a few years ago. Could not be happier. The tools available for programmers these days are superb and neovim chief among them.
It's probably because of Lua that the plugin ecosystem exploded in the recent years.
I'm glad I adopted neovim early.
load more comments
(2 replies)
rimusic
it's a wonderful feeling when that happens!
I don't usually get my hopes up, but yes, it is a wonderfull felling when it happens.