drey08

> Github was on the decline anyway in the past 5 years, it's time for an alternative and we'll see.

I tend to agree. But I don't see how an exact UI replica of Github is innovative.

I've only glanced at it though, maybe there's more features underneath the hood.

Happy to learn more about what makes it better. Is the CI system more refined than Github Actions? I was definitely never a fan of that system.

Have you ever heard someone get called slow? That's an insult too.

So now you have quick tests. That's disrespectful towards me because I got called slow once.

This can go on forever.

In a similar vain some of the AWS console pages make it hard to select text and use ctrl^c to copy it. It often deselects the text as soon as you hit ctrl. It is extremely irritating.

It looks promising, but why does it flicker every time I input a key? Using WSL & Terminal.

This is about commit comments, not commit messages.

Back when I was first learning about D (over 10 years ago), I crawled those archives and sorted all the posts based on the comment count. It revealed many interesting topics and the history of how D progressed as a language.

I wish forum.dlang.org had a quick way of browsing just the top list of the most commented posts.

How can I use this code snippet? Apologies if it's obvious to everyone.

Does it support three-way merge? I still use BeyondCompare for this, and it's a killer feature whenever I have to rebase my PR against the latest upstream HEAD. Can't live without it, and I consider it an essential feature for a paid product.

Yep.

With WSL I can seamlessly access files from both Linux and Windows. I use the Terminal (Windows) and various Unix tools for a lot of stuff (compiling & testing on Posix, objdump, debugging). And I use Windows GUI tools for editing (Sublime), diffing (BeyondCompare), and so on. I get the best of both worlds.

But WSL2 file access in `/mnt/c/` is now unbearably slow. So I just stick with WSL1.

From what I've read, Microsoft intends to support both WSL1 and WSL2 for the foreseeable future. So that's good.

This looks like web-based Visual Studio Code to me, not Visual Studio.

> blind test

Well yes, all cameras look the same if you do a "blind" test. :)

It's one of the reasons why I still haven't fully switched to VSCode. There doesn't seem to be a way to disable antialiasing in VSCode to make this font look good, as far as I can tell.

We're a medium-sized software company, and we had to create a dedicated GDPR position so someone can look into everything and decide whether we're GDPR-compliant, and if not, how we can fix it. GDPR really complicates everything, even though most uf us (devs) are actually in favor of it (because we don't really like the idea of companies tracking us forever).