• 14 Posts
  • 63 Comments
Joined 11 months ago
cake
Cake day: July 24th, 2023

help-circle
  • They’re making a new browser engine from scratch in an open way, absolutely amazing!

    I do have several questions:

    Why would they use BSD instead of GPL? If you care about open-source so much, why would you make it possible for a company to run away with your fancy new engine?

    Why are they creating a new browser, when even firefox has to struggle to keep some semblance of market share? I get that not every project needs to aim to be “the biggest”, and that even a smaller project (in terms of users), can be fun. It’s just that writing a browser engine that can handle the modern web seems like an almost Sisyphean task; which makes me wonder what their motivation(?) is.

    Why the FLOSS are they using closed-source proprietary discord as their main communication channel?











  • You can also do the following to prevent unwanted writes when something is not mounted at /mnt/thatdrive:

    # make sure it is not mounted, fails if not mounted which is fine
    umount /mnt/thatdrive
    
    # make sure the mountpoint exists
    mkdir -p /mnt/thatdrive
    
    # make the directory immutable, which disallows writing to it (i.e. creating files inside it)
    chattr +i /mnt/thatdrive
    
    # test write to unmounted dir (should fail)
    touch /mnt/thatdrive/myfile
    
    # remount the drive (assumes it’s already listed in fstab)
    mount /mnt/thatdrive
    
    # test write to mounted dir (should succeed)
    touch /mnt/thatdrive/myfile
    
    # cleanup
    rm /mnt/thatdrive/myfile
    

    From man 1 chattr:

    A file with the ‘i’ attribute cannot be modified: it cannot be deleted or renamed, no link can be created to this file, most of the file’s metadata can not be modified, and the file can not be opened in write mode.
    Only the superuser or a process possessing the CAP_LINUX_IMMUTABLE capability can set or clear this attribute.

    I do this to prevent exactly the situation you’ve encountered. Hope this helps!






  • It’s probably best to limit yourself to a used laptop.

    Reading and writing code is nothing more than reading and writing text, and for that you don’t need a fancy gpu or screen.

    What I would recommend you look for in a laptop is

    • an SSD instead of an HDD
    • more cpu cores (at least 4 cores)
    • more memory (RAM) (at least 8GB, preferably 16GB+)

    More memory and cores will help you with compiling and running your code.

    And make sure you take regular backups! You never know when your disk will fail.

    Also make sure to check linux compatibility before you buy. Laptops used to be a pain (10+ years ago), and it’s gotten a lot better, but it’s not always perfect. Just search for “[brand] [model] linux” or try to find the model on the archlinux wiki.