commit: 7c4b1745eacee2e8cced434fe358b6f32e55a03d
parent 0de9e9b4631134b75fd156eada4c5d485073e764
Author: Haelwenn (lanodan) Monnier <contact@hacktivis.me>
Date: Mon, 6 Jul 2020 08:43:29 +0200
articles/BadWolf, one year later: minor typo fixes
Diffstat:
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/articles/BadWolf, one year later.xhtml b/articles/BadWolf, one year later.xhtml
@@ -16,7 +16,7 @@
<p><strong>But!</strong> In my opinion WebKit is already much better than Firefox at privacy, for example ephemeral sessions (hardcoded mode in badwolf) will save absolutely nothing to the disk, which is something that is quite how Apple (or at least their employees) seems to want in a browser anyway. Mozilla could try to dance around with finally picking some of the modifications done in the Tor Browser but as far as I can tell there is still very large differencies between the two.</p>
<p>As far as RAM usage goes… well it's a modern web browser so it'll eat whatever is available, a laptop with 4 GB seems to still be quite confortable with it, WebKit seems to not clean up WebKitNetworkProcess when I close a tab but it's basically the only thing that stays so I can just close a bunch of tabs and get back some percents of memory. (and after something like 2 months close some windows) I haven't needed to put my browser in a cgroup to limit it's memory usage like I still do with firefox/chromium.<br />
On the other hand, startup time is so fast that I don't feel the need to have <code>badwolf [url…]</code> commands try to hook to an already running session. I litterally just spawn a new one for each link in my RSS/Atom feed and it's fast enough on my desktop with some quite slow (but reliable) SATA 1 HDDs.</p>
-<p>On the developer side of things: WebKitGTK is unusable with overcommit disabled than to GLib (it's calling <code>abort()</code> when malloc returns <code>NULL</code> which is great as it kills the whole browser when doing stuff like opening a new tab…), can't be fixed now because that would break the ABI/API because some parts are no return value, this is why you should use <code>int</code> which is more or less the default as a return value unless you're absolutely sure that it will never fail.<br />
+<p>On the developer side of things: WebKitGTK is unusable with overcommit disabled thanks to GLib (it's calling <code>abort()</code> when <code>malloc</code> returns <code>NULL</code> which is great as it kills the whole browser when doing stuff like opening a new tab…), can't be fixed now because that would break the ABI/API because some parts are no return value, this is why you should use <code>int</code> which is the default as a return value and one that you should use unless you're absolutely sure that it will never fail.<br />
Linux maintains bugs because the userland also does so…</p>
<h2 id="badwolf-1year-future">Future</h2>
<p>BadWolf 1.0.0 should arrive soon™, main blocker is documenting the interface so it can be properly put as stabilized. I'll also try to finish installing SourceHut on my setup so I at least get a tracker and CI from it.</p>
