dognotdog

Sounds exactly like the fever dream I see everybody live, lol

> The 105mm 2.0 DC and slightly older 135mm 2.0 DC [...]

I almost never change the defocus control on the 135/2.0 from neutral, yet I believe the lens makes it almost impossible to take a bad portrait. The only reason to keep a DSLR around instead of a mirrorless is that this lens has an old-school camera driven auto-focus, which Nikon's F-to-Z adapters don't support. While manually focusing that lens can be done, the shallow depth of field makes it very challenging for moving subjects.

In terms of control theory, the order "delay" is actually a simple filter. What leads to bad outcomes is exactly the described scenario, when the control response too fast for the system, overcorrecting and oscillating. Increasing the order filtering dampens the control response.

I am a big fan of learning LISP, at least once. Going through SICP after more than a decade of writing code for a living was probably the single best thing I did to deepen my understanding of a lot of compsci concepts, data structures, and how to think about software. For me, at least, it was very much a seeing the matrix for the first time kind of moment. My LISP use has quickly declined, but I've dabbled in dozens of programming languages since then, and I do attribute not feeling lost to that experience.

Indeed, how exciting a phone would be that fit in... you know... bear with me... your pants' pocket you already have... lol

Indeed I have 3D assets in this case. Would this be done differently in an enterprise that has all kinds of tools to manage specialty workflows? Sure. Do I want to spend my days configuring and maintaining some binary blob / LFS storage system? No.

I’ve migrated a lot of projects from fossil to git eventually, but I dare say they never would have made it that far, had I started out with more friction, including fighting vcs tools.

I keep coming back to fossil again and again, despite git having a huge pull because of the easy publishing and collab on github/gitlab.

Just the other day I was starting an exploratory project, and thought: I'll just use git so I can throw this on github later. Well, silly me, it happened to contain some large binary files, and github rejected it, wanting me to use git-lfs for the big files. After half an hour of not getting it to work, I just thought screw it, I'll drop everything into fossil, and that was it. I have my issue tracker and wiki and everything, though admittedly I'll have some friction later on if I want to share this project. Not having to deal with random git-lfs errors later on when trying to merge commits with these large files is a plus, and if I ever want to, I can fast-export the repo and ingest it into git.

I was under the impression you could only activate one esim at a time, but store up to 6(?) on that phone?

This is probably a longer discussion, but PM0.3 (anything less than 0.3 microns) is quite difficult to measure, especially optically, as light scattering drops off very steeply once your particle sizes are around the wavelength of the light being used. Anything short of an SMPS class instrument that “grows” small particles through condensation so that they appear large enough to be counted, will not see much below 0.3 microns. Also, the total MASS of small particles might be low, but if you look at count, or lung-deposited surface area, we get a different picture. Especially around 0.3um, particulate matter is prone to get deep into the lungs, instead of being caught in the upper airways, and the small size means larger relative surface area, and thus higher reactivity. Even smaller nano particles might not go as deep, but are more likely to enter cells or the bloodstream due to their minuscule size.

While I admire the efforts of the SC-AQMD, and generally agree with the article, using R2 from a higher-end, but not quite perfect instrument, can be quite misleading, and is not a great indicator of actual sensor performance. Also, there are a lot of potential improvements in sensor tech, but instead almost everyone is relying on the same cheap sensor modules instead of innovating, which have have pretty bad deficiencies, especially in detecting particulates in the ultra-fine range, and don’t age very well. But, they are the cheapest.

I kind of went the other way as github/gitlab took off. I was using fossil for years because it was so self contained with issue tracking and everything, and it is great, but the lack of easy two-way interop with github had me gradually drop it for new projects, when I anticipate some level of other contributors. That being said, going from fossil->git via git-export is very simple and painless.

My understanding is that Quicktime Player has been in the SIP domain for recent OS releases, so it just won't load 3rd party libraries at all :/

I'd claim things are more nuanced. There are many reasons why UIs in many places, not just cars, suck. In cars, wether warranted or not, there is also pressure from legal to err on the side of building a cludge that is unassailable vs. a smooth user experience that could be grounds for a class action because it doesn't make enough of an effort to discourage dangerous user behavior.