It can somehow be excused in cheap models because new versions are generally incremental evolutions, which would make proper integration of the touchscreen harder/more expensive. But not in a brand new model of a luxury brand.

Philip K. Dick's Ubik, A Scanner Darkly, and Flow My Tears, The Policeman Said.

Clifford D. Simak's City.

Classics.

Fond memories of Laelith ;-).

Yes… if the founder does. I don't care on which side of which ring they are as long as they keep me out of their pointless fights.

It's all just a stack of layers, one window per layer. There is no shadow to speak of, only a mask around the window that provides the illusion of shadow. So there is no real interaction between all those items, no source of light, no distance, and no way to do ray tracing or some other techniques.

Today, it's Tony Hoare: https://news.ycombinator.com/item?id=47324054

    :let no_man_maps=1
    :let loaded_matchparen = 1
    :set comments=""
    :set matchpairs=""
    :set paste

The values for 'comments' and 'matchpairs' are incorrect, they should be:

    :set comments=
    :set matchpairs=

Setting the following variable is useless if you don't enable the 'man' plugin, but maybe you do it manually during a session. I don't know. YMMV.

    :let no_man_maps=1

I tried to watch The Age Of Disclosure and, well… Everyone in it manages to stay relatively reasonable during the first fourth of the movie. Until they decide that the most likely explanation of all those unexplained phenomenons is a race of technologically advanced extraterrestrials hiding at the bottom of the ocean for thousands of years.

It went from "we don't know anything" to "it's threatening aquatic ETs" in a heartbeat. It was almost scary.

I could do it because I had _some_ level of control on my work machine. Now that I work for a much larger organisation… I can't even imagine how hard it would be to have such a setup.

I don't know how usable it is in practice if you are switching contexts every 10 minutes, though.

FWIW, I use Chrome 145.0.7632.117 on a M1 MacBook Pro and I just got a notification suggesting me to "correct" the o'rer tab because it used too much resource. I was looking at the details of my Transilien station.

Also, looking a the same "details" popin, I see some irrelevant info when I click on the "alert sign" of a Transilien line (Line N in this case): something about bus stops.

I have a couple of questions about the API:

I've looked at the data provided by IDFM and SNCF a few times but I was never able to find a way to match a commercial train number, say "134671", to a physical train number, say "211L" or "Z50421/22" or the more complicated EVN. Did you, by any chance come upon such a thing?

Also, could you confirm that the only data available concerns _departure_ times?

Good luck.

Strongly recommended.

https://cityofdarkness.co.uk/

I have one here: https://github.com/romainl/vim-sweet16 but it is intentionally weird and essentially unmaintained.

FWIW, the current de-facto standard is set by xterm. Here is a relevant excerpt of its source code:

    ! Disclaimer: there are no standard colors used in terminal emulation.
    !
    ! The choice for color4 and color12 is a tradeoff between contrast, depending
    ! on whether they are used for text or backgrounds.  Note that either color4 or
    ! color12 would be used for text, while only color4 would be used for a
    ! background.  These are treated specially, since the luminosity of blue is
    ! only about half that of red/green, and is typically not accounted for in the
    ! RGB scheme.
    !
    ! Blue text on a black background should be readable.
    ! Blue backgrounds should not be "too" bright.
    !
    ! Originally color4/color12 were set to the names blue3/blue
    !*VT100*color4: blue3
    !*VT100*color12: blue
    !
    ! They are from rgb.txt respectively:
    !  0   0 205  blue3
    !  0   0 255  blue
    ! However, blue3 is not readable on a black background.
    !
    ! Another choice was from the Debian settings:
    !*VT100*color4: DodgerBlue1
    !*VT100*color12: SteelBlue1
    !
    ! From rgb.txt:
    ! 30 144 255  DodgerBlue1
    ! 99 184 255  SteelBlue1
    !
    ! Some users object to this choice because the background (color4) is brighter
    ! than they are accustomed.  Others point out that the different weights for
    ! the red/green components make it appear to be not really blue.  Finally, it
    ! provides poor contrast against color13 and color14.
    !
    ! The current choice uses equal weights for red/green (effectively adding a
    ! gray to the result).  It is brighter than the original choice, and provides
    ! more contrast between color12 and color13, color14 than SteelBlue1 did.
    ! Contrast of color4 against black is slightly improved over the original.
    !
    ! Some refinement is certainly possible (you are welcome to try) -TD