DAWN VS Git

It is very important to get up to speed with the basics by going through this website first and foremost: https://github.com/berlin-open-wireless-lab/DAWN

By the way, which degree of configuration did you set up? https://github.com/berlin-open-wireless-lab/DAWN/blob/master/CONFIGURE.md

It's not out-of-the-box perfect, but I've had decent luck using DAWN, which targets openwrt, to get decent bandsteering. I can always ssh in (I personally havent been interested in installing/trying the "luci" web interface) & move someone between bands if I need to.

Also, this setup works across & steers clients between my multiple access points!

It's amazing being able to ssh in and see a map of what signals each AP sees. DAWN periodically asks clients to help map, so even if the AP's are on different bands, you can still compare what the signal would be if the node moved.

We'ee finally living in a pretty good time for open source wifi. A pity how only a couple chips have support (select MediaTek and Qualcomm) but wow things have gotten much better.

https://github.com/berlin-open-wireless-lab/DAWN

I'm a long term openwrt user, finally even set up DAWN[1] to orchestrate multiple APs (sometimes a win, sometimes worse than manually picking).

I really hate to say it, but even for the geeks, I'd generally recommend some kind of mesh product. A roommate installed a parallel Google mesh product & it worked so well, had such great coverage. Google spent hella time making this product good, thanks in part to Google Fiber. There's a great talk on their finding from Avery Penarunn back at the first netdevconf[2]. I'm sure many of the competing products are also very very capable. They have a level of reliable, just works intelligence, even over wifi mesh, that makes me envious.

There's sadly little new news in the OpenWRT space. There's some on-the-cusp work with some new Qualcomm chips that might start working in mere weeks or months. But we've been running the same wifi4 & wifi5 hardware for half a decade now, basically, with no real options. The Netgear X4S R7800 is still the go-to openwrt router. MediaTek has some wifi6 capable routers[3] targeted to the low end, which are nice & available & cheap, which is great, but decidedly low end.

[1] https://github.com/berlin-open-wireless-lab/DAWN

[2] https://www.youtube.com/watch?v=yZcHbD84j5Y

[3] https://openwrt.org/toh/views/toh_available_16128_ax-wifi

For central controller management there is DAWN (https://github.com/berlin-open-wireless-lab/DAWN) but I have not used it yet so I can't tell you how well it works.

A quick search brought up https://github.com/berlin-open-wireless-lab/DAWN on the first glance it looks more like hackers-hand-on than run-and-deploy :D

AFAIK this is what DAWN is for: https://github.com/berlin-open-wireless-lab/DAWN

Look at any PR/patch series that got merged into the Git project. https://github.com/git/git/

Any random one. Because those that did not meet the minimum criteria for a well-crafted history would not have passed review.

Boy, I can't find this either (but also, the kernel mailing list is _really_ difficult to search). I really remember Linus saying something like "it's not a real SCM, but maybe someone could build one on top of it someday" or something like that, but I cannot figure out how to find that.

You _can_ see, though, that in his first README, he refers to what he's building as not a "real SCM":

https://github.com/git/git/commit/e83c5163316f89bfbde7d9ab23...

Here is the direct link, as HN somehow removes the query string: https://github.com/git/git/commits?author=peff&since=2023-10...

I understand all that.

I'm saying, if you write a survey and one of the possible answers is "diff", but you don't clearly define what you mean by "diff", then don't be surprised if respondents use any reasonable definition that makes sense to them. Ask an ambiguous question, get a mishmash of answers.

The thing that Git uses for packfiles is called a "delta" by Git, but it's also reasonable to call it a "diff". After all, Git's delta algorithm is "greatly inspired by parts of LibXDiff from Davide Libenzi"[1]. Not LibXDelta but LibXDiff.

Yes, how Git stores blobs (using deltas) is orthogonal to how Git uses blobs. But while that orthogonality is useful for reasoning about Git, it's not wrong to think of a commit as the totality of what Git does, including that optimization. (Some people, when learning Git, stumble over the way it's described as storing full copies, think it's wasteful. For them to wrap their heads around Git, they have to understand that the optimization exists. Which makes sense because Git probably wouldn't be practical if it lacked that optimization.)

The reason I'm bringing all this up is, if you're trying to explain Git, which is what the original article is about, then it's very important to keep in mind that someone who is learning Git needs to know what you mean when you say "diff". Most people who already know Git would tend to gravitate toward the definition of "diff" that you're assuming (the thing that Git computes on the fly and never stores), but people who already know Git aren't the target audience when you're teaching Git.

---

[1] https://github.com/git/git/blob/master/diff-delta.c