I never used npp as my code editor but as a secondary program that i kept notes in and would paste text in to manipulate then move back into code editor. It had a rich plugin ecosystem way before that was common. I use Kate for those purposes instead now

Sort of alarming how many upvotes this has without anybody providing any reference at all. We have enough privacy problems to worry about without people posting unsubstantiated claims :/

I can’t find anything about it. Claim seems sus tbh

Where is the info about this?

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.

There is a video

The stuff in jenis sets up a lot of stuff way later in the series

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

Tampermonkey is one of the few that have already been available