I was taught script in the US and Italy as a child, and never learned it like this.
948 karma · joined May 6, 2015
I was taught script in the US and Italy as a child, and never learned it like this.
Very high end amateurs get pissy about it because they paid a lot of money for high end equipment to minimize imaging times, but for the rest of us it’s not a huge impediment as we already needed lots of subframes to get high SNR anyways.
I have one of the mentioned SeeStar smart telescopes, and have been quite successful in taking photos of both galaxies and nebulas from the rooftop of my apartment building in the middle of a city.
Sure, it takes time. Sure, it would be faster/better under darker skies. But it’s not impossible!
Consoles are always pressured to minimize upfront purchase costs, and they generally replace the vendor-provider SW stack with their own anyways.
It knows how to rematerialize, and has for a long time, but the backend is generally more local/has less visibility than the optimizer. This causes it to struggle to consistently undo bad decisions LICM may have made.
And "no problem" and "not bad" are both common colloquial statements in American English.
He had previously been working for a scientific supplies company in Chicago that was (unbeknownst to him) providing supplies to the Manhattan Project. Apparently his boss was aware of it, and when my grandfather's draft was called a letter from his boss convinced the draft board to assign him to Los Alamos instead. He was eventually able to get my grandmother, a secretary and typist, a job as a secretary in Los Alamos as well so that she could join him. She teased him the rest of their lives, because as the secretary to someone more important than a lowly technician, she had technically had a higher security clearance than he ever did!
The Atomic Heritage Foundation collects records about people who were affiliated with the Manhattan Project, as well as oral histories. Perhaps they have more information about your grandfather's work? See here: https://ahf.nuclearmuseum.org/ahf/bios/
I don't know that much about movie making, but my understanding is that there would be managers and/or leads within each specialty, who are (among other things) managing the interaction between their specialty and the director / producers.
That seems pretty comparable to what's being discussed here.
Optimization "timeouts" aren't done in wall time, but in something that can be deterministically counted: number of instructions, number of recurrences up a call stack or expression tree, etc.
Mostly the former. Some highly optimized bits of software do the latter—they are built with multiple code paths optimized for different hardware capabilities, and select which one to use at runtime.
> Do dynamic languages (Javascript, Python, PHP...) get a speed boost because they can compile just in time and use all the features of the user's CPU?
Hypothetically yes, but in practice no for the languages you mentioned because they don't map well to things like SIMD. Some JIT-based numerical computing systems as well as JIT-based ML compilers do reap those benefits.
It's also often about offload. Depending on the use case, the CPU and GPU may be busy with other tasks, so the NPU is free bandwidth that can be used without stealing from the others. Consider AI-powered photo filters: the GPU is probably busy rendering the preview, and the CPU is busy drawing UI and handling user inputs.
And that’s not to mention applications. It used to be common for GUI applications to be scriptable and to support plugins!
While not zero users, the default fee has been set at 30% since the beginning of the App Store, long before Apple had the level of market dominance it has today.
This argues in favor of it being acceptable: developers were willing to accept that fee without monopoly pressure being applied, since nobody has successfully argued that Apple held a monopoly in 2008.