I wonder if the slowdown in non-ai features this release was influenced in some way by their migration away from AMD modules to ES modules.

Putting myself in their shoes and taking codemods into account, I wouldn’t want to make a big feature and have to worry about AMD/ES module concerns. Why do that when instead I could get a bunch of checking and smaller (but non headline) tasks out of the way and get back onto the larger features in 1-2 months after the ES modules are proven to work and I don’t have to worry about rolling back changes.

Either that, or sometimes by statistical eventuality we end up with changes (which all take a different time to be completed) just not being released within a small period of time.

There’s no official announcement per se, but the windows version is built with .net which has been getting better linux support over the last two years.

There are unofficial instructions to run it through wine on their issue tracker.

It’s basically just a better sourcetree.

If you’re already used to sourcetree, it’s a really smooth transition.

The main reason to switch away from sourcetree is the bugs and papercuts.

• Bugs: Sure, bugs happen with everything but you’re stuck with them when they happen with sourcetree. There was an issue not too long ago where sourcetree couldn’t scroll. It was classed as a low priority bug and took about a year for it to be fixed. Imagine needing to use your keyboard to scroll up and down, but then git would refresh and take you back to the top where you’d need to start again. Now imagine trying to do that for a whole year. And that was just one bug.

• Papercuts: It’s so good at some things that you want to forgive the flaws in other things and find workarounds to bugs, but after a while they build up into poisoning you’re experience. For example: things going slow in larger repos, getting git errors when staging certain lines because a different line in the middle had to be staged/removed in a different order, the bi-yearly account issues, etc…

The thing is, you don’t need to put up with it since fork already does everything that sourcetree does (and a bit more), and they actually spend time sanding off the papercuts so you don’t need to worry about finding workarounds when something goes wrong.

Just losing the bugs without losing any features is already reason enough to switch.

But there’s also the improvements over sourcetree as well:

• Collapsible and sortable git graph (by date or topology)
• Better staging – Sourcetree supports staging changed content by file, hunk, and sometimes by line when it doesn’t bug out. – Fork supports staging changed content AND original content by file, hunk, and by line. That way if you changed a line, you can keep both the old version and new version in a commit. (e.g. You altered a comment in your code, but then upon self review when staging changes you realised you don’t want to change the comment, but instead you want the new comment to exist under the old comment. Instead of copying the change, undoing the change, then pasting the change into the code, you can simply stage the addition of the line, but discard the removal of the old line. Now both lines exist in your code)
• Better rebasing
• Supports new git features (e.g. worktrees, new diff algos, etc)
• Just how snappy the program is compared to sourcetree, it keeps you in that flow state

Looks quite good if you want to use git exclusively in vscode.

IMO, fork is the best git client for macOS/Windows but lacks native linux support (although they are experimenting with it).

Until fork gains linux support, this seems like a nice alternative if running on linux (and if it supports the remote development APIs: running on a linux docker image)

That’s 41 degrees for everyone who doesn’t measure things in bird per gun.

No one’s asking nor wondering why you find looking at things in the sky beautiful.

They’re asking why you’re ascribing meaning to an arbitrary number of days. Months aren’t subjective, they’re arbitrary.

What to know about blue supermoons:

1. They literally mean nothing.
2. The change is imperceptible to everyone.
3. Expect useless clickbait slop about it until it passes.

Post title is misleading as he’s not really the one causing the drama.

it’s simply false to say he’s continuing to cause the drama and problems when all he did was ask to get his commit access back …

No. When he realised he wasn’t immediately given access as he was asking for it he also made a post on the unmoderated reddit board with “Drama” in the title.

He inflamed drama during what should have been an otherwise fairly dull bureaucratic process, tried to hide his earlier posts, was called out on it with a timeline, then eventually half-admitted to creating drama.

… and tell his haters they’re being assholes

Engaging with haters is creating more drama, which makes more disruption, which makes more haters, repeat ad infinitum.

He just needed to ignore them and let the mods do their job, not make their job harder than it already was.

The drama comes from people who just hate the guy and are screaming about letting him back. His response to that was then very cordial and just calling out them for being to aggressive.

It definitely appeared cordial on his part, but the timelines of events comment showed he was cherrypicking and trying to change things after the fact. He was being deceitful and manipulative which of course made everything worse than it needed to be. He drove away more of the community.

All he needed to do was not be disruptive himself, let the mods sort out the initial haters, and let the boring topic of a commit bit be addressed.

Looking back at history, it would lead to more propaganda and more support for going to war.

A population getting attacked only leads to that population wanting to an us vs them mentality and emotional knee-jerk reactions over rational responses.

This particular release didn’t seem to add much to the core app in terms of features, but it’s nice to see they’re putting work into making the rest of the ecosystem better.

The thing I’m really hoping they fix is the Find / Select feature gap to help power users:

I made a bug for it: https://github.com/microsoft/vscode/issues/212562

Besides that, and maybe better modal support (for improved vi mode, or alternate modes like kakoune/helix), I’m not really seeing any notable feature gaps anymore, which is great!

As an outsider looking in, it looks like it’s a bit of a wipe the slate clean governance and moderation wise as voted on by the community.

So, now over the coming days the community will in essence vote on whether they will allow sponsorships from the military industrial complex.

The solution is simple: Remove the dagger mid-combat.

You could make the dagger too hot to hold and it falls out of reach (off a mountain, into rushing water, etc…)

You could make the dagger dissolve away (through lava, acid, being eaten, etc…)

You could make something take the dagger (disarming, stealing, etc…)

A hag/genie/etc could place a curse on the PC (holding anything makes them experience immense pain and drop what they’re holding, anything dagger they hold is turned into a spoon, etc…)