unperson [he/him]

  • 0 Posts
  • 60 Comments
Joined 4 years ago
cake
Cake day: July 28th, 2020

help-circle








  • For smartphones I think a significant driver of their ever-increasing sizes is that battery technology is lagging behind power demand. The worst thing of having a small phone these days is that the battery lasts less than a day. Big screens used to be too power hungry to be practical but LEDs are extremely efficient these days.

    My prediction is that we’ll return to the miniaturization craze of the 1990s whenever the next breakthrough in battery technology happens.


  • gif emoji nerd ajeitando óculos excuse me the embargo has an exception for food and medicine

    It’s really easy you see, you just need to pass an inspection and get a written permission from the President of the US, the payment must be made in cash in US dollars before shipment and through some non-American bank, and the shipping company must go straight from a US port to a Cuban port and back with no layovers.

    This is not a joke, it’s what is actually written in the law.





  • yay xfce sensors
    
    3 aur/xfce4-sensors-plugin-nvidia-hddtemp_through_netcat-current 1.3.95-1 (+2 0.00) (Orphaned) 
        Sensors plugin for the Xfce panel with nvidia and hddtemp (through netcat) support
    2 aur/xfce4-sensors-plugin-nvidia 1.4.4-2 (+26 0.00) 
        A lm_sensors plugin for the Xfce panel with nvidia gpu support
    1 extra/xfce4-sensors-plugin 1.4.4-1 (198.8 KiB 808.5 KiB) [xfce4-goodies] 
        Sensors plugin for the Xfce panel
    ==> Packages to install (eg: 1 2 3, 1-3 or ^4)
    ==> 1
    Sync Explicit (1): xfce4-sensors-plugin-1.4.4-1
    [sudo] password for unperson: 
    resolving dependencies...
    looking for conflicting packages...
    
    Packages (8) exo-4.18.0-1  garcon-4.18.2-1  libwnck3-43.0-3  libxfce4ui-4.18.6-1  libxfce4util-4.18.2-1  xfce4-panel-4.18.6-1
                 xfconf-4.18.3-1  xfce4-sensors-plugin-1.4.4-1
    
    Total Download Size:    2.66 MiB
    Total Installed Size:  15.76 MiB
    
    :: Proceed with installation? [Y/n] 
    




  • I doubt they worried about being condescending, lots of people fear that the official documentation will be too difficult and never read it. The logic is that the docs are arcana written by witches that know how to write programming languages, and the tutorials are written by regular girls that had to struggle to understand the language instead of the syntax just appearing on their heads.

    I pretty much learned how to program from the official Python tutorial. I had been struggling for years before that; I had some notions but I couldn’t put together anything really useful. The Python docs got me over the hump precisely because of what OP said: it starts from 0 and builds up until you have enough tools to write whatever project you have in mind. I imagine that having had to design and reason everything about the language actually gives the writer a great sense of how it fits together and what the logical increments are.

    Since then I always go first to whatever the language designers wrote; for example K&R’s The C Programming Language, the Rust book, the Postgresql manual, etc, and only once I feel that I know enough I complement it with other sources.

    This approach extends to libraries as well: first I read whatever official docs there are, then I search the source code for the functionality I need to learn about, and only if that fails I look elsewhere.

    It seems like a slow method but it’s so reliable that it works out for me. After a while of doing this you become the reference and people come ask you questions.