Some rust proponents having this attitude is probably part of the problem.

I think rust has good ideas and may even become the default systems language in the mid-term. I find it irritating that there is a very vocal subset of rust proponents that tend to insist that every project in every language needs to be rewritten in rust immediately. I suspect that is also why other people are down on rust.

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.

https://archlinux.org/packages/extra/any/kde-applications-meta/ ?

I like kate in general but I can’t seem to get it to use semantic highlighting with gopls

https://logseq.com/

Some of it is good and some of it is bad.

For instance it basically says that installing arch manually to learn is pointless and you should spend that time taking an operating systems class. This is confusing two completely different kinds of knowledge as well as time investments 2 or 3 orders of magnitude apart.

The site is also presenting opinions but using language that makes it sound like it is presenting facts.

Overall, I don’t think it’s a great site. It basically says “there are many differing opinions on various topics, but mine are the correct ones and you should treat me as an authority because I made a website.”

Not a fan/10

https://fishshell.com/docs/current/cmds/history.html#synopsis

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

I use fish. I really like that it is already configured to be a comfortable and usable interactive shell out of the box.

The differences from posix are generally easier to remember on the fish side imo (like if statements) and you generally only encounter them when you write scripts.

You can also write scripts in bash if you want and there is a nice tool if you need to put environment variables into shell from a bash script (https://github.com/edc/bass)