The real deal y0

  • 3 Posts
  • 723 Comments
Joined 3 years ago
cake
Cake day: July 16th, 2023

help-circle




  • Ye my biggest concern is keys, sdk configs, sdk programs, scripts, environment variables, vscodium configs, … I always take weeks to set all that shit up the way i like it haha.
    But ye, im still checking out what i can drop and what i cant. Or maybe create scripts to config something to the way i like it ( like git )


  • I disagree, semi. I started with mint but wanted to try fedora recently. With windows i had stuff set up that i needed minimal configurations on os switches, and that data splitting helped a bit when switching to linux.
    But to switch from one distro to another needs prep work if you want to keep data and configs with minimal set ups.
    So far ive been refactoring my mint slow but steady to have my home and /opt on partitions and i might need to do more since there is stuff in /var i might need too.



  • Those thingies sticking out are like part of the traces. It can be solder, but that looks very sus and with the brown shade i assume its the back of a trace hehe
    EDIT: and i just noticed there is a fitting mark on the other side. So very very likely ripped traces. And the more i look at it the more i think thats more ripped traces then alive ones haha



  • I didnt think about it, but byte and short and the only names that kinda kept their definition of the number of bits.
    Byte is 8, short is 16.
    And then there is int…
    Its 16 on 16 bit systems and 32 on 32 and 64bit systems
    Long is silly too, it can be 32 or 64, and then there is long long which wth is that even suppose to be.

    Thats why c/c++ systems often ditch ‘int’ or ‘long’ and rather use things like ‘int8_t’, ‘int32_t’ or ‘int64_t’ to explicitly specify the amount of bits