Y
HN Search
Hacker News Search
new
|
comments
|
top
|
jobs
goku12
searching PlanetScale…
1.
▲
2.
▲
3.
▲
4.
▲
5.
▲
6.
▲
97 ms
·
1351.
▲
by
goku12
3y ago
These services have the following (non-exhaustive) list of problems: - They are hard to use for regular people due to lack of modern and intuitive clients. - They are somewhat hard to discover and learn. For example, browsers don't ind
1352.
▲
by
goku12
4y ago
The most populated country and the authorities still don't understand P2P, federation and multiple clients. What makes you believe that: - Element (the company) represents the entire federated network - Users can't access the netw
1353.
▲
by
goku12
4y ago
It could be argued that the worst thing that happened to ads are targeted ads. The targeting part manages to insert irrelevant ads at the most inappropriate times, even after invading users' activity across the web. Even simple non-tra
1354.
▲
by
goku12
4y ago
One of the biggest ways in which caste discrimination is propagated is through denialism. That helps the quell the resistance against it. Caste discrimination is still alive among younger generation and in cities. Here we are - discussing c
1355.
▲
by
goku12
4y ago
I just tried it now. The default is still HTTPS when signed out and SSH when signed in. The `gh` workflow seems to be the default only for those who have authenticated using the tool.
1356.
▲
by
goku12
4y ago
QuickLogic [1] seems to support and target the open tool environment for their devices -especially the F4PGA [2] toolkit (known earlier as symbiflow). Others have mentioned Lattice FPGAs. But the impression I got from Lattice is that they l
1357.
▲
by
goku12
4y ago
> My biggest problem with git rebase -i is that it has to be interactive The way I see it, it's a feature rather than a problem. For once, the name (interactive) agrees with its purpose. Interactive rebases are meant to be manual ed
1358.
▲
by
goku12
4y ago
Thank you for the reply! I'm eagerly awaiting the 1.0 release. Good luck to you regarding the new nest and well as the new venture! > I also don't think there's a "right" way to use Pijul. The magic of algebra me
1359.
▲
by
goku12
4y ago
In my opinion, you should certainly go for 1.0, unless you are planning some breaking changes at this point - which I guess you are not, after reaching beta. My general deduction is that tools with a few bugs at an early 1.0 has a better ch
1360.
▲
by
goku12
4y ago
I maintain both branches - a WIP branch and a final rebased result. I agree with the age old concept that each commit on the master should be a full self-sufficient feature. I also like to keep the messy WIP for reference. How does the 
1361.
▲
by
goku12
4y ago
The author has a habit of taking his work offline for months. Hopefully, that's what's going on now. They are so close to 1.0 with their work. I seriously doubt that project stagnated entirely.
1362.
▲
by
goku12
4y ago
There are some advantages of Pijul over Git - Worries only about patches, not about snapshots too - Only a few commands to learn. No complex switches - Combines many git approaches in one. For example: - pijul record (its commit) is an in
1363.
▲
by
goku12
4y ago
Pijul is superb. I do use it. But my wish is that they release 1.0 ASAP. Long time in beta for a code management tool isn't too healthy for it.
1364.
▲
by
goku12
4y ago
It's possible with various tools: 1. git add -i or -p 2. History edits using interactive rebases 3. Using tools like lazygit or git-ui 4. Using stacked patch tools like stgit or topgit 4. Here is my favourites: Use magit on emacs or fu
1365.
▲
by
goku12
4y ago
Git model is intuitive until you have to deal with merge conflicts, rebasing etc. Are you judging with that experience? > For example it lets you browse the files at each commit which really shows how commits are snapshots, not diffs. Th
1366.
▲
by
goku12
4y ago
>I will award honorary negative points for any client which dares to treat git rebase -i as if it were a fundamental primitive. If you think that a git rebase is overcomplicated, rather than a fundamental primitive, then you missed an im
1367.
▲
by
goku12
4y ago
> Use available and widely used libraries for the low level crypto parts (e.g. don't code RSA or key generation on your own). Yes. That's the plan. I'm using Rust's crypto libraries. All the code in the application ar
1368.
▲
by
goku12
4y ago
> When I see a project with a massive disclaimer about "this crypto is not audited, I'm a noob never deploy this anywhere" I'm likely to see better crypto than most of the commercial products I work with, including on