check current python linkage
% otool -L /Applications/Synalyze\ It\!\ Pro.app/Contents/MacOS/Synalyze\ It\!\ Pro | grep Python
/System/Library/Frameworks/Python.framework/Versions/2.7/Python (compatibility version 2.7.0, current version 2.7.16)
Download and install Python2.7.16 for macOS. By default this lands in /Library/Frameworks/Python.framework/Versions/2.7
Make a copy of the Synalize It! Pro app bundle, e.g. to your desktop.
cp -R /Applications/Synalyze\ It\!\ Pro.app ~/Desktop
| #!/bin/zsh | |
| TARGET=$1 | |
| # to be used as an egrep pattern | |
| SYMS='getprogname|NSGetArgv|NSGetArgc|optarg|optind|getopt|getopt_long' | |
| sudo find ${TARGET} -type f -perm +111 \! -name "*.dylib" | \ | |
| while read f ; do | |
| sudo nm -u ${f} 2> /dev/null | \ |
| // ==UserScript== | |
| // @name Prevent link mangling on Google | |
| // @namespace LordBusiness.LMG | |
| // @match https://www.google.com/search | |
| // @grant none | |
| // @version 1.1 | |
| // @author radiantly | |
| // @description Prevent google from mangling the link when copying or clicking the link on Firefox | |
| // ==/UserScript== |
Below are a list of System Preference pane URLs and paths that can be accessed with scripting to assist users with enabling macOS security settings without having to walk them through launching System Preferences, finding panes, and scrolling to settings. Not all panes have an accessible anchor and some are OS specific.
To find the Pane ID of a specific pane, open the System Preferences app and select the desired Preference Pane. With the pane selected, open the ScriptEditor.app and run the following script to copy the current Pane ID to your clipboard and display any available anchors:
tell application "System Preferences"
set CurrentPane to the id of the current pane
set the clipboard to CurrentPane
| patch file to implement workaround from https://github.com/oracle/vagrant-boxes/issues/178 | |
| --- /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb.orig 2019-10-14 12:01:06.000000000 -0500 | |
| +++ /opt/vagrant/embedded/gems/2.2.6/gems/vagrant-2.2.6/plugins/providers/virtualbox/driver/meta.rb 2020-01-18 14:17:54.000000000 -0600 | |
| @@ -64,6 +64,7 @@ | |
| "5.1" => Version_5_1, | |
| "5.2" => Version_5_2, | |
| "6.0" => Version_6_0, | |
| + "6.1" => Version_6_1, | |
| } | |
| #!/usr/bin/python | |
| bpf_text = """ | |
| #include <linux/ptrace.h> | |
| #include <linux/sched.h> /* For TASK_COMM_LEN */ | |
| #include <linux/icmp.h> | |
| #include <linux/netdevice.h> | |
| struct probe_icmp_data_t | |
| { |
| require 'bundler/inline' | |
| gemfile do | |
| source 'https://rubygems.org' | |
| gem 'colorize' | |
| end | |
| class MatcherInterface | |
| def initialize(some_object) | |
| @some_object = some_object |
| package main | |
| import ( | |
| "bufio" | |
| "fmt" | |
| "io" | |
| "log" | |
| "strings" | |
| "k8s.io/apimachinery/pkg/util/yaml" |
| # Basic Makefile for Golang project | |
| # Includes GRPC Gateway, Protocol Buffers | |
| SERVICE ?= $(shell basename `go list`) | |
| VERSION ?= $(shell git describe --tags --always --dirty --match=v* 2> /dev/null || cat $(PWD)/.version 2> /dev/null || echo v0) | |
| PACKAGE ?= $(shell go list) | |
| PACKAGES ?= $(shell go list ./...) | |
| FILES ?= $(shell find . -type f -name '*.go' -not -path "./vendor/*") | |
| # Binaries | |
| PROTOC ?= protoc |
I am passionate about Ruby, but its execution time compared to other languages is extremely high, especially when we want to use more complex algorithms. In general, data structures in interpreted languages become incredibly slow compared to compiled languages. Some algorithms such as ´n-body´ and ´fannkuch-redux´ can be up to 30 times slower in Ruby than Go. This is one of the reasons I was interested in embedding Go code in a Ruby environment.
For those who do not know how shared libraries operate, they work in a similar way as DLLs in Windows. However, they have a native code with a direct interface to the C compiler.
Note Windows uses the DLL system, and in this case, this does not necessarily have to be in native code.
One example is DLLs written in C#, which runs on a virtual machine. Because I do not use windows, I ended up not testing if it is poss
