[–] 8 points 7 months ago (1 child)

People nowadays forget how shitty software used to be at launch.

Or so I’m told. I’m not actually of the generation that remembers software without an auto-updater.

  • source
  • [–] 11 points 7 months ago

    I program JavaScript for a living. I’ve noticed how I’ve become blind to my language’s idiosyncracies, but I still believe it isn’t super bad. Especially with all the new shiny features that were piled on ever since 2018-ish (I think).

    It is definitely nowhere near as bad as C++. And I’m only 6 minutes into the video.

  • source
  • parent
  • context
  • [–] 9 points 7 months ago* (last edited 7 months ago)

    I can’t edit my other comment, so I’ll put this here:

    The source mentions the town Sion and the mountain Bietschhorn. Here they are on OpenStreetMap. So I guess the image is taken in an Eastern, maybe East-Northeastern direction.

    The JPEG’s EXIF data say the image was recorded at 2026-04-09T04:26 (at least one of the timestamps says that. I’m taking this because the source also mentions the comet being visible just before sunrise).

    According to shademap.app, the Sun rose between 7:00 and 9:00 (depending on your exact position in Sion—the terrain is mountainous). Since the mountains in the image are already getting sunlight, I think the EXIF timestamp is actually in UTC, which puts it at 06:26 local time.

    Heading to Stellarium Web with that information I found that the Pegasus square is located between 70° and 90° (that is, East-Northeast to due East) and 10°–30° above the horizon. Eyeballing the image that is about the rectascension where the comet is visible.

    So If you’re looking for the comet, search the Pegasus square and below about an hour before sunrise.

    Edit: I just remembered that Google exists. Here’s the current position.

  • source
  • [–] 62 points 7 months ago* (9 children)

    The madman theory is a political theory commonly associated with the foreign policy of U.S. president Richard Nixon and his administration, who tried to make the leaders of hostile communist bloc countries think Nixon was irrational and volatile so that they would avoid provoking the U.S. in fear of an unpredictable response.

    https://en.wikipedia.org/wiki/Madman_theory

  • source
  •  

    Hi, I’m trying to get the hang of xinput. For a start I tried setting an option of a device to a value it already has.

    I want to go for my Touchpad. From the following output I identified ELAN050A:00 04F3:31B1 Touchpad as the device name.

    $ xinput --list
    ⎡ Virtual core pointer                    	id=2	[master pointer  (3)]
    ⎜   ↳ Virtual core XTEST pointer              	id=4	[slave  pointer  (2)]
    ⎜   ↳ ELAN050A:00 04F3:31B1 Mouse             	id=12	[slave  pointer  (2)]
    ⎜   ↳ ELAN050A:00 04F3:31B1 Touchpad          	id=13	[slave  pointer  (2)]
    # more lines
    

    Then I listed the available options:

    $ xinput list-props "ELAN050A:00 04F3:31B1 Touchpad"
    Device 'ELAN050A:00 04F3:31B1 Touchpad':
    	Device Enabled (180):	1
    	Coordinate Transformation Matrix (182):	1.000000, 0.000000, 0.000000, 0.000000, 1.000000, 0.000000, 0.000000, 0.000000, 1.000000
    # Lots more …
    	Synaptics Scrolling Distance (350):	-79, 79
    # Lots more…
    

    Then I tried setting the Scrolling Distance:

    $ xinput set-prop\
    "ELAN050A:00 04F3:31B1 Touchpad"\
    "Synaptics Scrolling Distance"\
    "-79, 79"
    X Error of failed request:  BadMatch (invalid parameter attributes)
     Major opcode of failed request:  131 (XInputExtension)
     Minor opcode of failed request:  57 ()
     Serial number of failed request:  21
     Current serial number in output stream:  22
    

    I also tried without the separating comma in the options list:

    $ xinput set-prop\
    "ELAN050A:00 04F3:31B1 Touchpad"\
    "Synaptics Scrolling Distance"\
    "-79 79"
    X Error of failed request:  BadMatch (invalid parameter attributes)
      Major opcode of failed request:  131 (XInputExtension)
      Minor opcode of failed request:  57 ()
      Serial number of failed request:  21
      Current serial number in output stream:  22
    

    What’s wrong with the parameter attributes? I’m on Linux Mint 21.3 and Kernel 5.15.0-173-generic.

     

    I understand that color is a 3D value, since all perceivable colors can be created my independently mixing 3 base colors. That naively gives us a color space shaped like a cube (like SRGB).

    I also understand that every color space needs to remove colors from the ‘everything’ color space due to technical limitations. This is usually represented by ‘cutting out’ a triangle from the following representation of the ‘everything color space’.

    BenRG and cmglee, CC BY-SA 3.0 https://creativecommons.org/licenses/by-sa/3.0, via Wikimedia Commons

    Even accounting for distortion of the color space (think Mercator projection), I believe there should only be three curves that cut the solid color space. Hover, in the image of the OKLAB color space there are 5. Why is that?

    And why is the ‘amount of height’ they cut from this supposed triangular prism so different depending on hue?

    The image is taken from the OKLCH Color Picker & Converter by Andrey Sitnik & Roman Shamin. https://oklch.com/#0.7344,0.1025,272,100

    view more: next ›