Comparing Windows and macOS to Linux is moot and we should stop doing it. Linux has always been and will continue to be an ecosystem driven by various communities, and expecting everyone to agree on the same standards is silly.
The sooner we all begin treating Ubuntu and Red Hat Enterprise Linux as separate Operating Systems the sooner we can all move on from the "single standard" and "Linux on Desktop" debates. As an application vendor I always find it amusing when customers ask if we support Linux. My response is no, we don't support Linux but we do support Ubuntu 18+ and RHEL 8. Linux distros are so wildly different these days, not just in software but in ideologies, that this distinction is important, and there's nothing wrong with that.
Samsung support is atrocious. Had a similar issue with my S9 phone where the power button suddenly got jammed and couldn't be released. They sent it back with the exact same reasoning: "Caused by physical damage". Well yeah, I physically press the button to turn the phone on and off, what do you expect. I don't understand how they are still so popular when they never help you with anything.
Nice and simple. I tend to use a wrapper around BSD tree.h and SQLite for persistence. Longer insert/update times but quick access and you get the SQL language and tools for free.
Out of the loop when it comes to the latest processor technology. How does this chip maintain the same TDP as a 6850K but with 4 more core? Same size (lithography), roughly the same freq, memory size/types.
Works OK for small teams. If a user forgets to close the database then other team members are only able to open it as read-only. My biggest gripe is that you don't know who is holding the write lock. We work around this by using a setting in our keepass client to close the db after a certain amount of time.
Sorry, I'm not asking about current Debian. In your previous comment you mention that the symbol packages are not new. I'm wondering how people have been creating them on Debian 8.
> Knowing of projects that require it, and specifically which parts, or that are already using the static libdpkg library are very valuable, so that those parts can be improved.
What would be the best way of contributing this sort of information?
Did not know that, thank you. Do you know happen to know how it is done? When I pull the debian tarball for nginx (which has a -dbg package with symbol files) I see:
> dh_strip --dbg-package=nginx-$(*)-dbg
Which is the exact same command I use in my rules file. But instead of giving me a -dbg package with symbol files debuild gives me a -dbg package with the unstripped binary. Not sure what I am missing. I am following the DebugPackage guide on the Debian Wiki[1].
DESCRIPTION: Any plans to go ahead and stabilize the dpkg library for buster? Having access to a stable package management library is essential in our software. Ie. being able to verify package signatures and querying the database for files. Both of which are not supported.
> If you use debhelper/9.20151219 or newer in Debian, it will generate debug symbol packages (as <package>-dbgsym) for you with no additional changes to your source package. These packages are not available from the main archive. Please fetch these from debian-debug or snapshot.debian.org.
No more shipping -dbg packages with full binaries. And less storage space is always a win.