Yeah the advice to "use trimmings!" seems very based in a restaurant situation where (a) lots of vegetables are getting prepped regularly and (b) cutting techniques are based on the goals of speed and uniform product, so you'll see things like squaring up a vegetable into a cuboid before dicing it... which produces "scraps" that aren't wasted, because they can go into a stock!
So much peripheral functionality has been pushed inside the CPU that a modern desktop motherboard is from one point of view essentially a fancy DC-DC converter that happens to also handle I/O port breakout. The motherboard has to translate 12 volts at 10-ish amps from the PSU, into a highly stable 1.2-ish volts at 100-ish amps for the CPU power rail.
There were/are a couple of aerospace surplus shops in the area. Apex and Norton are the ones I'm familiar with. The supply comes from the SoCal aerospace industrial base and a lot of the demand is indeed for movie props. It's a fortuitous pairing - the prop rental business seems to be keeping them going to some extent whereas a lot of industrial surplus businesses in other parts of the country seem to be struggling these days.
Singular "pant" has recently-ish become accepted fashion industry jargon: "Our spring collection includes a khaki pant and a capri pant". I've started to see it creep from there into everyday language.
Yeah I'm a little surprised not to see the article touch on keyboard layouts (e.g. DEC, Sun) that had Ctrl in the home row where Caps Lock is on a PC keyboard. While Emacs may have been initially developed on the "space cadet" keyboard, it really became popular on Unix systems that often had an even-easier-to-reach Ctrl key. And to this day swapping caps lock with a modifier remains fairly common.
> The idea was that you didn't want young kids opening the driver side door and stepping out into traffic.
I always heard that was sort of a retroactive justification, and the real reason is that a driver's side sliding door would have interfered with the fuel filler. The second-generation Chrysler minivans solved that problem by introducing a mechanical interlock, so that you couldn't open the driver's side slider while the fuel door was opened.
In the Palo Alto/Mountain View/Sunnyvale area I see Waymo, Nuro, and unmarked-but-we-all-know-it's-Apple autonomous vehicles quite frequently. A few times a week at least.
Cruise specifically operated in SF where I agree they have been a very common sight.
> That's possibly the most inefficient way of saying "AWS bought Fig" but I guess it makes some people happier to frame it that way
Often that kind of language is employed when the actual transaction was structured as an asset sale coupled with en-masse hiring of the team, rather than a true acquisition of the company as a complete entity, which is not an unusual scenario when a company is in distress.
Good ergonomics for Perl-style quick and dirty text processing were part of the original design goals for Ruby. Those parts of the language are still there. You can write code that feels more concise than Python yet, IMO, tends to be more readable/maintainable than Perl can stereotypically be. Modern style guides, however, de-emphasize that style of Ruby since it might not be the most appropriate in the context of say a large Rails project.
... Electrolytic capacitor manufacturers have to publish Material Safety Data Sheets (MSDS) just like everyone else, disclosing exactly what's in there (with CAS numbers and everything), what the health and safety risks are, and giving advice on treating an exposure. They don't have to give the exact percentages or recipe for making the electrolyte, and they can omit mention of constituents that are known harmless (e.g. water), but they certainly can't put random dangerous chemicals in their products without saying so.
A big usecase for C is embedded systems projects where wrangling cross-compilers, debug dongles, etc. can become a big headache especially when trying to keep multiple developers' local toolchains in sync or when managing multiple projects with different requirements for the development environment.
The key dimension for refracting astronomical telescopes is the diameter of the primary lens, which is 36 inches at Lick and 40 inches at Yerkes.
However, my understanding is that the Yerkes lens has suffered cracks around its perimeter and the telescope has been stopped down with baffles to mitigate the optical problems these cracks would otherwise cause, such that presently the Lick telescope has a larger clear aperture.
> Naively, I assumed that it must take more power to transmit than to receive, which is true on an instantaneous basis, but false on an average basis.
Even that is not necessarily always the case in low-power systems, since often receive amplifiers need to be run at a fairly high current to achieve a low noise floor, and power saving tricks like envelope tracking power supplies are harder to implement on the receive side.
For example, I've seen several Bluetooth LE radios where the instantaneous supply current is higher during receive than during transmit.
I mean, what did you expect from a product category that was basically born of the question "how can we use modern food science to create a product that appeals to vodka-soda drinkers, but falls under the tax regime of a beer?"
I'm more familiar with the world of spirits but it's much the same situation - there is certainly unpalatable swill on the very bottom shelf, but at some fairly low price point you hit a perfectly adequate level of quality and products priced above that level are about some combination of brand cachet and/or unique and interesting flavors, moreso than being objectively "better".
I've never really seen this explicitly stated anywhere, so maybe this is some super idiosyncratic idea on my part, but it's always seemed to me that one of the key pieces of OO is the use of polymorphism as a sort of syntactic/conceptual sugar around function indirection, that many people seem to have an easier time understanding and reasoning about.
For binary software licenses, historically a lot of them have been premised on the idea that it is impossible to use the software without copying it from installation media onto local storage and/or from storage into RAM for execution, meaning that effectively it's possible to use contracts based in copyright law to set terms for the use of the software and not just for what a human might think of as "copying".
I once saw a CS student ask for homework help on Reddit, with a question premised on the course material's attempted formalization of "high level" and "low level" programming languages as a partial ordering based on machine-translatability from one language to the other. The terms "level n" and "level n-1" were being bandied about. Another instance of adding confusion by trying to sharpen the definition of terminology that is probably most useful when it remains fuzzy.
By far the most memorable college class I took was an advanced electronics lab where I ended up as the "unofficial TA". I was by no means an expert but I guess I got a reputation for picking the material up quickly and being able to help guide my classmates to the same understanding. It was honestly a little stressful but in retrospect being pushed to internalize what I was learning deeply enough to be able to explain it clearly to fellow students was highly beneficial to my own learning process. I was never all that interested in grad school or academia, but the meta-lesson of that course has stuck with me in guiding career choices... I tend to seek out opportunities for consulting or mentoring type roles knowing that they will help further my own learning as well.
A practicing musician owning multiple instruments, some of which may be used only rarely, is a different situation from a non-musician collecting instruments for their decorative or monetary value.
(Sometimes, collectors who own valuable instruments lend them to accomplished musicians, perhaps even on a long-term basis. I think that's admirable!)
I had been under the impression it was relatively common knowledge that the reason Reddit had been keeping both the API and old.reddit alive was that power users - both moderators and the most prolific content submitters - disproportionately used those interfaces and were considered too valuable to alienate. I have been surprised not to see much discussion about what, if anything, changed about that situation leading up to the current kerfluffle. Have enough power users been moving over to new.reddit and the official apps? Or has Reddit's calculus as to the importance of that segment of the user base shifted?
I feel like it used to be (I'm thinking 1990s or so) the norm that basically everyone reclined starting from the first in-flight announcement, except for mealtimes. Come to think of it, didn't those announcements from the pilot often specifically invite passengers to recline?
I am curious why, and when exactly, sentiments around this apparently changed so much. Was it tighter row pitches that prompted the shift? Widespread ownership and use of laptops?
And for what it's worth today's Broadcom is actually Avago - which got its start as HP's semiconductor division - after having acquired Broadcom and adopting its name.
Typically mathematical treatment of DSP is based on the discrete-time Fourier transform and the Z transform, which differ from respectively the Fourier transform and the Laplace transform not in using square waves, but in using an infinite series rather than an integral to capture the idea of discrete sampling.
Sublime Text 2 (its first cross-platform version) came on the scene around that time and I think drew away a lot of the crowd that had been waiting for TextMate 2.