Since 2008 or 2009 I work on Apple hardware and OS: back then I grew tired of Linux desktop (which is going to be MASSIVE NEXT YEAR, at least since 2001), and switched to something that Just Works. Six years later, it less and less Just Works, started turning into spyware and nagware, and doesn't need much less maintenance than Linux desktop — at least for my work, which is system administration and software development, probably it is better for the mythical End User person. Work needed to get software I need running is not less obscure than work I'd need to do on Linux or othe Unix-like system. I am finding myself turning away from GUI programs that I used to appreciate, and most of the time I use OSX to just run a terminal, Firefox, and Emacs. GUI that used to be nice and unintrusive, got annoying. Either I came full circle in the last 15 years of my computer usage, or the OSX experience degraded in last 5 years. Again, this is from a sysadmin/developer ki
States. The final frontier. These are the voyages of an enterprising developer. Her eternal mission: to explore strange new techniques, to seek out better ways to engineer for mental models and new design patterns. To boldly go where a few awesome devs have gone before.
So you’ve found our poignant guide to SCXML and surely you’re wondering “Why should I want to go out of my way to use formal state machines?” or something like that. Hopefully this introduction addresses that kind of question.
| ########## | |
| #' Applies a function to subsets of a given dataset. | |
| #' Note: sets values without sufficient data to NA. | |
| #' Using 'step' is particularly useful for leave-one-out analysis. | |
| #' | |
| #' @export | |
| #' @name slide_apply | |
| #' @author \href{https://github.com/stillmatic}{Chris Hua} | |
| #' @title Use apply over a sliding window of data | |
| #' @param data Array of data to apply the function over. |
| import sys | |
| import subprocess | |
| import csv | |
| def describe_ucrt_lib(platform): | |
| lib_path = "windows-10-sdk/Lib/10.0.10240.0/ucrt/{}/ucrt.lib".format(platform) | |
| output = subprocess.check_output(["nm", lib_path]) | |
| output = output.decode("utf-8") | |
| # Output (x86 32-bit) looks like: |
| export function retrieve(nodeId) { | |
| return { type: 'RETRIEVE_NODE', payload: { nodeId: nodeId } } | |
| } | |
| export function show(nodes) { | |
| return { type: 'SHOW_NODE', payload: { nodes: nodes } } | |
| } |
| library(rvest) | |
| library(tidyr) | |
| library(splines) | |
| library(stringr) | |
| library(ggplot2) | |
| library(dplyr) | |
| setwd("C:/Dropbox/Projects/20160705_Calories_Per_Meal") | |
| men = read_html("http://health.gov/dietaryguidelines/2015/guidelines/appendix-2/") %>% |
| public class Sample1 | |
| { | |
| public native int intMethod(int n); | |
| public native boolean booleanMethod(boolean bool); | |
| public native String stringMethod(String text); | |
| public native int intArrayMethod(int[] intArray); | |
| public static void main(String[] args) | |
| { | |
| System.loadLibrary("Sample1"); |
If you're thinking of checking out the Pony programming language, here's a list of things that I think are important to know. This list is based on a Tweet that I wrote.
There are Pony packages for several popular editors.
Concurrency is a domain I have wanted to explore for a long time because the locks and the race conditions have always intimidated me. I recall somebody suggesting concurrency patterns in golang because they said "you share the data and not the variables".
Amused by that, I searched for "concurrency in golang" and bumped into this awesome slide by Rob Pike: https://talks.golang.org/2012/waza.slide#1 which does a great job of explaining channels, concurrency patterns and a mini-architecture of load-balancer (also explains the above one-liner).
Let's dig in: