Screenshots of both:

“Classic”	“New”

Well, you can see I use dark color scheme, which apparently got lost. Make a guess how much better I like that.

It’s not my full monitor width because of vertical browser tabs, but even then the horizontal distance between left nav bar and top right nav toolbar is horrendous.

The spacing is wasteful, the sizing is unnecessarily big.

It’s worse in every way. Less accessible, less readable, less scannable, less overview.

I wish they would simply drop their new design draft completely.

For anyone visiting the site thinking “looks like before for me” like I did, at the top there’s a link to “try out the new site”.

Their blog post, research blog post, previous community feedback, feedback form.

We onboarded our team with VS integrated Copilot.

I regularly use inline suggestions. I sometimes use the suggestions that go beyond what VS suggested before Copilot license… I am regularly annoyed at the suggestions moving off code, even greyed out sometimes being ambiguous with grey text like comma and semicolon, and control conflicting with basic cursor navigation (CTRL+Right arrow)

I am very selective about where I use Copilot. Even for simple systematic changes, I often prefer my own editing, quick actions, or multi cursor, because they are deterministic and don’t require a focused review that takes the same amount of time but with worse mental effect.

Probably more than my IDE “AI”, I use AI search to get information. I have the knowledge to assess results, and know when to check sources anyway, in addition, or instead.

My biggest issue with our AI is in the code some of my colleagues produce and give me for review, and that I don’t/can’t know how much they themselves thought about the issues and solution at hand. A lack of description, or worse, AI generated summaries, are an issue in relation to that.

/edit: Here is my comment on the post four months ago.

And it’s so popular! It must be good!

Many times I’ve used piefed, wrote a comment, some longer some shorter, and without fail, it denied posting after writing it out but without telling me specifically why I can’t post. Just no permission. Consequently, it never stuck to me.

I’ve been using TortoiseGit since the beginning, but it’s Windows-only.

In TortoiseGit, the Log view is my single entry point to all regular and semi-regular operations.

Occasionally, I use native git CLI to manage refs (archive old tags into a different ref path, mass-remote-delete, etc).

Originally, it was a switch from TortoiseSVN to TortoiseGit, and from then on, no other GUI or TUI met my needs and wants. I explored/tried out many alternative GUIs and TUIs over the years, but none felt as intuitive, gave as much overview, or capabilities. Whenever I’m in Visual Studio and use git blame, I’m reminded that it is lacking - in the blame view you can’t blame the previous versions to navigate backwards through history within a code view. I can do that in TortoiseGit.

I’ve also tried out Gitbutler and jj, which are interesting in that they’re different. Ultimately, they couldn’t convince me for regular use when git works well enough and additional tooling can introduce new complexities and issues when you don’t make a full switch. I remember Gitbutler added refs making git use impractical. jj had a barrier to entry, to understand and follow the concepts and process, which I think I simply did not pass yet to have a more accurate assessment.

I did explore TUIs also as no-install-required fallback alternatives, but in practice, I never needed them. When I do use the console, I’m familiar with native git to cover my needs. Remote shell: native git, locally: Nushell on top of native git for mass queries and operations.

pen and paper is decentralized storage too, but the push and fetch sync protocols are a lot of work

I expected alpha becoming beta, but the download has no such label at all. Is it considered stable now?

Their news doesn’t say much about the drop of and about the new status either.

The Release 28 is our first release without the Alpha label: our development process has matured, our releases are more frequent, and our commitment to quality has never been higher.

This doesn’t seem programming-related. Am I missing something?

When I was researching keyboards recently, I stumbled over a pro gamer (I believe) YouTuber who was quite vocal about pretty much all gear marketed as “gaming gear” is overpriced marketing bullshit. Apparently, they tested dozens of keyboards, mice, and headsets over the years. It certainly matched my impression of reading tests about products previously.

“Gamer” chairs are racecar chairs meant to keep you from sliding sideways, not being fit for long sitting sessions on a PC. Prefer a good or decent office chair. “Gamer” headsets are worse and more expensive than other headsets. Keyboards and mice are mostly marketing. etc.

Regarding input, they made a point about physical human limitations and state like sleep and caffeine intake having much more of an effect than the hardware you use.

2022 update

So this article is quite old. There are keyboard switches now that activate as soon as you activate the key, and that can recognize lift and press without passing a trigger point. If you want that kind of edge, those are the top performers right now. I’d be more interested in the technology and maybe playful capabilities than the performance they add.

I’m always way too thorough when researching products before buying…

I thought I remembered a standardized metadata file format you can place on your website, but I can’t find it.

GitHub defines FUNDING

Brave webbrowser attempted something like that with Brave Rewards, but through ads, and basically collected for themselves until the websites actually signed up for Brave Rewards.

I remember Flattr.

Claims that it can, but no evidence or anecdotal examples of how it worked in practice.

“Yeah, I can do that task. I’m very experienced in struggling to implement stuff like that.”

Is it available in the free tier?

I don’t think they mention maintenance burden specifically. Using a framework with packages means you have to track upgrades, do upgrades, check release notes, breaking changes, support and end of life cycles, license changes, etc. It’s a have maintenance burden if you keep it live, even if you don’t intend to make any changes.

Vanilla doesn’t have this problem. Server-side has it too, but in a slightly different flavor.

The heavier and integrated the framework, and the more additional packages you include, the heavier the burden.

Why does nothing link to the content/MS page in question? Not this article, nor the Bluesky post or replies.

I would have liked to see and verify the context, and explore the git history which should lead to some context that may give some context to what the author asks at the end: How did it come to be, with what ideas or goals, or justification, etc.

The Bluesky replies mention(/claim) that the image has been replaced, now seemingly copying a graph from Atlassian docs.

I totally get that. Technical and implementation exploration doesn’t necessarily correlate with publishability. :)

It is impossible for me to remember all my passwords. Maybe I have more accounts than other people. I remember the most important ones, amongst them a very long password manager DB password that is annoying to enter, especially on mobile.

First time I set up keepass I forgot the password. I still have the DB file without access. But the second time, I was more serious and committed to it, and made sure to remember and use the password. 😅

I find itch.io to be a great resource not just for games as a “finished product” but for prototypes as well. The regular gamejams contribute to this - a platform of many prototypes. They don’t need the polish and coherence you’d want to invest and publish on Steam.

Have you considered publishing your prototypes?

Even as only a player, some prototypes make for very interesting playful exploration, even if it’s short. For a technological, creative, and inspiration they can be a treasure trove as well.

Thanks for the suggestion. As a first step, I set it up in Nushell with a ctrl+t shortcut:

$env.config.keybindings = (
    $env.config.keybindings | append {
        name: fzf_file_picker
        modifier: control
        keycode: char_t
        mode: [emacs, vi_insert, vi_normal]
        event: {
            send: ExecuteHostCommand
            cmd: "commandline edit --insert (fzf | str trim)"
        }
    }
)

Maybe I will look into more. :) I’ve known about fzf but I guess never gotten around to fully evaluating and integrating it.

Nushell supports fuzzy completions, globbing, and “menus” (TUI) natively. Still, the TUI aspect and possibly other forms of integrations seem like they could be worthwhile or useful as extensions.

To what end? What would you expect version numbers to do? How would you specify or use them, which what consequences?

Grouping changes into releases with explicit numbering instead of a living standard with generic @supports checks?

I guess it would make some things easier and more obvious.