Skip Navigation

InitialsDiceBearhttps://github.com/dicebear/dicebearhttps://creativecommons.org/publicdomain/zero/1.0/„Initials” (https://github.com/dicebear/dicebear) by „DiceBear”, licensed under „CC0 1.0” (https://creativecommons.org/publicdomain/zero/1.0/)BI
Posts
2
Comments
425
Joined
2 yr. ago

  • You can install any general purpose distro (debian, opensuse or one of that others suggested) with a lighwwight DE (LXQT, Xfce, MATE) and it will work well. However when you run a browser and open several tabs with heavy websites it will become very slow. It does not matter what distro you use. You need 8G+ of RAM for comfortable web serfing nowadays.

  • BTW it is possible to compress existing qcow2 images. Before that I recommend to run fstrim -a inside the VM. Then shut it down and execute qemu-img convert -cp old_image.qcow2 new_image.qcow2 && mv -f new_image.qcow2 old_image.qcow2.

  • I did not use virt-manager for a while, but probably it allocates the whole virtual disk by default (i don't remember for sure). Try to create it manually and ensure that checkbox "allocate the whole volume" is disabled. You can also do this with qemu-img create command (see man qemu-img for options).

  • Well, sometimes it is possible to write a loop with break or without it, and in such cases solution without break is better readable. But if you don't see a simple way to avoid using break, use it. It is very common, as well as having multiple return statements in function. Even goto can be a good solution sometimes if it points to label located below and not very far.

    However you should avoid some antipatterns. If you write an infinite loop that is interrupted only by break, it is highly likely that you are doing something wrong. Nested loops with multiple breaks or gotos are very hard to read and debug. Such code usually can and should be rewritten for better readability and to avoid possible errors (occasional hangs, for instance).

  • First, it is generally a bad idea to manually install software in package based distro. It can break something in your system (providing install.sh script is quite uncommon, it means that developers can do something uncommon and unexpected). Even if everything will go fine, once after system update the program you installed will get broken dependencies and stop working. Better search for prebuilt RPM package.

    Then, answering your question: to build against libraries you need to install corresponding -devel packages. In Fedora their names can differ from the library name (e. g. not libglvnd-devel, but glvnd-devel, you need to search them yourself). For wayland-scanner you need wayland-devel as you can find here or with command dnf provides '*/wayland-scanner'.

  • While transition to Thumbleweed can go smooth if you are lucky enugh, switch from Thumbleweed to Slowroll can be problematic. It will envolve downgrading packages that is usually not tested at all. Better switch from Leap to Slowroll directly.

  • In general, no. Better way is to download packages with that tools from your distro repository, transfer them via flash key and install. You also have to download dependencies, but CLI tools usually have few of them and there are good chances they are already installed.

  • I agree. The problem is that we already have a lot of compatibility breaking options in gcc: different language standards, non-standard extensions, language features that can be disabled, warnings that can be turned into errors... Multiplying them is not the thing that will make a programming language/compiler better.

  • There's nothing new in rust that was not already possible with C++. It is possible to change language syntax using macros and templates... if you want to write code that nobody will understand.

  • Well, every C/C++ compiler is overcomplicated because it has a preprocessor, provide numerous pragmas, attributes etc. etc. What you want is not just a new compiler, it is a new customizable language.