I suppose they could implement smooth panning in high fps even if actual updates would be slower… though it might look funky.
I suppose they could implement smooth panning in high fps even if actual updates would be slower… though it might look funky.
It doesn’t actually detect moved code, though, like git diff
can? I gave it a shot and also there’s a couple issues open about it, e.g. https://github.com/Wilfred/difftastic/issues/520 .
Other than that, difftastic is quite nice.
I use etckeeper to autocommit changes in /etc as git just has better and faster tools to look at the changes of a fle, compared to backup tools.
It’s just so easy to do that there hardly is any point in not doing it.
I suppose it’s the easiest way to try it out.
I wouldn’t use it long-term, because you don’t want Godot to update without you knowing, if there’s something that needs to be changed due to an update. I bet a few people noticed the update from 3.x to 4.x…
I’ve read it also doesn’t come with the C# support, so that’s one reason not to use Steam for it if you’re interested in testing that side.
If you can do that, you already had enough space for reflinking not to matter in the first place, right? Or you can carefully do defragmenting in parts, running dupremove incrementally? seems like a lot of wasted time :).
Here’s one sharp edge: defrag will unshare file contents so sometimes it’s not just feasible to do it.
I was under the impression cross-site cookies are a standard feature per the RFC, though? Or is Patreon using some kind of non-standard extension?
Speed records aren’t usually representative of regular use top speeds, are they?
And how about the actual speeds they are used with? Another poster suggested the maintenance costs of traditional speeds skyrocket as speed increases, while maglev doesn’t really have a lot of stuff that wears down in the first place.
I rather enjoy Tilix. It can tile a single tab without tmux and it can also give special handling to links matched from regexps. I use it to go from Python stacktraces to correct line in Emacs with just a click. It can also do Quake-like terminal, which I use alot.
The project is looking for maintainers, though, so it’s possible at some point I need to start looking for alternatives…
Admins can and do use email server block lists, though, so maybe that’s a great example.
I suppose you’re right–for now. But at some point Lemmy etc will grow large enough to make manual blocking infeasible. Just how much effort does it take to start a new instance even today?
Just keeping a single frame buffer image can take tens of megabytes nowadays, so 100MB isn’t all that much. Also 64-bit can easily double the memory consumption, given how pointer-happy the ELISP data structures can be (this is somewhat based on my assumptions, I don’t actually know the memory layouts of the different Emacs data structures ;)).
But I don’t truly know, though. If I start a terminal-only Emacs without any additional lisp code it takes “only” 59232 kilobytes of resident memory. Still more than I’d expect. I’d expect something like 2 MB. But I’ll survive.
Thanks for the links! Once flatpak/yabridge works great I’ll be able to use it with SteamDeck :).
I wonder though if this might need some additional functionality in flatpak itself…
A patch contains more than the changes: it contains the commit message. In open source projects, and in particular in CVE fixes, the commit message can indeed be quite descriptive. It needs to be!
You’re still right, though. But I like to think professionals are able to verify the changes with the high-quality commit message—possibly in less time than investigating the issue themselves.
I doubt there would be a measureable benefit: after all, the kernel is already compiled without 32-bit support, and the code related to it just doesnt exist in the resulting binary. I assume there could be some small exceptions, though, like choosing to do something in a certain way so that the same approach will also work for 32-bit, and opting for another approach would perform better in 64-bit. That’s just a guess, though.
It’s mostly about maintenance load.
Btw, with PAE the host can have more than 4 GB of memory, so the limit would only apply to individual processes. Still quite feasible to use that kind of system even in the modern day–even if the browser can sometimes become quite large… And then there are of course the numerous embedded applications.
I think I could easily enjoy the gesture, however it’s way too easy to trigger. It’s like a one centimeter movement on a tablet. E.g. the Android app switcher needs a much bigger movement to trigger app closing.
It comes from the words “Eight Megs And Constantly Swapping”.
Yeah, the name hasn’t aged well…
^Zkill -9 %1
is the only way.
kill -9 -1
if that doesn’t work.
It’s two commands to grow the / fs on the fly:
So don’t worry about it. LVM is great :).