Just think of how long it takes to craft a skeuomorphic icon compared to a symbolic monochrome one.

About the same time.

To be fair I’m not too fond of extremely colorful icons. They do have their place, but in most interfaces I do prefer flat or slightly shadowed icons.

I value more the UX of the interface than the design of the icons, tough the icons are indeed important. Painting icons over KDE does not really change how you interact with KDE.

I don’t particularly like KDE, but have not found a better DE anyway.

Saint Elbakyan, please redeem us. Give us our daily papers and don’t lead us to paid open access.

Would be great! Fuck Elsevier, may that company burn in hell.

If I have to pick a side, I’d go for meta in this case. Elsevier has no rights to defend their ownership of research conducted with public investment.

You overestimate the amount of people who actually use a computer.

In Italy “Non dare da bere all’acido”

Do not pour a drink to acid.

I guess this could be a cool solution to having to make several usernames on different gitlab instances.

Still, I’m not sure if this is really worth it: if I want to self host I’ll just self host a git repository and that’ll be incredibly easy to setup.

The main advantage of GitHub is that it’s completely free and I don’t have to bother about self hosting it and maintaining the software.

I do see some advantage, but I’m not sure it compensates the added maintainance work.

In Italy a pizza is a pizza. Size can vary a little bit restaurant to restaurant, but no way you can ask a different size pizza than the one you’re being served.

Some places may offer slightly smaller ones for kids, but that’s quite uncommon.

As you can see, this is not at all a reliable way to communicate sizes: I have no way to decypher how large a large pizza is.

That’s just because you didn’t start looking in the smaller problems yet.

What is large pizza? The only size of pizza I know is pizza. How many seats does the school bus have? That can easily change by 15 meters.

The pipes were running just nearby the data centre, free real estate

A very useful thing I found is the following: take a couple hours thinking about interesting research ideas. Work out with chatgpt existing solutions and identify key publications. Use Claude code to modify existing software to do something new. In one day of work you got a proof of concept of whether your idea may work. Of course from there on you have to work it out and make it good, but having a confirmation quickly completely changes the fact that you normally have to go through dozens of papers and take several months to review existing publications on the topic.

They just told me, you should be ashamed

dnf has a MUCH nicer interface than apt. Pacman is a completely different beast, but will basically just install anything you ask it no problems regardless of whether that will brick your device or not. I still don’t get why you need all that update && upgrade thing. How many users want to upgrade without resolving the repositories before that?

Not really, my browser should happily comply if a webpage I want to use needs 7 GB.

No way YouTube needs 7 GB.

Tried ACL, it kind of works. However users first respect the creation umask, which is generally 022. Which means they can create files in my directory but I can not delete them.

You can force everyone working with you to set their umask to 000, which clearly is not a really nice solution. However, even this does not solve the problem, since if they copy anything over which does not have 666 permissions then you can not edit it or delete it.

Then you’re stuck with a bunch of files by someone else who left you their things that you can not delete.

I still have 1 TB of stuff somewhere from a user which has long been deleted from the system, I have no other way to delete that stuff than contact the system administrator.

You can assign a group and then set permissions to 660 and do some ACL magic which hopefully works to enforce a umask of 0 on group; however you can not create a group without being root, which does not really solve the problem.

To be fair, I would appreciate if users were allowed to create their own groups.

Never have I seen a public folder on a Linux system, neither personal nor the ones I use for work.

Either way, it would not solve the problem of me myself deciding to share a folder with a set of selected people who can write files in the folder which I then can modify or delete.

I can get to the point of them reading, modifying and creating new files; but the fact that I can not delete files by someone else in my own folders really pisses me off.

Cool, but to be fair Linux is made to not make you root.

In most cases a sysadmin somewhere is root, and you may only pledge to him by email and wait weeks for when he decides you waited long enough for a reply.

User permissions are quite strict in Linux.

I’m still pissed there is no way for a user to decide to open a shared folder to other users which enforces base permissions without root doing that.

I like squash merge on small changes, but when larger code changes are there it becomes a huge commit which is difficult to review if you ever have to go back.

When I do that I always have a Dev branch that I use as the production branch to run the actual calculations.

When I get something working I merge it off, clean up the history a little bit, rebase main onto it and then rebase de onto main.