I made a tool for this some time ago. It detects when programs write to your home directory outside the XDG spec and logs the file and the location of the binary that wrote it to an SQLite file.

The screenshot isn’t real though

Monads are just monoids in the category of endofunctors

Everything is meaningless, nothing matters. Therefore whatever you decide is important is all that matters.

You can look up [optimistic nihilism] (https://youtu.be/MBRqu0YOH14) if you want

At some point they l announce that paying for a Reddit premium account allows you to be unbanned and free to do whatever you want.

What other reasons or ideas can you think of, that mass banning users, (some with years of age and contributions, some of them mods.) could be the first step in a plan to capitalize.

To me it seems like it’s a consequence of both cost cutting moderators and lowering the threshold for bans to make the plaform more appealing to large companies advertising.

…definitely takes some getting used to when you come from a non-memory safe language…

I actually think it’s more like the opposite. The compiler takes the normal rules you apply to avoid issues with a non-memory safe language like C/C++ and enforces them explicitly where memory safe languages don’t have those rules at all. I think lifetimes are much more confusing if you’ve never dealt with a user after free and usually let GC deal with it.

Also yes the compiler warnings and errors are amazing, the difference between rustc and gcc is night and day.

I don’t really prefer it. I just buy gaming mice because they have more buttons and disable the RGB.

It will become more complex when you start needing circular references in your datastructures.

It’s only intended to be used by the program itself. It’s purely storage.

Thanks for the advice, but this is just the format of some eyetracking software I had to use not something I develop myself

It’s used to export tracking data to analyze later on. Something like SQLite seems like a much better choice to me.

I’ve seen this myself too

Have some patience and let them learn, it will be fine

Yeah, and it’s useful to just check everything so you don’t forget to add some essential system package for e.g. SSL, especially when working with Alpine.

Why not? Why doesn’t the programmer want to test a container?

https://en.wikipedia.org/wiki/Stockholm_syndrome

Link for those that are interested: https://modrinth.com/mod/psi

I used QEMU but I don’t think it’s possible anymore. I had to use an older version of OSX (I think I tried 3-4) but that version is no longer supported by XCode.

Yes, and the worst part is that XCode is only available on OSX.

I once had to make an iOS app once and didn’t have a Mac so I developed the entire thing in a VM. There was no video encoding, the FPS was in the low single digits, which made it very difficult to even type. So I ended up writing the code using VSCode through SSH through Wireguard connected to the VM on the host machine, which actually worked surprisingly well. But hey, the app did work in the end.

…developing for a platform that doesn’t allow LGPL3 libraries to be used because users can’t replace the LGPL3-licensed binary (ios, android, game consoles, proprietary hardware)…

TIL. I didn’t know that LGPL would add any additional restrictions except for inside the library

Explanation from HN in case anyone else is wondering:

In the case of the App Store, Apple is the one doing distribution, so Apple must also comply with the terms of the license (in addition to the app developer). Apple has decided they will not do that (that is, people they distribute to will not have the ability to modify the LGPL code, relink the final executable, and run it on their devices), so Apple cannot legally distribute binaries that contain LGPL code.

It only makes sense, then, that Apple should preemptively reject apps that link in LGPL code, as they know that they will not abide by the licensing terms.