Ah, does not releasing full documentation not count as Apple "trying to get in their way"? Not trying to be snarky, genuinely trying to figure out how folks draw the line, since in my head, keeping documentation private smells like obstructionism.
Posting because as a former piano kid who never really got music theory, the practice exercises and the embedded YouTube examples really helped me grok some stuff that was black magic to me previously.
It's called union-find, but also disjoint-set sometimes. The process of reparenting nodes is called path compression, and the optimization of using the larger set of the two as the parent when merging is usually just called "union by rank." Any of those terms should give you more details upon search.
“ Until further notice, Emirates plans to operate as scheduled to and from LHR.” Anyone more familiar with airport operations care to explain how this is feasible, if LHR doesn’t think they have what it takes to handle the load?
The older, non-web versions of most of those things are still available to pirate. I’d find it hard to believe that the marginal improvements found in the online versions would have any significant impact on the poverty reduction effects of even having a decade-old version of things like the Office Suite or Photoshop.
In the sense that public market stock valuations are debt-dependent, because cheaper debt increases future earning potential by making it cheaper to finance operations, acquisitions, expansions. Without the expectation of high public valuations, VC have less incentive to pump cash into early-stage companies. I think that's the rationale?
Where do you get that sense that Rust results in memory leaks? Is that just an assumption you’re making about languages without garbage collection, or are there examples you’re aware of Rust applications having to deal with runaway memory consumption?
Community college is cheap, but isn't $65 for four credits cheap. Most financial aid I've seen has been in the form of loans, which also won't be as cheap as getting credit for those classes from testing out.
Pretty nifty how the example images of things like the sand grains (but make it Deep-Field-y) were made. I was hoping for an explanation, and the author didn’t disappoint.
You can manually choose the lens, but in edge cases where the stock camera app decides that you're too close to the subject to be able to focus with, e.g. the 3x lens, it switches to the 0.5x ultrawide lens instead, to maintain focus, and crops to maintain the same field of view. Using a non-stock app lets you force it to respect your lens setting, out-of-focus and all.
I was trying to ask about things where it took you a certain amount of time upfront to learn to make it well, but once that's done, it only takes you a small amount of time to make each individual piece. I think this sort of thing was asked elsewhere, basically how do you account for "R&D" and expertise-building in your hourly rate.
I'm interested in how you adjust that for expertise; do you bump your hourly rate for items that took you longer to learn to make well? How do you figure out how much to bump by, if you do?
I had it in my head somehow that the only version of the FSD out was the beta, didn’t realize the beta was a layer on top of the paid FSD package. Cutting off beta access seems reasonable here if the paid FSD package wasn’t rescinded.
Huh, that's kind of wild. I'd assumed that blocking all light out at your eyes would do the same trick, I'll have to try the blackout curtains. Thanks!
Doesn’t the same criticism apply to the aesthetic choices baked into film? It seems to me that the amount of technical expertise it takes to post process a phone-captured RAW file in Lightroom compares favorably to the amount of expertise it would take to have a physical dark room and tools to dodge and burn. If anything, it seems to me that it’s gotten easier to master the tools necessary to make your pictures look technically better.
The tone of the article stands out to me; not much in the way of exaggeration or opinions on “the best” way to do a certain thing, but an almost dispassionate tour of some of the different ways we’ve thought about light and dark artistically, over time. Thoroughly enjoyed the read!
Cursory look gives you a ~$3500 price tag for a gaming PC with a 3090 [1], vs. at least $4k for a Mac Studio with an M1 Ultra. Roughly the same ballpark, but I wouldn't call the M1 Ultra more affordable given those numbers.
Professor Lue from Harvard has a pretty cool visualization of how ATP synthase uses rotation and the energy produced through cellular respiration to produce ATP at https://www.youtube.com/watch?v=kXpzp4RDGJI, slightly more visceral than digging through a paper for a layperson.