MacOS has this feature under Settings -> General -> Language & Region -> Preferred Languages. Here you can have an ordered list of languages you wish apps and websites (I _think_ only works for Safari) to use. I don't know how widespread this is in other OS'es or browsers.
> Promises are a nice success story, but without async/await it wasn't really necessary to standardize
One benefit of standardisation that's not tied to async/await is that the JavaScript engines has been able to do performance optimisations not otherwise possible which benefit Promise-heavy applications
You most likely just don’t realize that your podcast app of choice actually gets its list of podcasts from Apple. That’s the authors point of Apple hosting it for free for everyone.
The ISP sets up rack-cabinets full of equipment in central buildings where the “last mile” fiber terminates, close to the neighborhoods that they service. Each ISP that provides service to the area needs to have their own equipment there. This is how they differentiate and how one ISP can do 1Gbps while another might be able to do 2Gbps. Simply because they have installed different equipment. The fiber itself can of course support much more
They want to close accounts with poor security (i.e. no 2FA enabled). These accounts has a higher risk of being compromised and used to get access to whatever they control
I would assume so, yes. This is exactly how regular motors get started, unless you have one of those old-timy cranks you had to manually turn to get the motor running
I really love this tool - We use it to backport commits from master to our older release branches on the Kibana project. I can't emphasize enough how many hours this saves us every week.
When I read the title, I honestly thought this was an official LEGO thing. This is exactly why it's important for a company like LEGO to protect its trademark.
I realize this is just an homage to LEGO and I'm sure they know and appreciate that. But they still need to defend their trademark. If they don't, anybody could just use their name for whatever they wanted - even things they DO NOT want to be associated with.
You're free to just depend on ci-info directly if that's all you need of course. The is-ci module does give you one added benefit however: It allows you to run this on the command line:
$ is-ci && echo "I'm running in a CI environment"
But of course that could technically be baked into ci-info. It's just more convenient to use with npx and to reason about if it's a self-contained module
Hi, co-creator of volkswagen here. Just some fun trivia about the project, which Kenneth and I obviously made as a joke years back when Volkswagen got caught cheating:
The Node module actually works. If you use it, it will make all your tests pass.
When writing the code, I put the logic for detecting if code is being run on a CI server into a separate node module called is-ci[1] (which the volkswagen module then depends on). That module (later split out into ci-info[2]) turned out to be so useful for actual work, that today it's being used by both React and the npm cli.
I only found this out recently. Imagine the surprise when a tiny part of a joke project you created years ago turns out to be one of your most popular open source projects :D