Materialistic[0] effectively does this (minus the screenshot part), not intentional I think (I belive it makes the webview as tall as the requested page and then uses the OS native scroll widget to add a scrollbar for it). The problem I regularly encounter with this is sites that have a vertically centered popup (cookie banner, newsletter, etc.), with a backdrop that obscures the whole page. You first have to scroll down quite a bit (half the size of the article) to be able to click the popup away.
I wonder who is behind this sudden push for these age verification laws. This wasn't an issue until recently and suddenly there are not just laws in California and Colorado, but also New York and Brazil.
> Static libraries have lots of game-changing advantages, but performance, security, and portability are the biggest ones.
No idea how you come to that conclusion, as they are definitively no more secure than shared libraries. Rather the opposite is true, given that you (as end user) are usually able to replace a shared library with a newer version, in order to fix security issues. Better portability is also questionable, but I guess it depends on your definition of portable.
> Why the heck would the application for the German passport or Ausweis be published by some random GmbH and not Bundesregierung.gov?
This way the government doesn't have to release information to the public (think FOIA) about it. Moving central part of government operation into a private GmbH wholly owned by the government has (sadly IMHO) become a somewhat common strategy for the government. Not just Governikus (the one with the passport) but also the Telematik (Health system) and probably some more.
It looks like VVC (H.266) will be significantly better compared to HVEC and AV1.
But due to the patent issues it'll bound to have, I suspect common usage will practically be nonexistent, just like HVEC.
Yes, as unsigned overflow is fine by default. AFAIK the issue was originally that there were still machines that used ones complement for describing negative integers instead of the now customary twos complement.
They absolutely know about this, given that the seemingly reworked markers for this tablet have a redesigned nib holder that doesn't look like it breaks as easily as the old ones.
This is a common enough issue that there are people on ebay selling caps to replace the broken nib holder, but they seem to expensive for what amounts to a piece of 3D-printed plastic; I might just look into your solution with the lamy pen. It's just a shame that reMarkable is handling those issues so badly. They force you to buy a new pen for $130 because a little piece of broken plastic.
Still, if you include transitive dependencies you end up with a total of 90 dependencies[0] which is unheard of in systems programming. This for some reason includes stuff like "winapi-i686-pc-windows-gnu" which really has no place for a set of linux software tools.
I wonder how this behaves in combination with __attribute__((cleanup(...))). Especially if the to be cleaned variable is passed into the tail function as parameter.
Obligatory Lunduke warning, but I feel like the main point of the article (that the project was led by someone without any qualifications in leading such a project) still stands.
The ESP is just a FAT-32 partition, so its capable of being up to 4GB (by default).
At 4GB you can probably store most linux distributions on the ESP, so the title makes it less impressive than it is.
> This C program doesn’t use any C standard library functions.
This is only half true. While the code doesn't call any stdlib functions, it still relies on the the c stdlib and runtime in order to get called and properly exit.
I'm somewhat perplexed why the author did do it with the runtime, given that he doesn't really depend on features of it (except maybe the automatic exit code handling) instead of building with -ffreestanding.
GLib also provides macros that use autocleanup.[0]
Using a bunch of macro magic, they allow you to write `g_autoptr(GPtrArray) arr = ...` to automatically unref arr when the scipe exits.
One footgun that autocleanup has and C++ smart pointers don't is, that the cleanup function isn't called on reassignment, so reassigning on a autoptr causes the previous value to leak.
[0]:https://github.com/hidroh/materialistic