• 0 Posts
  • 15 Comments
Joined 3 years ago
cake
Cake day: July 8th, 2023

help-circle

  • nemith@programming.devtoSelfhosted@lemmy.worldVyOS or Opnsense
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    edit-2
    5 days ago

    Both are just abstractions over primatives and services find in the underlying operating system.

    Moving to just native PF or nftables and running your firewall like a server has been on of my best moves. You will learn a tone more, have a lot more flexibility and overall I think it’s a much better experience.

    I am a traditional network engineer as well (learned Juno’s/Cisco/etc). Ansible is a good way to do “commits” and config management.


  • I have bought and returned 2 framework laptops. They are repairable but they are also questionable build quality.

    The screen on the Framework 12 is very subpar and the size and weight throw it out of being a light laptop.

    Despite saying how good Linux support was running NixOS on the replacement Framwork 13 was not great either. Wireless drops and countless reports of drops on their forums with zero responses or workarounds. Most people buy replacement wireless adapters cause the one Framework ships just doesn’t work.

    On top of that the laptop just feel cheap with a steep price. I have hope for the new Pro, but we’ll have to see if it’s any good because so far I am pretty dissapointed with Framework.





  • I used to work at FB a a while back (working on infra, not FE or anything user touching) and we would have private development servers and occasionally I would need to do work on the FE PHP repo (called www) and would need to stay a development server for FB.

    It would connect ti the various services and database as read only and was a private copy. It functioned just like a real webswver with the exception that the cache was stone cold. It would takes MINUTES to load the front page the first time. It is crazy how much caching just makes it functional.

    The problem is that there are so many services and datasets read all the time.



  • In general, you are right. Once you explain to the borrow check you are doing the right thing then you have a fair level of confidence in it being right.

    I think the point from the article is if it is worth it. Give the single sentence in the article about a list and pointer. There are various ways to do it safely (and ways to do it unsafely like you pointed out) and sometimes it might be ok to put the onus of that onto the developer and validated with valgrind, asans, and unit tests. For some this is far more enjoyable than worry about the borrow collector.

    It’s all a trade off and it’s ok to have difference criteria when approaching a problem like a cli tool or even a business critical service. The problem becomes when Rust people claim that the borrow checker is the only way and we all roll our eyes.






  • How are you measuring memory storage size? Are you sure you are looking as resident memory size and not just the virtual memory size?

    Actual storage of the structures should be nothing. Interfaces are “fat pointers” but that should really just be an extra word which node would have at least that if not more.

    My guess is that if you are looking at virtual memory that more memory/garbage is produced in PARSING and not storing and that the virtual memory size allocated is high even after garbage collection but RSS should be different.