The stuff in jenis sets up a lot of stuff way later in the series
The stuff in jenis sets up a lot of stuff way later in the series
Usually it doesn’t matter what abstractions you choose when you try to factor them to support hypothetical future work, because chances are you incorrectly anticipate future needs.
In other words, generic code that only supports one use case will almost certainly have to be deconstructed to allow a good generic implementation for 2 use cases, so it is better to just write simple code and factor code out when you can see the real commonalities.
In other, other words, KISS, YAGNI
I hate reading code like this. It means that there is a bunch of object or global state that could be getting modified by anything all over the place that I can’t see just by looking at the method. In other words, if you say you understand this method, it is because you are making assumptions about other code that might be wrong.
I’ll take a 30 line pure function over a web of methods changing member state every time.
I like kate in general but I can’t seem to get it to use semantic highlighting with gopls
One thing to note about using forks is that they have no chance of being on corporate software whitelists, while firefox does. For that reason, adding to firefox numbers is potentially important. I’ve already seen companies wanting to only allow chrome/edge/safari (even while they officially support firefox …)
Probably because it has only existed for 2 years
Is there a reason you think Forgejo is only for smaller projects?
The way that rust attempts to prevent this class of error is not by making an implementation of free that is safe to call twice, but by making the compiler refuse to compile programs where free could be called twice on a pointer.
Anyway, use after free doesn’t depend on a double free. It just means that the program frees memory but keeps the pointer (which now points at memory that could contain unrelated data at some future point in time) and if someone trying to exploit the program finds a way to induce the program to read or write to that memory they may be able to access data they are not expected to, or write data to be used by a different part of the program that they shouldn’t be able to
Hollow Knight is pretty different than metroid games and I’m not sure I’d directly compare them. I’m the only person I know that doesn’t like Hollow Knight and it seems like the departures it makes from the classic metroidvania formula that put me off it are part of the reason other people like it
Tampermonkey is one of the few that have already been available
There is a video