Does anyone have suggestions for tools similar to this/Screen Studio that works as a webcam on macOS? I'd like to share 2-3 windows, with those fancy backgrounds, and a camera overlay, in a 16:9 or 4:3 aspect ratio, without needing to change the resolution of my ultra wide monitor or move/close all other windows etc.
Agreed! The CMake Xcode generator is extremely slow because not only is it running the configure tests sequentially, but it generates a new Xcode project for each of them.
Amazing summary of the mental model of the interdiff review style, and the problems with GitHub's approach to code review. Thank you!
One thing you don't touch upon (yet) is that the diff soup may lead people to prefer the squash merge strategy, to get rid of the "noise" of the fixup commits, which throws away the "good" initial 3 atomic commits as well.
With interdiff review style you're left with the initial 3 commits, and the choice of whether to land them individually or squash them is based entirely on the commits themselves and how atomic they really are.
As far as I know, splitting the series into individual PRs only works if you have commit rights to the repository, so you can base one PR on a different branch (in the main repository) than main.
As an outside contributor, with a fork of the repository, your three PRs will incrementally contain change A, A+B, and A+B+C, making the review of the last two PRs harder, because you need to review diffs for code you're already reviewed in another PR.
Not sure about the fork workflow but otherwise it is possible to change the base branch (manually on GH’s web interface) so that you don’t have to see the original branches and review the changes from A to B and from B to C. Maybe this is not possible with fork workflows?
I remember seeing a similar layout used for an article or blog post about reverse engineering a binary format. I’ve tried finding it later, but couldn’t. Anyone know of such a tool that lets you describe the various headers, fields, etc of a binary format with a similar visualization?
6.0.4 released at 2021-04-22, 6.1 released at 2021-04-27. Where's 6.0.5 and so on? It's not released. Debian supports its releases for 5 years, not for 5 days.
Debian supports its releases for 5 years, not for 5 days.
Only run Debian here, but to be clear, Debian supports releases for 1 year after the next release, so typically 3 years max.
Debian LTS is handled by a third party, non-debian org, via donations. All packages are not necessarily covered, it's not the Debian securtiy team.
This is important to understand, as LTS depends upon donations to decide what gets secuirty updates. Donors have a say. So for example, you'll see apache, openssl, php updated, but not obscure pacakges.
6.0.0 was released 08.12.2020, with 6.0.4 released at 04.05.2021 as the last patch release in that minor series. That's more than 5 days of support for the 6.0 minor series.
If Debian supports its releases for longer than the upstream projects do, then that's a (perfectly valid) choice of Debian, but I'm assuming that involves maintaining those projects as well, to the standards of Debian's support policies.
AFAIK LTS is for paying customers only. For mortal people there's no LTS, there're only promises that 6.3 is backwards-compatible (but then why people pay for LTS at all).
Qt 6.2.4 was released at 2022-02-17 and it's the last public available 6.2 version. 6.3 was released at 2022-03-16. For paying customers they released 6.2.8 few months ago, for example, but it's not available for everyone else.
I do not expect anything from them and I’m grateful to receive quality open source library for free with current terms as that’s infinitely better than having a proprietary library. I’m just merely trying to understand how Debian deals with thus situation.
That said, of course having upstream patches available for free, as it was in the past, would even be better.
How do these distributed build tools work across the Internet, i.e. outside of a local LAN office setting? Does the increased latency and slower bandwidth become a bottleneck?
They will work over the internet. You should use SSH or a VPN like Tailscale because the native protocol is not encrypted.
Bandwidth and latency effects will have some effect on how well it will scale, but on a reasonably high latency and low RTT connection it's probably still faster than purely local compilation. Sending work over the network takes time but not much CPU, so the local CPU is freed up to do other work.
If you distribute preprocessed code, you need LAN speeds/latency for it to be faster than a local compilation. Otherwise, you need to have the exact same headers in addition to the exact same compiler installed everywhere. It MAY work otherwise, until it breaks in a subtle / obscure way one day and after tracking it down you will think maybe compilation doesn't take THAT long on a single machine :)
So all in all, I wouldn't say works outside of a well-controlled cluster on a LAN.
Assuming you don't use NFS to continuously read and write, I think it would be fine. Compiling is generally speaking CPU bound.
Even the website mentions that it just copies all preprocessed code to the workers, so I expect this to be a one-time overhead per job.
I wish I could use Zeal to browse the Apple documentation as well, but unfortunately that’s exclusive to Dash.
I’ve even paid for Dash to get that feature, but no longer use it due to some UI changes in the latest version that add extra clicks for each search query, making the UI inefficient.
Zeal seems to have be inspired by the old and efficient Dash UI, but I can’t have both that and the Apple docs from what I can tell.
The communication with the author (Bogdan) has unfortunately been lacking, taking very long to reply (months) and at best confirming the issues but without any plans to fix them.
reply