musicmatze

5 ms·

1.
by musicmatze 2mo ago
Same here, atuin is such a time-saver, especially when it comes "oh dang, I ran this command on another host but I need it here now". It just works as you'd expect!
2.
by musicmatze 3mo ago
Been using it for years, for opensource stuff and at work. No issues whatsoever.
3.
by musicmatze 3mo ago
As long as tokens are cheap
4.
by musicmatze 3mo ago
I think a business case for a "look I let an LLM rewrite a large codebase" does not exist.
5.
Show HN: Fail2ban-Dashboard(github.com)
2 points by musicmatze 3mo ago|0 comments
6.
by musicmatze 4mo ago
Shame they use discord though.
7.
by musicmatze 5mo ago
You did not explain why the patch based process is "inferior", neither did you explain why you'd have to "work around" the process!
8.
by musicmatze 5mo ago
One very crucial point that no forge (IIRC) supports that the article missed (or I accidentially skipped it) is that email supports tree-style discussion! That is a HUGE benefit IMHO, especially for patchsets, but also for "issue"
9.
by musicmatze 5mo ago
I switched from KDE with almost what you mentioned: Workspace 1 had a fullscreen terminal with zellij, Workspace 2 had a browser, workspace 3 had two chat apps open and that was it. Bindings to switch between those. I switched to niri becau
10.
by musicmatze 5mo ago
I see where the author is coming from, but still this feels like a reinvention of commit trailers ("Acked-by", "Reviewed-by",...) especially for these non-blocking and "only appraising" comments. Commit trailer
11.
by musicmatze 5mo ago
Exactly as you do. The thing that's different at first is that workspaces are organized vertically rather than horizontally, but I for one adapted to that really quick (coming from KDE).
12.
by musicmatze 7mo ago
Unfortunately, muscle memory cannot be changed that easily. And thanks to the git maintainers, the checkout command still exists, because apparently they know that.
13.
by musicmatze 8mo ago
gitlint (linked in the article, https://jorisroovers.com/gitlint/ ) is a really cool project that we use extensively (and in CI) to ensure we do not accidentally merge "!fixup"/"!squash" commits
14.
by musicmatze 4y ago
It is nice to see another IPFS implementation coming up, especially in Rust - but will there be any good client libraries in Rust any time soon? Does your project involve implementing client libraries?
15.
by musicmatze 4y ago
> If you use Neovim, can you share why you chose it over VS Code, or one of the new terminal-based editors [...] I am using vim/neovim for almost 15 years now. I was introduced to vim within _days_ after I started programming. I hav
16.
Show HN: Roc is a language for making delightful software(github.com)
10 points by musicmatze 4y ago|0 comments
17.
by musicmatze 4y ago
> Am I the only one who thinks that Git's UX is fine, and maybe even rather enjoyable? Same here. Have been using git for over 10 years now though, so this might be an "experts view" kind of thing.
18.
by musicmatze 4y ago
After reading this article I think the author just wanted to trigger everyone or that this is all some strange form of sarcasm/irony. No need to give it a second thought I guess...
19.
by musicmatze 4y ago
> Doesn't anyone else find it annoying and distracting to have your IDE or editor constantly throwing "suggestions" at you? I see where this is coming from. That's why I do not let neovim hit me with completions all
20.
by musicmatze 5y ago
It really struck me to read how many people have a "I don't give a f..."-style workflow with git, especially in the hackernews audience which I always considered to be more on a technical side. With "I don't give a
21.
by musicmatze 5y ago
> - No merge commits. Only rebase onto latest main. Which means force-pushing PR branches and, thus, rewriting history (other devs working on same branch need to be aware that history has changed). How does that even scale? I would imagi
22.
by musicmatze 5y ago
IMO this feature destroys the history the developer of the PR should have crafted carefully in the first place. With a squash merge you basically say "I don't give a f..." and remove all traceability from the PR, giving futur
23.
Himalaya(github.com)
2 points by musicmatze 5y ago|0 comments
24.
by musicmatze 5y ago
I feel that these "workflow suggestions" are all nice and dandy, but have nothing to do with the real world. The real world looks like this: Create a new branch, make changes, commit, make a PR, commit some more (all without prop
25.
by musicmatze 5y ago
I changed jobs on 1.1.2022. The first trigger when I started looking for another job was solely because of compensation. When I learned what I _could_ make and my boss (two levels above me actually) just ignored my requests for half a year,
26.
by musicmatze 5y ago
> I've always seen conventional commits as an anti-pattern as it seems to discourage developers from writing small, atomic commits. Me too, actually I hate conventional commits with a pattern, because I have never seen a "conve
27.
I Hate Conventional Commits(beyermatthias.de)
3 points by musicmatze 5y ago|1 comments
28.
by musicmatze 5y ago
No, we need the power that git offers us for scaling workflows and contributions to large ecosystems. Software does not get less complex over time, but more complex - and we need a system to handle contributions to a complex system (read: l
29.
by musicmatze 5y ago
The constraints of the borrow checker do not make tree structures harder to get right! They just force you to get it right!
30.
by musicmatze 5y ago
Nice writeup, but you forgot to mention https://crates.io/crates/typed-builder - for more compiletime goodness!

More ›