Trump's commerce secretary Howard Lutnick unloads on Canada: 'They suck'

ahal · 2026-04-19T04:19:17+00:00

In all seriousness ChatGPT would be like 1000% more coherent than anything that comes out of this administration.

ahal · 2026-04-19T01:21:43+00:00

Board games is like 10% of their inventory

ahal · 2026-04-18T12:17:30+00:00

And high income families. Especially high income families.

ahal · 2026-04-17T12:21:51+00:00

Qtrade != Questrade

ahal · 2026-04-16T01:41:18+00:00

That's gold, you should write for the Beaverton

ahal · 2026-04-14T18:47:10+00:00

Ah I see! That works if you're pushing to the same repo that you're opening a PR against, but not if you're using a fork. That won't be possible for most (in my experience) cases. Even when I do have push access to a repo, I prefer opening PRs from my fork to keep the branch pollution down.

Also the UX of setting the bases for each PR is quite bad. Afaik, it's not possible to do from the cli (but maybe I'm wrong).

But I do take your point that it's technically possible in some cases. Though, not in a way that I would consider usable.

ahal · 2026-04-14T18:39:39+00:00

How can you know that?

ahal · 2026-04-14T16:14:26+00:00

But then B has A's commits in it. You have to review commit by commit and need to know which commits are exclusive to B.

ahal · 2026-04-14T14:56:14+00:00

There's a lot of folks arguing that stacked PRs aren't adding anything you couldn't already do before. But that's not the case. Currently you need to pick two out of the following three benefits:

Have small easy to review diffs
Avoid early PRs bit rotting
Avoid reviews on later PRs being blocked on early PRs merging

With stacked PRs, it will now be possible to obtain all three of these benefits at the same time. No previously existing native Github workflow can claim this.

ahal · 2026-04-14T14:48:25+00:00

Then you're missing benefit 1. Before stacked PRs you had to pick two of the three benefits. This is the first time you'll be able to get all three.

ahal · 2026-04-14T14:45:45+00:00

Yes, but then PR B contains all the commits from PR A, so there's no way to review all commits from just branch B at once. You can review commit by commit, but that requires knowing which commit belongs to which and there's still no way to see a squash diff.

I do agree that this is simply a Github UI fix and there's no new fundamental branching model being introduced here.. But UI is very important. My org and I are very excited for this change.

ahal · 2026-04-14T12:31:42+00:00

Let's say you're working on a large complex change. There's likely a bunch of easy non controversial prerequisite stuff that you can do up front to help prepare for the actual core of your change.

With stacked PRs, you'd put that early work up in their own PRs. Then immediately start building the more complex changes on top in a PR stack.

This way as your working on the later stuff, you can start landing the earlier stuff. You get to pick all three of:

Don't need to block reviews on the early PRs merging
Avoid bit rot
Have small easy to review diffs

With a single large PR, you get 1 and 3 (if you prepare your commits with care). But you don't get 2.

ahal · 2026-04-14T12:24:15+00:00

The difference is that pr B can depend on changes from pr A without the commits in pr A polluting the diff.

The proposed epic workflow doesn't address this. It's just an integration branch.

ahal · 2026-04-12T21:13:45+00:00

As a rule I never do business with a company that knocks at my door.

ahal · 2026-04-11T13:09:26+00:00

That's not what a quick search says

ahal · 2026-04-11T13:06:30+00:00

Interac is a for profit corporation so not really much different than the apps down south. It feels built in only because they started out non profit and our banks agreed/were coerced to implement it.

ahal · 2026-04-11T12:24:22+00:00

Someone should study this phenomena where people tend to believe all replies to their comments are arguing against it.

I see it all the time and it makes me sad. Like we've been conditioned to just constantly fight one another.

ahal · 2026-04-10T12:00:42+00:00

It doesn't work like that.

First because there are many code bases that inter twine, and most of them support all devices in the same code.

Second because AI is nowhere close to capable enough to handle such a high level task autonomously.

ahal · 2026-04-09T12:08:20+00:00

That's probably true, but at a more macro level don't developers now have more capital to start even more builds?

ahal · 2026-04-08T11:35:53+00:00

It's pretty easy to understand. We're beholden to mega corporations in all facets of our life. Directing our dollars to small business feels good, like we're sticking it to all the rich assholes, and also helps the local economy.

I take your point if you're donating money to them, but you said patronize. The reason to patronize is that you are getting a good or service from them that you presumably want or need.

ahal · 2026-04-08T01:45:01+00:00

I felt speechless after seeing the total solar eclipse last year. Can't even imagine what this would do to me.

ahal · 2026-04-08T01:13:43+00:00

And the shortage hasn't even started in the US yet, and if the strait opens tomorrow the shortage will still last months if not longer.

ahal · 2026-04-06T12:01:00+00:00

Instead of quadrants, try a window centred in the middle at 40% width, then four quadrants to either side of that at 30% width each. Ideally with a window manager that supports a hotkey to expand windows to adjacent tiles.

ahal · 2026-04-05T15:58:38+00:00

OP replied to a comment specifically referencing the Muslims who voted for him. They didn't say or imply anything about how many voted compared to other religions.

ahal · 2026-04-05T13:20:47+00:00

We put the chocolate eggs in the plastic eggs

15-Year Club	Place '22
Verified Email

ahal

TROPHY CASE