Honestly I just hate having fingerprints on a screen. And I use pageup/pagedown mostly which to me is better than scrolling.
Trackpad is nice for a device you can lay flat on a table or keep on one hand while sitting on the sofa, not too much when the device has a keyboard permanently attached to it and it cannot fold. I know I have a thinkpad like that and I never use the touchscreen.
Yesterday someone online told me I'm a boomer because (among the many other issues I mentioned) I said that apple computers lack page up/down keys which is annoying.
Two keys rather than one, but makes up for it by not being way off in some oddball part of the keyboard. You can one-hand it pretty easily, since there's an "option" right next to the arrow keys.
As a stolid classic-era Thinkpad user I don't have a dog in this fight, but it seems to me that the strain of having to hold down another key as I scroll rapidly would get tiring rather quickly. Perhaps if there was a Cmd lock it would be fine.
While I understand the network effect of github for public project, I don't really understand why one would want to use it for private repos.
There are tons of git providers including free ones that include full gitlab/gitea/forgejo to get similar features to github and there is nothing more easy to self host or host on a vps with near zero maintenance.
Actions are bad, but they're free (to start) and just good enough that they're useful to set up something quick and dirty, and tempt you to try and scale it for a little while.
Which, as far as I found so far, means Forgejo. Haven't found any others. And even Forgejo Actions says that it's mostly the same as Github Actions syntax, meaning you still have to double-check that everything still works the same. It probably will, but if you don't know what the corner cases are then you have to double-check everything. Still, it's probably the best migration option if you rely on GHA.
How do people even on hacker news of all places conflate git with a code hosting platform all the time? Codeberg, GitHub or whatever are for tracking issues, running CI, hosting builds, and much more.
The idea that you shouldn't need a code hosting platform because git is decentralized is so out of place that it is genuinely puzzling how often it pops up.
They said they want to be able to rely on their git remote.
The people responding are saying "nah, an unreliable remote is fine because you can use other remotes" which doesn't address their problem. If Codeberg is unreliable, then why use it at all? Especially for CI, issues, and collab?
The person you’re replying to is saying that you can do everything outside of tracking issues, running CI, ... without a remote. Like all Git operations that are not about collaboration. (but there is always email)
Maybe a hard blocker if you are pair programming or collaborating every minute. Not really if you just have one hour to program solo.
The original intent of the authors is by now irrelevant. The current "point" of git is that it's the most used version control solution, with good tooling support from third parties. Nothing more. And most people prefer to use it in a centralised fashion.
That doesn't remove the fact that when people are working on the code, their local copy doesn't disappear after they pushed their commits and a local copy is still available.
Only exception is when people are using the code editor embedded in the "forge" but this is usually an exceptional use rather than the norm.
> That doesn't remove the fact that when people are working on the code, their local copy doesn't disappear after they pushed their commits and a local copy is still available.
It doesn't remove it but doesn't make it very relevant either, because of all the tests that are necessarily done remotely and can't be done locally, and without that feedback in many cases development is not possible.
Yes! I was racking my brain trying to remember what it was called. Back in the early 2000s I ran BeOS on my desktop and absolutely loved it. Then when they went under, I followed the effort to come up with an open source version with guest interest. There was one effort that wanted to build everything from scratch. That's what was later renamed into Haiku (I think initially openBeOS maybe?). There was also BlueEyedOS who thought you could get there faster by building on Linux and X11.
I think Haiku got more traction because at the time people felt that it should run BeOS software without recompiling. I have long wondered what would have happened if BlueEyedOS would have gotten most of the effort.
Trackpad is nice for a device you can lay flat on a table or keep on one hand while sitting on the sofa, not too much when the device has a keyboard permanently attached to it and it cannot fold. I know I have a thinkpad like that and I never use the touchscreen.
reply