• 0 Posts
  • 40 Comments
Joined 1 year ago
cake
Cake day: June 20th, 2023

help-circle
  • Depends on settings and the amount of availlable RAM. Install fedora KDE spin on three systems, one with 4GB, one with 8 and one with say 16GBs of RAM. You should see, that the vanilla install of KDE uses different amounts of RAM on each system. KDE uses caching of all kinds of stuff to make the overall experience smoother. The amount and aggressivenes of the caching depends on distribution defaults. And KDE using, say, 8GB of RAM when idling isn’t bad. RAM is only useful, when it is used. When memory pressure increases (applications are actively using lots of RAM), KDE will automatically reduce cache sizes to free the RAM up again.

    The entire notion of the system using as little RAM as possible is really weird and usually (imho) shows that people who say that don’t understand how the RAM is used. I want my system to make good use of my RAM, and as much of that as is reasonable.





  • it will help developers

    Until they break it.

    ship extensions faster

    Which they need to adress the regular breakages.

    and with fewer bugs by using standard JavaScript modules and IDE support

    If I wanted to suffer web technologies, I’d develop content targeting web browsers, not a DE. JavaScript does a lot of things, being conducive to bug free code is not one of them.

    I really admire the pain tolerance and endurance of devs developing and maintaining extensions for gnome. At what point does it become acceptable for them to drop that garbage DE? Rhetoric question: always has been.


  • I remember this working really well on google. Recently (several months?) it didn’t as I would expect. Fictional example: when searching for “asdf123” google would show results just containing ‘asdf’. One particular thing I noticed was that google seems to omit underscores from verbatim strings. So for example when searching for “asdf_qwertz” it would show results that contained asdf and qwertz without the underscore.




  • When I was studying CS I had a few courses on UX/UI design and the most interesting fact I learned there when looking for papers is: ~half the high profile researchers in the UX/UI field are on Microsoft payroll, and everything Microsoft does is highly inconsistent to contrary to all the insights of their own researchers. I think they buy as many of those people off the market as they can, just so they don’t work for somebody else, while shitting on their work, so their UX/UI just doesn’t look as bad in comparison to others.








  • edit: mixed you up with OP, but, meh, unaltered reply:

    Where the fuck is the actual executable and its configs?

    which ... with … being the name of the executable. Whyever it matters to you in which exact path an executale is …

    God help you when you uninstall and clean things up if you use compiled packages instead of ones from your repository.

    make uninstall or xargs rm < install_manifest.txt will usually do the trick. If neither is an option, observe the output of make -n install and undo the installation manually.

    Judging from your post and comments, you’d be much better off with a distro other than arch and using packages from a distros repository plus maybe flatpak or snap.

    This has to be my number one gripe about Linux. How every package just spews binaries and libraries and config files all over the place.

    99.9% of the times those places are pretty well defined and easy to look up. You seem to lack some basic knowledge about linux/unix conventions and make false assumptions about how things should be and then come to judgemental conclusions when they aren’t.




  • For the kind of workload you’re describing, 16GB of RAM was on the low end like 5 years ago. Your number one priority should be getting more RAM. For what you’re doing vmware is at least better than HyperV, and depending on what people are doing with their machines there can be pros and cons favoring Windows, linux, OSX, … in your case Windows is factually the worst choice. When working as a developer with linux native technologies, use linux. If you insist on your kids playing with your work machine (interesting choice), and they “need” Windows, then dual boot. Other than that I’d second another users advice to go with fedora (easy to use, up to date, no bullshit). But do yourself a favor, go bare metal, and get more RAM.


  • Up until now, I’ve only been commenting on other peoples comments to nitpick. I think it is time to give you a comprehensive answer on my own:

    You didn’t mention, what distribution you are using. Either way, you should use your distributions package manager to install zsh. Wherever that places the zsh binary is fine; you should not change that! If you want to know where the zsh binary is located, you can issue the command which zsh. That zsh should somehow be dangerous as a root shell because it is not POSIX compliant is nonsense. You can use whatever you like as a shell for root. If you don’t want to change the login shell for root, you can just start every shell from any shell by executing it’s binary (i.e. in bash type zsh, or the other way around). If you want to know what shells on your system are considered viable login shells by your system, you can issue the command cat /etc/shells; in your case it should list /usr/bin/zsh. If you want to change the login shell for a user, as that user run chsh -s ... where … is the fully qualified path of a valid login shell; to be sure to not make typos or use an alternate path, you can combine that with which, and for example to use zsh use the command chsh -s $(which zsh). If you are the sole user of your system, I’d strongly recommend using seperate configurations for zsh for your normal user and root.

    So now when I drop into a root shell I don’t get […]

    Issuing su - or sudo -i or logging in as root in a full screen TTY (ctrl+alt+F*) will spawn a new shell (the login shell configured for root). If you are unsure, what shell you’re currently in, you can find that out, by issuing the command readlink /proc/$$/exe. If readlink is not available on your system, you can use ps -fp $$; be aware though, that that will show you the command the shell was started with, not necessarily the path of the shell executable.

    If you want to write scripts you should always specify the shell it should be executed by with a shebang. For maximum portability/compatibility (do you like to distro hop? want to share it with a friend/the internet?) you should use env in the shebang. For you, if you want to script with zsh, that simply means always having #!/usr/bin/env zsh as the first line of scripts.