sharpen the edges, and it’s a home defense weapon

oh man probably me too. either that or Evanescence.

i was a angsty lil’ dickhead omg

“Pretty fly, for a wi-fi.”

I guess I haven’t seen that many, but there aren’t any comments yet, so I win by default!

It wasn’t English class before you got here — but, unfortunately, it turned out you missed the other English classes! No big deal, though, we’re happy to pivot.

So, let’s talk about the subjunctive …

DP-alt-mode, datarates, cabling are all vastly more complicated than you’d think. (I’ve spent easily 500 hours of my life, buying dozens of products and specific cables, running debugging hardware and software … getting Pro Display XDR’s (6k displays) working at longer distances, behind Thunderbolt docks, on multiple OSes, etc — it’s it’s never intuitive.)

Some absurd things that may actually help:

1. flip the dock-to-display cable around (not even shitting you)
2. if the dock is a DP-alt consumer itself, plug an unterminated HDMI cable into it (and into nothing else),
3. change the order in which you plug various things into eachother post-boot (ideally, nothing plugged into anything other than that C-D-M chain of three items; then try C-D-first/D-M-second, and try D-M-first/C-D-second.)

Failing various fixes with existing equipment, the cheapest next steps will be cabling — despite the high promises of USB-C, all cables are absolutely not created equal when it comes to high-pixelclock-DP-alt-mode:

1. Shortest possible cables. Get shorter USB-C cables from reputable vendors. Make sure they’re maximum-data-rate certified.
2. This is counterintuitive as fuck, but do not use “better” Thunderbolt cables to substitute USB-C cables for USB-C-capable-displays. (They can work plenty often; but they can also be problematic with some EDID/OS combinations.)
3. If your display has other inputs, you may have more luck with a USB-C-to-DisplayPort-proper cable, than a traditional USB-C-to-USB-C cable.
4. Worst case, look into a cable with an active repeater. I’ve had luck with CableMatters’ Cable Matters Active USB C Cable… https://www.amazon.com/dp/B07PPVMYRV?ref=ppx_pop_mob_ap_share

tl;dr good luck this might be gon suuuuuck. )=

What on earth size of monorepo is that!? iirc, we’ve got ~1Mloc of OCaml, probably another two or three times that in assorted generated code, specs, config, infra, and other languages; and my VScode-Remote definitely boots up as fast as the network connection can stand up.

Definitely faster than I can think of the first thing I want to do … ¯_(ツ)_/¯

That said, I should own up to having had an absurdly overcomplicated vim config, tons of plugins, a decade n change of customizations and patches and shit. Maybe I’ve just always had a high tolerance for a slow boot. hahaha

Whewf I’m boutta out myself or something, but …

after 15 years of vim, writing (and contributing to) a host of plugins, even running custom builds with my own patches …

I basically never boot up Actual Vim anymore?? I’ve basically entirely switched to VScode + VSCodeVim. embarrassing as fuck, in some ways, but jesus christ it’s just too goddamn good.

The neovim integration, even, was fantastic. (Although I don’t use it right now, for “VSCode Remote reasons,” lol.)