I just can't get past how bad SourceHut's UI is. They really need to hire someone that knows some basic UI principles. Edit: As a commenter suggested, I will elaborate a little: I'm a big fan of minimalist and lightweight UIs, that's not my issue with SourceHut's design. My issue is the disregard for several established UI principles (balance, proportion, repetition, etc.). Some examples: - The login[0] and register[…
Considering Sourcehut
71–80 of 81 posts
Re: Considering Sourcehut
#72Re: Considering Sourcehut
#73I'm surprised I never really hear people talk about GNU's Savannah. I've never hosted a project there, but it seems like a good fit for a GPL'd project https://savannah.nongnu.org/
>Projects running on Replicant may be hosted on Savannah. Projects having dependencies on nonfree software, such as proprietary software drivers or AndroidOS, are not permissible.
Re: Considering Sourcehut
#74Earlier quoted context omitted.
The issue is most users do not have the infrastructure to let others pull directly from their repositories, hence centralized hosts became popular.
Well, no, that's putting the cart before the horse. Git was not designed for remote fetching from every menial contributor. Nothing was—it didn't make sense to.* The idea with git-pull is that it's for use among a set of frequent collaborators—so for a given repo you have a handful of remotes, if any. It was not intended that everyone would need "infrastructure to let others pull directly from their repositories". Th…
Surely it would be a million times more intuitive for forges to offer a "submit a patch to this project" feature?
Re: Considering Sourcehut
#75I'm surprised I never really hear people talk about GNU's Savannah. I've never hosted a project there, but it seems like a good fit for a GPL'd project https://savannah.nongnu.org/
Does Postmarket meet the requirements? I could be wrong, but I thought Postmarket used non free firmware? >Projects running on Replicant may be hosted on Savannah. Projects having dependencies on nonfree software, such as proprietary software drivers or AndroidOS, are not permissible.
Re: Considering Sourcehut
#76I just can't get past how bad SourceHut's UI is. They really need to hire someone that knows some basic UI principles. Edit: As a commenter suggested, I will elaborate a little: I'm a big fan of minimalist and lightweight UIs, that's not my issue with SourceHut's design. My issue is the disregard for several established UI principles (balance, proportion, repetition, etc.). Some examples: - The login[0] and register[…
While I get how the first line of your comment could come across dismissive in isolation (and I guess that was the entire comment before the Edit - so I understand the downvotes in that context), there's a common reply in sibling comments here that bothers me much much more: > "bloated Javascript" > "pointless javascript" > "javascript-free UIs" I don't know how much people have worked in UI and with front-end code (…
That's why people were mentioning JS. If you've worked on frontend UI then you can't tell me you don't know what I'm talking about.
(And yes, I know it can be done with just CSS instead of moving an absolutely-positioned header with JS in scroll events. Tell that to the websites that do it, not to me.)
Re: Considering Sourcehut
#77Earlier quoted context omitted.
Well, no, that's putting the cart before the horse. Git was not designed for remote fetching from every menial contributor. Nothing was—it didn't make sense to.* The idea with git-pull is that it's for use among a set of frequent collaborators—so for a given repo you have a handful of remotes, if any. It was not intended that everyone would need "infrastructure to let others pull directly from their repositories". Th…
What are you talking about? git request-pull came far before GitHub existed, and that sends an email for a request & instructions to pull from a remote branch.
What are you talking about? (The general tone suggests that you're refuting something about my comment. What part are you trying to refute?)
Re: Considering Sourcehut
#78Earlier quoted context omitted.
Well, no, that's putting the cart before the horse. Git was not designed for remote fetching from every menial contributor. Nothing was—it didn't make sense to.* The idea with git-pull is that it's for use among a set of frequent collaborators—so for a given repo you have a handful of remotes, if any. It was not intended that everyone would need "infrastructure to let others pull directly from their repositories". Th…
It is truly weird to me that the standard workflow for submitting a change to someone's project is now to make a copy of their project, change it, and then ask them to import your change. This is inside-out and upside-down! Surely it would be a million times more intuitive for forges to offer a "submit a patch to this project" feature?
Re: Considering Sourcehut
#79Earlier quoted context omitted.
While I get how the first line of your comment could come across dismissive in isolation (and I guess that was the entire comment before the Edit - so I understand the downvotes in that context), there's a common reply in sibling comments here that bothers me much much more: > "bloated Javascript" > "pointless javascript" > "javascript-free UIs" I don't know how much people have worked in UI and with front-end code (…
The kind of whizzbangs associated with "beautiful UI" often involves copious amounts of JavaScript hijacking scroll events, running code for every pixel of a mouse move, and so on. Something as simple as "header in the middle of the page" can involve an absolutely-positioned header moved around on scroll events. That's why people were mentioning JS. If you've worked on frontend UI then you can't tell me you don't kno…
Noone was talking about whizzbangs here, least of all the gp.
Re: Considering Sourcehut
#80I'm surprised I never really hear people talk about GNU's Savannah. I've never hosted a project there, but it seems like a good fit for a GPL'd project https://savannah.nongnu.org/