If you use homebrew to manage packages in macOS, you might notice that some formulas come with several versions. Take elasticsearch for example,
$ brew search elasticsearch outputs two versions:
fetchEachSynopsis() to work in parallel. For that, I will introduce a worker queue, to manage the execution of individual calls (tasks) to
movieApi.fetchSynopsis(). At its most basic, the queue constructor will accept a function to process individual task, and the queue instance will accept inputs (in our case, the movie titles) for the task.
movieApi is inefficient, you would then need to download each synopsis individually!. After each pair of title and synopsis is downloaded, it will be rendered into the UI.
While trying to work around some recent macOS limitation imposed on dtrace due to System Integrity Protection (SIP), I found this useful little sjourdan/strace docker container.
If you have been using Concerns in Rails, you might have noticed both controller and model directories have their own concern sub directory. It is helpful to think Concerns are modules meant for both components, as such might contain code specific to each component.
The goal of this post is enable very simple integration of a Rails application and Kibana (v5.2.1) dashboard.
Well I have been guilty of not exploring ES6, and even the ES7 standard was already finalized!
When working with android development, simple tasks like turning on the screen of your device during code deployment could easily become tiresome and annoying, if you have to do it every few minutes. One solution is to enable “Stay awake” via the “Developer options” of your device. But that is not very energy friendly!.
One of the projects I’m working on requires us to download web pages for some security analysis. Not only we need to download and store the main HTML source code, but also other resources the page pulls (eg: images, stylesheets).