Actual Problem: C → Segmentation Fault

Honestly, vscode opens in a split second for me, faster than I can react and start typing. For all intents and purposes it is instantaneous. Granted my setup is extremely clean and I only have the barest extensions installed for my workflow. The performance is consistent in my Windows, macOS and Linux machines.

I can’t imagine it running slow at all (perhaps someone with hundreds or thousands of extensions would). The last two editors I could recall that took the whole of eternity in the time space continuum to load were Eclipse and Atom. And those were slowass right out of the gate with zero extensions or plugins.

Best I can do is a JPEG of a goat, but singular. One goat.

This man is too dangerous to be left alive.

China: “Hold my Tsing Tao”

If it fits you must acquit!

But are you even a real programmer if you don’t test in production?

There’s the (very) real issue of infant mortality.

Anyone who doesn’t use standardized libraries for tz should be summarily tried.

I’ve never met this man in my life.

Black speech all the way. I believe the hellfire of Mt. Doom will cleanse all bugs, and I will die on this volcano so fight me on it.

Same, I have never pirated any game since the day I installed steam for the first time. It just makes buying games so much easier, and I don’t have to worry about drm or malware at all.

In my case, I rather pay a one-stop reasonable price for content than deal with the hassle of piracy.

Its a travesty that MATLAB isn’t in there somewhere.

I did exactly this last year to monitor my cats at home while I was on holiday.

I bought two of these - REOLINK RLC-811A: https://www.amazon.com/gp/product/B09873G7X3

I assigned static IPs to both of these, and blocked all of their outgoing traffic to the public internet (in case Chairman Xi or Strongman Putin wants to also see what my cats are up to).

I then spun up a local motioneye container: https://github.com/motioneye-project/motioneye

The cameras by default (I think) provide rtsp streams, so I added the two streams (rtsp://somehostname.local:554/h265Preview_01_main) to motioneye and verified that I was able to view the camera streams on my local LAN.

The last step was simply to use cloudflare to as an authentication frontend to proxy my local motioneye container to my public domain name. Worked a treat!

Hope this helps, cheers.